Re: Call for Consensus: Publication of an updated Working Draft of Content-Hints

I support publishing the current content-hints draft as a Working Draft

On Thu, Feb 27, 2020 at 8:01 AM Harald Alvestrand <harald@alvestrand.no>
wrote:

> I support publishing the current draft at the "next level of stability".
>
>
> WD publication is fine, and I'm looking forward to getting it to CR.
>
>
> On 2/20/20 6:03 PM, Bernard Aboba wrote:
>
> This is a Call for Consensus (CfC) to push the editor's draft of Content-Hints, https://w3c.github.io/mst-content-hint/ out as a new Working Draft.
>
> The CfC will last for one week, and will end on Friday, February 28, 2020
> at 16:00 UTC
>
> In response, please state one of the following:
>
>    - I support publishing the current content-hints draft as a Working
>    Draft
>    - I object to publishing the current content-hints draft as a Working
>    Draft, due to issues filed in open bug <#number>.
>
> Bernard, for the Chairs
>
> Explanation
>
> Since the last CfC for a Content-Hints WG Draft
> <https://lists.w3.org/Archives/Public/public-webrtc/2019Jul/0066.html>
> (which went out on July 24, 2019), the specification has been revised.
> Changes include:
>
>    - Clarification of the behavior in various specifications triggered by
>    content-hint values, to address the following issues:
>       - https://github.com/w3c/mst-content-hint/issues/28
>       - https://github.com/w3c/mst-content-hint/issues/29
>       - https://github.com/w3c/mst-content-hint/issues/30
>
>       - Moving degradationPreference from WebRTC-PC to content-hints.
>    This was the subject of a previous CfC:
>    https://lists.w3.org/Archives/Public/public-webrtc/2019Oct/0087.html
>
>