Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebCodecs registration policy #426

Closed
chrisn opened this issue Dec 17, 2021 · 3 comments · Fixed by #693
Closed

WebCodecs registration policy #426

chrisn opened this issue Dec 17, 2021 · 3 comments · Fixed by #693
Labels
PR exists A PR has been submitted that addresses this issue registry pertains to new or updated registry entry

Comments

@chrisn
Copy link
Member

chrisn commented Dec 17, 2021

In the last Media WG meeting we talked about criteria for adding new WebCodecs registrations. @aboba suggested:

  1. Specification required. This could be a reference to a specification published by an SDO, or a website (e.g. VP9). There may be some stability requirement (e.g. a reference to a personal github may not qualify). The specification should be available at least to the designated Expert Reviewer.
  2. Expert review required. The expert could be one of the spec editors, or someone designated by the WG Chairs. The idea is to designate someone to review the proposal and produce a written review with a recommendation (with the reasoning behind it), posted to the WG mailing list.
  3. WG discussion. The WG (and the submitter) should have the opportunity to respond to the expert review.
  4. Consensus determination. The WG Chairs determine whether the Expert review has consensus or not.
@dalecurtis dalecurtis added the registry pertains to new or updated registry entry label Mar 16, 2023
@aboba
Copy link
Collaborator

aboba commented Mar 16, 2023

@dalecurtis Can we close this?

@dalecurtis
Copy link
Contributor

We now have a VideoFrameMetadata registry.

@chrisn
Copy link
Member Author

chrisn commented Mar 16, 2023

This issue was about clarifying codec registrations, and we haven't updated the registry requirements based on these suggestions.

The main differences I see are:

(1) A stability requirement for the codec specification
(2) An explicit expert review step (e.g., as part of step 5 of the requirements). I note that this is where we had difficulty with the proposed H.263 registration
(3) WG discussion is implied in step 5 by "If the Media Working Group reaches consensus", but this doesn't currently require discussion with the submitter if they are not a Media WG member

The other points may be already sufficiently covered:

(1) Step 1 already requires a link to a public specification
(4) Consensus determination is mentioned in step 5, and covered by the WG charter

We could prepare a PR to change the registry document, the main thing needing input would be whether we want to include a stability requirement, and - if we do - how it should be formulated.

@chrisn chrisn reopened this Mar 16, 2023
@chrisn chrisn added the PR exists A PR has been submitted that addresses this issue label Jun 23, 2023
@aboba aboba closed this as completed in #693 Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR exists A PR has been submitted that addresses this issue registry pertains to new or updated registry entry
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants