Re: Preparation of MSE Proposed Recommendation

>
> https://github.com/w3c/encrypted-media/issues/293

I think I'm missing some context. I don't understand how this is related to
w3c/media-source#83 or what the workaround is. It's also not clear whether
a ReSpec bug has been filed. I can fix the majority of the problems by
breaking the attribute markup, but fixing this will likely require a ReSpec
fix.

https://github.com/w3c/encrypted-media/issues/249

This is assigned to Philippe and appears to be related to the publishing
flow since I couldn't reproduce it locally.

On Fri, Aug 5, 2016 at 6:37 PM, Mark Watson <watsonm@netflix.com> wrote:

>
>
> On Aug 5, 2016, at 5:33 PM, Paul Cotton <Paul.Cotton@microsoft.com> wrote:
>
> This email enumerates work that I believe needs to be done before we can
> produce a final MSE Proposed Recommendation.  Please respond inline with
> your status updates.  If we can do this via email then maybe we can avoid
> having an Editor’s meeting on Tuesday.
>
>
>
> David:  There are a couple of items related to EME below.
>
>
>
> /paulc
>
>
>
> 1. At Risk Features
>
>
>
> > The appendStream feature is covered by ISSUE-14 [2].
>
> > The VideoPlaybackQuality and totalFrameDelay features are covered by
> ISSUE-69 [3].
>
> > The TrackDefault feature is covered by ISSUE-136 [5].
>
>
>
> Where do we stand in removing these features from the MSE Editors’ Draft:
>
> http://w3c.github.io/media-source/
>
>
>
> 2. Remaining V1Editorial issues
>
> https://github.com/w3c/media-source/milestone/5
>
>
>
> When will the last 4 V1Editorial issues we dealt with?
>
>
>
> Matt: Since we have seen no movement on the HTML 5.1 issue that is
> blocking MSE ISSUE-99, do we have a work around we can use WITHOUT any HTML
> 5.1 change?
>
> https://github.com/w3c/media-source/issues/99
>
> https://github.com/w3c/html/issues/550
>
>
>
> Mark: When are we going to finish the WebIDL work?
>
>
> I thought this was done. I don't think it has been merge yet - I'm waiting
> for someone to check the most recent changes.
>
>
>
> Matt and David: Given that Mark and Jerry are on vacation this coming
> week, can you take care of this so it does not block us?
>
> https://github.com/w3c/media-source/issues/83
>
> https://github.com/w3c/encrypted-media/issues/293
>
> https://github.com/w3c/encrypted-media/issues/249
>
>
>
> Matt: Can you close out ISSUE-45 using Jerry’s proposed change?
>
> https://github.com/w3c/media-source/issues/45
>
>
>
> 3.  Recent MSE issues with no milestone
>
>
>
> Matt: What do we plan to do with the following recent MSE issues?  Do any
> of these bugs block us from proceeding to PR?
>
> https://github.com/w3c/media-source/issues/137
>
> https://github.com/w3c/media-source/issues/124
>
> https://github.com/w3c/media-source/issues/110
>
> https://github.com/w3c/media-source/issues/104
>
>
>
> 4. MSE Testing results
>
>
>
> Philippe: Can you summarize our current MSE testing status?  Do we have
> enough evidence to proceed to PR?  What if anything do we need to do about
> Jean-Yves Avenard private email about MSE test results?
>
> https://lists.w3.org/Archives/Team/team-html-chairs/2016Aug/0001.html
>
>
>
> 5. MSE Registry
>
> Philippe:  Can you give an exact schedule for completing the EME and MSE
> Registry work?
>
> https://github.com/w3c/media-source/issues/74
>
> which depends on
>
> https://github.com/w3c/encrypted-media/issues/104
>
> https://github.com/w3c/encrypted-media/pull/213
>
>
>
> /paulc
>
>
>
> *From:* Paul Cotton [mailto:Paul.Cotton@microsoft.com
> <Paul.Cotton@microsoft.com>]
> *Sent:* Wednesday, August 3, 2016 6:40 PM
> *To:* 'public-html-media@w3.org' <public-html-media@w3.org>
> *Subject:* CfC: Handling of MSE Candidate Recommendation "at risk"
> features
>
>
>
> The HTML Media Extensions WG is issuing a Call for Consensus to determine
> how to handle the "at risk" features published in the most recent MSE
> Candidate Recommendation [1].
>
> This CfC proposes to remove ALL of the "at risk" features identified in
> [1] and they will NOT appear in the upcoming candidate Proposed
> Recommendation.
>
>         The following features are at risk and may be removed:
>
>                 . The appendStream method on the sourceBuffer object and
> algorithm steps that are used only by it.
>
>                 . The VideoPlaybackQuality object and the HTMLVideoElement
> Extensions that use it.
>
>                 . The totalFrameDelay attribute on the
> VideoPlaybackQuality object.
>
>                 . The TrackDefault object and its related objects,
> attributes, methods and algorithms, including: TrackDefaultList,
> SourceBuffer.trackDefaults, Default track language, Default track label,
> and Default track kinds.
>
> The appendStream feature is covered by ISSUE-14 [2].  The current CR text
> will be maintained in MSE VNext for further work and to await
> implementations of the Streams API and the associated parts of MSE.
>
>
>
> The VideoPlaybackQuality and totalFrameDelay features are covered by
> ISSUE-69 [3].  The current CR text will NOT appear in the initial MSE VNext
> and will be worked on in the Web Incubator Community Group [4].
>
>
>
> The TrackDefault feature is covered by ISSUE-136 [5].  The current CR text
> will be maintained in MSE VNext for further work and to await MSE
> implementations of this feature.
>
>
>
> Silence will be taken to mean there is no objection, but positive
> responses are encouraged.  If there are no objections by Wednesday Aug 10,
> this resolution will carry and we will proceed with the removal of the
> identified at risk features as we prepare the MSE Proposed Recommendation.
>
> /paulc
> HTML Media Extensions WG Chair
>
> [1] http://www.w3.org/TR/2016/CR-media-source-20160705/
>
> [2] https://github.com/w3c/media-source/issues/14
>
> [3] https://github.com/w3c/media-source/issues/69
>
> [4] https://wicg.github.io/media-playback-quality/
>
> [5]  https://github.com/w3c/media-source/issues/136
>
>
>
> Paul Cotton, Microsoft Canada
>
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>
> Tel: (425) 705-9596 Fax: (425) 936-7329
>
>
>
>