Re: CfC: Publish WebCodecs codec registrations

I support publication of the WebCodecs codec registrations as proposed.

> Does this call for consensus cover that switch?

My preference would be to go ahead and publish as-is, then switch later.
This is a shorter path to fix the broken links in our codec registry (which
is pretty confusing for spec readers). After this we can move to registry
track (currently blocked by tooling).

On Thu, Nov 18, 2021 at 9:52 AM Francois Daoust <fd@w3.org> wrote:

> For WebCodecs codec registrations specs, I note that publication here
> means publication as First Public Working Draft, and that these specs
> are intended to become Working Group Notes.
>
> Boilerplate and pubrules got updated with the switch to Process 2021 and
> automated publication fails for the time being (I'll look into it next
> week), but the Codec Registry and AVC Codec registration spec are
> already setup for automated publication, and so they get republished as
> Working Draft whenever the Editor's Draft is updated.
>
> For the WebCodecs Codec Registry spec, we talked about switching to the
> Registry track now that Process 2021 is in place. Does this call for
> consensus cover that switch? One practical impact is that, as opposed to
> Notes, registries do get reviewed by the Advisory Committee (review
> starts when spec gets published as a Candidate Registry), and a call for
> wide review needs to be issued.
>
> Thanks,
> Francois.
>
>
>
>
>
> ------ Original message ------
> From: "Chris Needham" <chris.needham@bbc.co.uk>
> To: "public-media-wg@w3.org" <public-media-wg@w3.org>
> Date: 18/11/2021 12:10:24
>
> >Dear all,
> >
> >
> >
> >This is a call for consensus to publish a set of WebCodecs codec
> >registrations.
> >
> >
> >
> >The current Editor's Drafts are available at:
> >
> >
> >
> >* https://w3c.github.io/webcodecs/aac_codec_registration.html
> ><https://w3c.github.io/webcodecs/aac_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/alaw_codec_registration.html
> ><https://w3c.github.io/webcodecs/alaw_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/av1_codec_registration.html
> ><https://w3c.github.io/webcodecs/av1_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/flac_codec_registration.html
> ><https://w3c.github.io/webcodecs/flac_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/mp3_codec_registration.html
> ><https://w3c.github.io/webcodecs/mp3_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/opus_codec_registration.html
> ><https://w3c.github.io/webcodecs/opus_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/pcm_codec_registration.html
> ><https://w3c.github.io/webcodecs/pcm_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/ulaw_codec_registration.html
> ><https://w3c.github.io/webcodecs/ulaw_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/vorbis_codec_registration.html
> ><https://w3c.github.io/webcodecs/vorbis_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/vp8_codec_registration.html
> ><https://w3c.github.io/webcodecs/vp8_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/vp9_codec_registration.html
> ><https://w3c.github.io/webcodecs/vp9_codec_registration.html>
> >
> >
> >
> >The following documents will also be republished:
> >
> >
> >
> >* https://w3c.github.io/webcodecs/avc_codec_registration.html
> ><https://w3c.github.io/webcodecs/avc_codec_registration.html>
> >
> >* https://w3c.github.io/webcodecs/codec_registry.html
> ><https://w3c.github.io/webcodecs/codec_registry.html>
> >
> >
> >
> >The CfC will last for two weeks, ending on 2nd December. Please reply
> >
> >to this email and state one of the following:
> >
> >
> >
> >* I support publication of the WebCodecs codec registrations as
> >proposed
> >
> >
> >
> >* I object to publication of the WebCodecs codec registrations (please
> >detail your concerns)
> >
> >
> >
> >Many thanks,
> >
> >
> >
> >Chris (for the Media WG co-chairs)
> >
>
>
>