For what it's worth, I support publishing content-hints as a working draft. It has been implemented and is currently in use (for the purpose of optimizing application screen-sharing). Previously, we had used degradationPreference for a similar purpose, but found it was less general, since it applied only to encoding in WebRTC, but not to other APIs such as MediaStream Recording. ________________________________ From: Bernard Aboba Sent: Wednesday, July 24, 2019 8:18 AM To: public-webrtc@w3.org <public-webrtc@w3.org> Subject: Call for Consensus (CfC): Publish an updated Working Draft of content-hints Our present Working Draft of content-hints is published as <https://www.w3.org/TR/webrtc-stats/> https://www.w3.org/TR/2018/WD-mst-content-hint-20180703/, is almost exactly 1 year old. The spec has evolved significantly over the course of a year. Thus: This is a Call for Consensus to push the editors' draft, https://w3c.github.io/mst-content-hint/, out as a new Working Draft. The CfC will last for one week, and end on Wednesday, July 31, at 16:00 UTC In response, please state one of the following: - I support publishing the current content-hints as a Working Draft - I object to publishing the current content-hints as a Working Draft, due to issues filed in open bug <#number>. Bernard, for the chairsReceived on Thursday, 1 August 2019 20:54:10 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:48 UTC