W3C home > Mailing lists > Public > public-html-media@w3.org > May 2016

WG Decision: MSE Candidate Recommendation "at risk" items

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Tue, 31 May 2016 12:56:53 +0000
To: "'public-html-media@w3.org'" <public-html-media@w3.org>
Message-ID: <CY1PR03MB14239C0600AD858D6FAE61B4EA460@CY1PR03MB1423.namprd03.prod.outlook.com>
> If there are no objections by Monday May 30, this resolution will carry.

Since there were no objections to this CfC, the resolution passes and we will add the entire VideoPlaybackQuality object to the "at risk" features of the next re-publications of MSE CR.

/paulc
HME WG Chair

-----Original Message-----
From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] 
Sent: Monday, May 23, 2016 6:36 PM
To: 'public-html-media@w3.org' <public-html-media@w3.org>
Subject: CfC: MSE Candidate Recommendation "at risk" items

The MSE and EME timeline [1] indicates that we are to finalize the MSE and EME "substantive change" V1 issues by June 9 and then publish Candidate Recommendation drafts in early July.

	Thu Jun 9: Last "substantive change"s [3] to MSE and EME
	Thu Jun 16: MSE Candidate Recommendation (CR) update; EME Working Draft update, CFC for EME and MSE CR (Jun 16-23)
	Tue Jun 28: EME and MSE transition to CR request
	Tue Jul  5: EME and MSE Candidate Recommendation publication

Currently there are 12 MSE V1 open issues [2]  and 13 EME V1 open issues [3].  In order to make as much progress as possible on these open V1 issues, the Editors are meeting F2F at the end of this week.  In addition, in order to help the Editors deliver by the June 9 date and to give us the maximum time to deal with more controversial issues I am proposing that we keep some items in the Candidate Recommendation but that we mark these items as being "at risk".  Marking an item "at risk" means that the HTML Media Extensions (HME WG) can decide to remove the item from our Proposed Recommendation without having to re-publish another Candidate Recommendation.

On May 3 we published a revised MSE Candidate Recommendation [4] which contains two "at risk" items:

	The following features are "at risk" and may be removed due to lack of implementation. 
		. totalFrameDelay http://www.w3.org/TR/2016/CR-media-source-20160503/#widl-VideoPlaybackQuality-totalFrameDelay
		. appendStream() http://www.w3.org/TR/2016/CR-media-source-20160503/#widl-SourceBuffer-appendStream-void-ReadableStream-stream-unsigned-long-long-maxSize

The second of these items is covered by the MSE open issue [5].

Since May 3, a new issue [6] has been opened to remove the entire VideoPlaybackQuality object and to move it to a separate document for further incubation.  We have subsequently received additional issues [7-8] that elaborate on [6].

Since we have several implementations of the currently specified VideoPlaybackQuality object and have received explicit requests for it to remain in the MSE specification, the HTML Media Extensions WG is issuing a Call for Consensus to add the VideoPlaybackQuality object to the current list of two "at risk" features when the next MSE Candidate Recommendation is published in early July.  This will permit discussion to continue on [6] and its related issues during the Candidate Recommendation phase when we will have the most implementation evidence to make a decision on this feature.

Silence will be taken to mean there is no objection, but positive responses are encouraged.  If there are no objections by Monday May 30, this resolution will carry.

/paulc
HTML Media Extensions WG Chair

[1] https://lists.w3.org/Archives/Public/public-html-media/2016May/0029.html
[2] https://github.com/w3c/media-source/milestones/V1
[3] https://github.com/w3c/encrypted-media/milestones/V1 
[4] http://www.w3.org/TR/2016/CR-media-source-20160503/
[5] https://github.com/w3c/media-source/issues/14  
[6] https://github.com/w3c/media-source/issues/69
[7] https://github.com/w3c/media-source/issues/76 
[8] https://github.com/w3c/media-source/issues/77 
Received on Tuesday, 31 May 2016 12:57:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 31 May 2016 12:57:25 UTC