From 04597ef07fd7430ef277627971360c400ba5fb3c Mon Sep 17 00:00:00 2001 From: Chris Needham Date: Fri, 21 Oct 2022 18:24:12 +0100 Subject: [PATCH 1/3] Add requirements to metadata registry definition Covers adding, changing, and deprecating registry entries --- video_frame_metadata_registry.src.html | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/video_frame_metadata_registry.src.html b/video_frame_metadata_registry.src.html index d29db69a..f00ddc21 100644 --- a/video_frame_metadata_registry.src.html +++ b/video_frame_metadata_registry.src.html @@ -30,21 +30,30 @@ Registration Entry Requirements {#registration-entry-requirements} ================================================================== -A registration entry is a document describing one or several metadata entry, +A registration entry is a document describing one or several metadata entries, and has the following requirements: 1. Each metadata entry is defined as a separate {{VideoFrameMetadata}} dictionary member. 2. Each metadata entry must be serializable. -3. Each metadata must be defined by a W3C specification and have clearly defined semantics. - In particular, its interactions with the media processing pipeline - (encoders, decoders, renderers, etc.) should be well defined. -4. A candidate registration entry must be announced by filing an issue in the +3. Each metadata entry must be defined by a W3C specification that has + reached consensus in the originating Working Group. +4. Each metadata entry must have clearly defined semantics. In particular, + its interactions with the media processing pipeline (encoders, decoders, + renderers, etc.) should be well defined. +5. A candidate registration entry must be announced by filing an issue in the WebCodecs GitHub issue tracker 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. +6. Existing entries may be changed after being published, through the same + process as candidate entries. Possible changes include modification of + the link to the public specification. +7. Existing entries may be deprecated. This requires Media Working Group + consensus, and if still active, consensus of the Working Group that + originated the registration entry specification. + VideoFrameMetadata definition {#videoframemetadata-definition} ============================================================= From 4a000c74326a8b6d453e6e8a7cffdbe54840685a Mon Sep 17 00:00:00 2001 From: Chris Needham Date: Mon, 24 Oct 2022 12:54:41 +0100 Subject: [PATCH 2/3] Clarify metadata entry requirements --- video_frame_metadata_registry.src.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/video_frame_metadata_registry.src.html b/video_frame_metadata_registry.src.html index f00ddc21..8b102407 100644 --- a/video_frame_metadata_registry.src.html +++ b/video_frame_metadata_registry.src.html @@ -37,9 +37,9 @@ 2. Each metadata entry must be serializable. 3. Each metadata entry must be defined by a W3C specification that has reached consensus in the originating Working Group. -4. Each metadata entry must have clearly defined semantics. In particular, - its interactions with the media processing pipeline (encoders, decoders, - renderers, etc.) should be well defined. +4. The specification defining each metadata entry must provide clearly defined + semantics. In particular, its interactions with the media processing + pipeline (encoders, decoders, renderers, etc.) should be well defined. 5. A candidate registration entry must be announced by filing an issue in the WebCodecs GitHub issue tracker so they can be discussed and evaluated for compliance before being added to the registry. If the Media Working Group From 409ada01b962e63502c4c63f92fcff396b2b3d14 Mon Sep 17 00:00:00 2001 From: Chris Needham Date: Mon, 24 Oct 2022 12:57:35 +0100 Subject: [PATCH 3/3] Clarify metadata entry requirements --- video_frame_metadata_registry.src.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/video_frame_metadata_registry.src.html b/video_frame_metadata_registry.src.html index 8b102407..9fe49d10 100644 --- a/video_frame_metadata_registry.src.html +++ b/video_frame_metadata_registry.src.html @@ -38,8 +38,8 @@ 3. Each metadata entry must be defined by a W3C specification that has reached consensus in the originating Working Group. 4. The specification defining each metadata entry must provide clearly defined - semantics. In particular, its interactions with the media processing - pipeline (encoders, decoders, renderers, etc.) should be well defined. + semantics. In particular, interactions with the media processing pipeline + (encoders, decoders, renderers, etc.) should be well defined. 5. A candidate registration entry must be announced by filing an issue in the WebCodecs GitHub issue tracker so they can be discussed and evaluated for compliance before being added to the registry. If the Media Working Group