Revise codec registration entry requirements

[marcoscaceres]

Updated registration entry requirements for codec strings and specifications.

Based on last week's discussion on the WG's teleconference: https://www.w3.org/2026/01/13-mediawg-minutes.html#74c6

Process and Requirements Clarifications:

• Expanded the registration process to require filing an issue in the WebCodecs GitHub tracker, discussion and evaluation by the Media Working Group, and consensus before submitting a pull request.
• Clarified that the codec specification must be made available to the Working Group,
• At least one implementer must be interested.
• Updated and clarified the requirements for registration entries, including the need for a unique codec string, a common name, and a link to a public registration specification.
• Clarified the required and optional sections for each registration's specification, including recognized codec strings, internal data, config description bytes, and possible extensions to encoder/decoder configuration dictionaries.
• Simplified and clarified the process for merging accepted entries, and reiterated that existing entries cannot be deleted or deprecated, but may be changed through the same process.

[Copilot]

Pull request overview

This PR revises the codec registration entry requirements based on a working group teleconference discussion. It reorganizes the registration process to be more procedural and improves document structure.

Changes:

• Reorganized registration requirements to present the process flow upfront before listing technical requirements
• Changed terminology from "public specification" to "registration specification" for consistency
• Improved table accessibility by converting bold text in <td> elements to proper <th> elements within <thead> sections

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chrisn]

Based on discussion in https://lists.w3.org/Archives/Public/public-media-wg/2026Jan/0005.html.