Skip to content

Commit 779fe18

Browse files
committed
Add requirements to metadata registry definition
Covers adding, changing, and deprecating registry entries
1 parent 4644373 commit 779fe18

File tree

1 file changed

+14
-5
lines changed

1 file changed

+14
-5
lines changed

video_frame_metadata_registry.src.html

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -31,21 +31,30 @@
3131
Registration Entry Requirements {#registration-entry-requirements}
3232
==================================================================
3333

34-
A registration entry is a document describing one or several metadata entry,
34+
A registration entry is a document describing one or several metadata entries,
3535
and has the following requirements:
3636
1. Each metadata entry is defined as a separate {{VideoFrameMetadata}}
3737
dictionary member.
3838
2. Each metadata entry must be serializable.
39-
3. Each metadata must be defined by a W3C specification and have clearly defined semantics.
40-
In particular, its interactions with the media processing pipeline
41-
(encoders, decoders, renderers, etc.) should be well defined.
42-
4. A candidate registration entry must be announced by filing an issue in the
39+
3. Each metadata entry must be defined by a W3C specification that has
40+
reached consensus in the originating Working Group.
41+
4. Each metadata entry must have clearly defined semantics. In particular,
42+
its interactions with the media processing pipeline (encoders, decoders,
43+
renderers, etc.) should be well defined.
44+
5. A candidate registration entry must be announced by filing an issue in the
4345
WebCodecs GitHub issue tracker so they can be discussed and evaluated for
4446
compliance before being added to the registry. If the Media Working Group
4547
reaches consensus to accept the candidate, a pull request should be drafted
4648
(either by editors or by the party requesting the candidate registration)
4749
to register the candidate. The registry editors will review and merge the
4850
pull request.
51+
6. Existing entries may be changed after being published, through the same
52+
process as candidate entries. Possible changes include modification of
53+
the link to the public specification.
54+
7. Existing entries may be deprecated. This requires Media Working Group
55+
consensus, and if still active, consensus of the Working Group that
56+
originated the registration entry specification.
57+
4958

5059
VideoFrameMetadata members {#videoframemetadata-members}
5160
========================================================

0 commit comments

Comments
 (0)