Re: CfC: Republish MSE and EME registry entries

I support publication of the proposed MSE and EME registries.

On Tue, Jun 18, 2024 at 2:29 PM Xiaohan Wang (王消寒) <xhwang@google.com>
wrote:

> I support publication of the MSE and EME registries and registrations as
> proposed.
>
>
>
> On Tue, Jun 18, 2024 at 10:21 AM Chris Needham <chris.needham@bbc.co.uk>
> wrote:
>
>> Thanks, that’s a good point. The changes are mostly procedural, e.g.,
>> document status, names of editors, fixing links where there are references
>> to other specs.
>>
>>
>>
>> Here are links to compare the latest drafts with those currently
>> published on /TR:
>>
>>
>>
>> MSE WebM Byte Stream Format (this one has a more substantial change):
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fmse-byte-stream-format-webm%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fmse-byte-stream-format-webm%2F
>>
>>
>>
>> MSE ISOBMFF Byte Stream Format
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fmse-byte-stream-format-isobmff%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fmse-byte-stream-format-isobmff%2F
>>
>>
>>
>> MSE MP2T Byte Stream Format
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fmse-byte-stream-format-mp2t%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fmse-byte-stream-format-mp2t%2F
>>
>>
>>
>> MSE MPEG Audio Byte Stream Format
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fmse-byte-stream-format-mpeg-audio%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fmse-byte-stream-format-mpeg-audio%2F
>>
>>
>>
>> EME CENC Init Data Format
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Feme-initdata-cenc%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fencrypted-media%2Fformat-registry%2Finitdata%2Fcenc.html
>>
>>
>>
>> EME Keyids Init Data Format
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Feme-initdata-keyids%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fencrypted-media%2Fformat-registry%2Finitdata%2Fkeyids.html
>>
>>
>>
>> EME WebM Init Data Format
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Feme-initdata-webm%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fencrypted-media%2Fformat-registry%2Finitdata%2Fwebm.html
>>
>>
>>
>> EME Common Encryption for ISOBMFF Stream Format
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Feme-stream-mp4%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fencrypted-media%2Fformat-registry%2Fstream%2Fmp4.html
>>
>>
>>
>> EME WebM Stream Format
>>
>>
>>
>>
>> https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Feme-stream-webm%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fencrypted-media%2Fformat-registry%2Fstream%2Fwebm.html
>>
>>
>>
>> Chris
>>
>>
>>
>> *From:* Xiaohan Wang (王消寒) <xhwang@google.com>
>> *Sent:* Tuesday, June 18, 2024 4:28 PM
>> *To:* Joey Parrish <joeyparrish@google.com>
>> *Cc:* Chris Needham <chris.needham@bbc.co.uk>; public-media-wg@w3.org
>> *Subject:* Re: CfC: Republish MSE and EME registry entries
>>
>>
>>
>> *External: *Think before clicking
>>
>> Hello Chris,
>>
>>
>>
>> Thank you for driving this work to move MSE/EME forward!
>>
>>
>>
>> One quick question. Is there a way to see what has been changed in these
>> registries? Or is this mostly a process change?
>>
>>
>>
>> Best,
>>
>> Xiaohan
>>
>>
>>
>> On Fri, Jun 14, 2024 at 9:45 AM Joey Parrish <joeyparrish@google.com>
>> wrote:
>>
>> I support publication of the MSE and EME registries and registrations as
>> proposed
>>
>>
>>
>>
>>
>> On Fri, Jun 14, 2024 at 9:01 AM Chris Needham <chris.needham@bbc.co.uk>
>> wrote:
>>
>> Dear all,
>>
>>
>>
>> The Media Source Extensions Byte Stream Format Registry, Encrypted Media
>> Extensions Initialization Data Format Registry, Encrypted Media Extensions
>> Stream Format Registry, and associated registry entries have not been
>> updated on w3.org/TR since 2016, which means they don’t reflect the
>> latest changes made to the Editor’s drafts.
>>
>>
>>
>> This is a call for consensus to (a) publish the following registries on
>> the W3C Registry Track [1]:
>>
>>
>>
>> * Media Source Extensions Byte Stream Format Registry
>>
>>    https://w3c.github.io/mse-byte-stream-format-registry/
>>
>>
>>
>> * Encrypted Media Extensions Initialization Data Format Registry
>>
>>
>> https://w3c.github.io/encrypted-media/format-registry/initdata/index.html
>>
>>
>>
>> * Encrypted Media Extensions Stream Format Registry
>>
>>
>> https://w3c.github.io/encrypted-media/format-registry/stream/index.html
>>
>>
>>
>> (b) publish the registry entries on the W3C Note Track [2]:
>>
>>
>>
>> * MSE Byte Stream Formats:
>>
>>   * https://w3c.github.io/mse-byte-stream-format-webm/
>>
>>   * https://w3c.github.io/mse-byte-stream-format-isobmff/
>>
>>   * https://w3c.github.io/mse-byte-stream-format-mp2t/
>>
>>   * https://w3c.github.io/mse-byte-stream-format-mpeg-audio/
>>
>>
>>
>> * EME Initialization Data Formats:
>>
>>   *
>> https://w3c.github.io/encrypted-media/format-registry/initdata/cenc.html
>>
>>   *
>> https://w3c.github.io/encrypted-media/format-registry/initdata/keyids.html
>>
>>   *
>> https://w3c.github.io/encrypted-media/format-registry/initdata/webm.html
>>
>>
>>
>> * EME Stream Formats:
>>
>>   * https://w3c.github.io/encrypted-media/format-registry/stream/mp4.html
>>
>>   *
>> https://w3c.github.io/encrypted-media/format-registry/stream/webm.html
>>
>>
>>
>> and (c) set up auto-publication, so changes to these documents also
>> update the published versions on w3.org/TR.
>>
>>
>>
>> The CfC will last for two weeks, ending on 28th Jun. Please reply to this
>> email and state one of the following:
>>
>>
>>
>> * I support publication of the MSE and EME registries and registrations
>> as proposed
>>
>>
>>
>> * I object to publication of the MSE and EME registries and registrations
>> (please detail your concerns)
>>
>>
>>
>> Many thanks,
>>
>>
>>
>> Chris (for the Media WG co-chairs)
>>
>>
>>
>> [1] https://www.w3.org/2023/Process-20231103/#registries
>>
>> [2] https://www.w3.org/2023/Process-20231103/#note-track
>>
>>

Received on Tuesday, 25 June 2024 18:47:57 UTC