Skip to content

Update registry requirements #578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chrisn merged 1 commit into from
Dec 2, 2025
Merged

Update registry requirements #578

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 20 additions & 11 deletions format-registry/initdata/index-respec.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,22 +98,31 @@ <h2>Organization</h2>
<section id="entry-requirements">
<h2>Registration Entry Requirements</h2>
<ol>
<li><p>Each entry must include a unique [=initialization data type=] string.</p></li>
<li>
<p>Each entry must include a link that references a publicly available specification.
It is recommended that such a specification be made available without cost (other than reasonable shipping and handling if not available by online means).
</p>
Each entry must include a unique [=initialization data type=] string.
</li>
<li>
<p>Candidate entries must be announced by filing an issue in the
<a href="https://github.com/w3c/encrypted-media/issues/">Encrypted Media Extensions GitHub issue tracker</a>
so they can be discussed and evaluated for compliance before being added to
the registry.
</p>
Each entry must include a link that references a publicly available specification.
It is recommended that such a specification be made available without cost (other than reasonable shipping and handling if not available by online means).
</li>
<li><p>Per the [[[ENCRYPTED-MEDIA]]] specification, entries must be fully specified and support common formats such that instances of the format can be processed in a fully specified and compatible way.</p></li>
<li>
<p>Existing entries cannot be deleted or deprecated.</p>
Per the [[[ENCRYPTED-MEDIA]]] specification, entries must be fully specified and support common formats such that instances of the format can be processed in a fully specified and compatible way.
</li>
<li>
Candidate entries must be announced by filing an issue in the
<a href="https://github.com/w3c/encrypted-media/issues/">Encrypted Media Extensions GitHub issue tracker</a>
so they can be discussed and evaluated for compliance before being added to
the registry.
</li>
<li>
If the Media Working Group reaches consensus to accept the candidate,
a pull request should be drafted
(either by the registry editors or by the party requesting the candidate registration)
to register the candidate.
The registry editors will review and merge the pull request.
</li>
<li>
Existing entries cannot be deleted or deprecated.
</li>
</ol>
</section>
Expand Down
33 changes: 21 additions & 12 deletions format-registry/stream/index-respec.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,23 +98,32 @@ <h2>Organization</h2>
<h2>Registration Entry Requirements</h2>
<ol>
<li>
<p>Each entry must include a unique MIME-type/subtype pair. If the byte stream format is derived-from an existing file format, then it should use the MIME-type/subtype pairs typically used for the file format.</p>
Each entry must include a unique MIME-type/subtype pair. If the byte stream format is derived-from an existing file format, then it should use the MIME-type/subtype pairs typically used for the file format.
</li>
<li>
<p>Each entry must include a link that references a publicly available specification.
It is recommended that such a specification be made available without cost (other than reasonable shipping and handling if not available by online means).
</p>
Each entry must include a link that references a publicly available specification.
It is recommended that such a specification be made available without cost (other than reasonable shipping and handling if not available by online means).
</li>
<li>
<p>Candidate entries must be announced by filing an issue in the
<a href="https://github.com/w3c/encrypted-media/issues/">Encrypted Media Extensions GitHub issue tracker</a>
so they can be discussed and evaluated for compliance before being added to
the registry.
</p>
Per the [[[ENCRYPTED-MEDIA]]] specification, the media container for a stream format must not be encrypted.</li>
<li>
Per the [[[ENCRYPTED-MEDIA]]] specification, entries must be fully specified and support "common encryption" such that the content can decrypted in a fully specified and compatible way when a key or keys are provided.
<li>
Candidate entries must be announced by filing an issue in the
<a href="https://github.com/w3c/encrypted-media/issues/">Encrypted Media Extensions GitHub issue tracker</a>
so they can be discussed and evaluated for compliance before being added to
the registry.
</li>
<li>
If the Media Working Group reaches consensus to accept the candidate,
a pull request should be drafted
(either by the registry editors or by the party requesting the candidate registration)
to register the candidate.
The registry editors will review and merge the pull request.
</li>
<li>
Existing entries cannot be deleted or deprecated.
</li>
<li><p>Per the [[[ENCRYPTED-MEDIA]]] specification, the media container for a stream format must not be encrypted.</p></li>
<li><p>Per the [[[ENCRYPTED-MEDIA]]] specification, entries must be fully specified and support "common encryption" such that the content can decrypted in a fully specified and compatible way when a key or keys are provided.</p></li>
<li><p>Existing entries cannot be deleted or deprecated.</p></li>
</ol>
</section>

Expand Down
1 change: 0 additions & 1 deletion hdcp-version-registry-respec.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,6 @@ <h2>Registration Entry Requirements</h2>
to register the candidate.
The registry editors will review and merge the pull request.
</li>

<li>
Existing entries cannot be deleted or deprecated.
They may be changed after being published through the same process as candidate entries.
Expand Down