From f0dc7496b44fd6820c391c68e3816e8ee65506ce Mon Sep 17 00:00:00 2001 From: Chris Needham Date: Fri, 23 Jun 2023 17:22:37 +0100 Subject: [PATCH 1/2] Add to codec registry requirements Changes: - Adds a requirement for a public specification that is stable - The WG may consult external expertise as part of its review - Fixes the numbering in the source document --- codec_registry.src.html | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/codec_registry.src.html b/codec_registry.src.html index bc684625..52a142d9 100644 --- a/codec_registry.src.html +++ b/codec_registry.src.html @@ -45,7 +45,7 @@ ================================================================== 1. Each entry must include a unique codec string, a common name string, and a - link to a public specification. + link to a stable public specification. 2. The codec string must be crafted as follows: 1. If the codec string contains a fixed prefix with variable suffix values, the suffix must be represented by an asterisk and the registration's @@ -62,17 +62,19 @@ 3. {{AudioDecoderConfig}} or {{VideoDecoderConfig}} description bytes 4. Expectations for {{EncodedAudioChunk}} or {{EncodedVideoChunk}} {{EncodedVideoChunk/[[type]]}} -3. Where applicable, a registration specification may include a section +4. Where applicable, a registration specification may include a section describing extensions to {{VideoEncoderConfig}} or {{AudioEncoderConfig}} dictionaries. -4. Candidate entries must be announced by filing an issue in the +5. Candidate entries must be announced by filing an issue in the [WebCodecs GitHub issue tracker](https://github.com/w3c/webcodecs/issues/) so they can be discussed and evaluated for compliance before being added to - the registry. If the Media Working Group reaches consensus to accept the - candidate, a pull request should be drafted (either by editors or by the - party requesting the candidate registration) to register the candidate. The - registry editors will review and merge the pull request. -5. Existing entries cannot be deleted or deprecated. They may be changed after + the registry. The Media Working Group may seek expertise from outside the + Working Group as part of its evaluation, e.g., from the codec specification + editors or relevant standards group. If the Working Group reaches consensus + to accept the candidate, a pull request should be drafted (either by editors + or by the party requesting the candidate registration) to register the + candidate. The registry editors will review and merge the pull request. +6. Existing entries cannot be deleted or deprecated. They may be changed after being published through the same process as candidate entries. Possible changes include expansion of the codec string to better qualify the codec, adjustments to the codec name string, and modification of the link to the From 46e8e1684a0aa24e3015d27f0f2dc16ec51981ae Mon Sep 17 00:00:00 2001 From: Chris Needham Date: Thu, 6 Jul 2023 12:21:39 +0100 Subject: [PATCH 2/2] Remove stable from codec registry requirements --- codec_registry.src.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/codec_registry.src.html b/codec_registry.src.html index 52a142d9..f322f6ce 100644 --- a/codec_registry.src.html +++ b/codec_registry.src.html @@ -1,7 +1,7 @@ 
 Title: WebCodecs Codec Registry
 Repository: w3c/webcodecs
-Status: NOTE-ED
+Status: DRY
 Shortname: webcodecs-codec-registry
 Level: none
 Group: mediawg
@@ -45,7 +45,7 @@
 ==================================================================
 
 1. Each entry must include a unique codec string, a common name string, and a
-    link to a stable public specification.
+    link to a public specification.
 2. The codec string must be crafted as follows:
     1. If the codec string contains a fixed prefix with variable suffix values,
         the suffix must be represented by an asterisk and the registration's