|
1 | 1 | <pre class='metadata'> |
2 | 2 | Title: WebCodecs Codec Registry |
3 | 3 | Repository: w3c/webcodecs |
4 | | -Status: NOTE-ED |
| 4 | +Status: DRY |
5 | 5 | Shortname: webcodecs-codec-registry |
6 | 6 | Level: none |
7 | 7 | Group: mediawg |
|
62 | 62 | 3. {{AudioDecoderConfig}} or {{VideoDecoderConfig}} description bytes |
63 | 63 | 4. Expectations for {{EncodedAudioChunk}} or {{EncodedVideoChunk}} |
64 | 64 | {{EncodedVideoChunk/[[type]]}} |
65 | | -3. Where applicable, a registration specification may include a section |
| 65 | +4. Where applicable, a registration specification may include a section |
66 | 66 | describing extensions to {{VideoEncoderConfig}} or {{AudioEncoderConfig}} |
67 | 67 | dictionaries. |
68 | | -4. Candidate entries must be announced by filing an issue in the |
| 68 | +5. Candidate entries must be announced by filing an issue in the |
69 | 69 | [WebCodecs GitHub issue tracker](https://github.com/w3c/webcodecs/issues/) |
70 | 70 | so they can be discussed and evaluated for compliance before being added to |
71 | | - the registry. If the Media Working Group reaches consensus to accept the |
72 | | - candidate, a pull request should be drafted (either by editors or by the |
73 | | - party requesting the candidate registration) to register the candidate. The |
74 | | - registry editors will review and merge the pull request. |
75 | | -5. Existing entries cannot be deleted or deprecated. They may be changed after |
| 71 | + the registry. The Media Working Group may seek expertise from outside the |
| 72 | + Working Group as part of its evaluation, e.g., from the codec specification |
| 73 | + editors or relevant standards group. If the Working Group reaches consensus |
| 74 | + to accept the candidate, a pull request should be drafted (either by editors |
| 75 | + or by the party requesting the candidate registration) to register the |
| 76 | + candidate. The registry editors will review and merge the pull request. |
| 77 | +6. Existing entries cannot be deleted or deprecated. They may be changed after |
76 | 78 | being published through the same process as candidate entries. Possible |
77 | 79 | changes include expansion of the codec string to better qualify the codec, |
78 | 80 | adjustments to the codec name string, and modification of the link to the |
|
0 commit comments