|
31 | 31 | Registration Entry Requirements {#registration-entry-requirements}
|
32 | 32 | ==================================================================
|
33 | 33 |
|
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, |
35 | 35 | and has the following requirements:
|
36 | 36 | 1. Each metadata entry is defined as a separate {{VideoFrameMetadata}}
|
37 | 37 | dictionary member.
|
38 | 38 | 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 |
43 | 45 | WebCodecs GitHub issue tracker so they can be discussed and evaluated for
|
44 | 46 | compliance before being added to the registry. If the Media Working Group
|
45 | 47 | reaches consensus to accept the candidate, a pull request should be drafted
|
46 | 48 | (either by editors or by the party requesting the candidate registration)
|
47 | 49 | to register the candidate. The registry editors will review and merge the
|
48 | 50 | 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 | + |
49 | 58 |
|
50 | 59 | VideoFrameMetadata members {#videoframemetadata-members}
|
51 | 60 | ========================================================
|
|
0 commit comments