# Summary of S4-260262: [VOPS] On Conformance

## Document Metadata
- **Source:** Apple Inc.
- **Meeting:** SA4#135 (India, 9-13 Feb 2026)
- **Agenda Item:** 9.4
- **Purpose:** Discussion

## Introduction

This contribution addresses the incomplete implementation of repository tagging mechanisms for VOPS conformance material in TS 26.265, which were previously agreed but not yet executed.

## Background

### Previous Meeting Agreements

At SA4#134, the following decisions were made regarding VOPS conformance:

1. **S4-252017 was agreed as candidate content** for VOPS conformance, pending validation from companies
2. **TS 26.265 shall include references to repository tags** reflecting the status from each meeting
3. **Tags would provide traceability** of conformance material availability

### Current Problem

The current version of TS 26.265 fails to implement the agreed approach:
- No repository tags are present in the specification
- No reference to conformance material from SA4#134
- Lack of traceability between meeting decisions and repository content

## Proposals

The contribution proposes that SA4:

1. **Update the repository** to correctly reflect the agreed conformance material from the last meeting
2. **Add appropriate tags to TS 26.265** that reference the repository status
3. **Establish a process** to ensure future meeting outcomes are properly tagged in the repository
4. **Update the status** of candidate conformance content based on feedback from companies

## References

[1] S4-252017: [VOPS] On Conformance