W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2018

Move forward with 'Content Hints'

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 8 Mar 2018 13:17:19 +0000
To: WebRTC WG <public-webrtc@w3.org>
Message-ID: <HE1PR07MB34184EFA307DEE7D00F8226CC9DF0@HE1PR07MB3418.eurprd07.prod.outlook.com>
All,

the discussion at the last VI [1] (re-)confirmed that many see the need 
for an API surface that allows the app developer to tell (hint to) the 
UA what kind of content it is (or perhaps rather its characteristics). 
There were discussions on whether the API surface should be on the track 
or on the sink, and it was also said that it should be explained that 
using this API really means that the intent is to override the UA’s own 
classification of the content’s characteristics.

There is currently one written up proposal for this API surface, the 
“MediaStreamTrack Content Hints” document [2], which adds the API on the 
track. At the VI [1] there were also persons indicating they would 
prefer to have the surface on the sink, but we have not yet seen a 
concrete proposal for that.

In the interest of making progress we would like to see any alternative 
proposal (in some form, e.g. an email) before March 25th in order to be 
able to have a discussion comparing the different approaches.

If no alternative proposal surfaces we propose that the WG adopts [2] as 
an Editor’s Draft (which basically means it is moved to the 
https://github.com/w3c/ github space).

Stefan for the chairs

[1] https://www.w3.org/2018/02/21-webrtc-minutes#item02
[2] https://wicg.github.io/mst-content-hint/
Received on Thursday, 8 March 2018 13:18:24 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 March 2018 13:18:25 UTC