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

I also support publishing the current content-hints draft as a Working Draft.
________________________________
From: Carlos N Reina <cnreina@gmail.com>
Sent: Thursday, February 20, 2020 8:29 PM
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Subject: [EXTERNAL] 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

Carlos N Reina
801-477-4138
cnreina@gmail.com

On Feb 20, 2020, at 10:06, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:



This is a Call for Consensus (CfC) to push the editor's draft of Content-Hints, https://w3c.github.io/mst-content-hint/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fmst-content-hint%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C9002421b5d9045f861a108d7b686ac3a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637178562592339864&sdata=RB41gD8schI1jylFG6denR5gR7kRu1u7YeSLZD9Tufo%3D&reserved=0> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-webrtc%2F2019Jul%2F0066.html&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C9002421b5d9045f861a108d7b686ac3a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637178562592339864&sdata=uDBtpIejf4mRIWMUEJV%2BjTtREX2i29XollLs6FXdqYA%3D&reserved=0> (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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fmst-content-hint%2Fissues%2F28&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C9002421b5d9045f861a108d7b686ac3a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637178562592349816&sdata=8Y4db2AIVd9Gcelcpe0bV5XUgBb8EkLsVjT4qXz0iK8%3D&reserved=0>
     *   https://github.com/w3c/mst-content-hint/issues/29<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fmst-content-hint%2Fissues%2F29&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C9002421b5d9045f861a108d7b686ac3a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637178562592349816&sdata=3tLQcSQMrZM2suQFUZKol%2FdhJxLdfa0xN6XDP5k0EsE%3D&reserved=0>
     *   https://github.com/w3c/mst-content-hint/issues/30<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fmst-content-hint%2Fissues%2F30&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C9002421b5d9045f861a108d7b686ac3a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637178562592359768&sdata=JhJAt3AKL5E%2FcBQPAVKdt%2BEg2mPNQPK7yoebyM%2BuBFk%3D&reserved=0>

  *   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

<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-webrtc%2F2019Oct%2F0087.html&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C9002421b5d9045f861a108d7b686ac3a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637178562592359768&sdata=jyX0fAW9nLmhCQa%2Fy3JO9r8vVd9NVPe0eZMUBR6qVO0%3D&reserved=0>