Re: [streams-api] Seeking status of the Streams API spec

The MSE spec doesn't reference the updated version of the spec. I
intentionally pinned it to the Nov 05, 2013 version of that spec so that we
didn't have broken references while the Streams spec was being reworked.

I have been chatting with Domenic about how to integrate the new Streams
APIs with MSE. I'm still trying to digest the whole spec and I'm trying to
come up with a proposal that will fit naturally in with the direction that
spec is going.

At this point it may just be better to remove appendStream() and its
related algorithms from the MSE spec since I don't believe any other
browser is going to implement the old Streams API. I can then file a bug to
track work on adding support for the new Streams API. In my opinion, that
is the best way to track the reality of the current situation.

Aaron

On Thu, Oct 23, 2014 at 10:46 AM, Jerry Smith (WINDOWS) <
jdsmith@microsoft.com> wrote:

> Separate from heartbeat publication, we don't believe it is appropriate to
> directly reference this spec in MSE until some questions are answered about
> how streams will be represented.
>
> Jerry
>
> -----Original Message-----
> From: David Singer [mailto:singer@apple.com]
> Sent: Thursday, October 23, 2014 6:26 AM
> To: chaals@yandex-team.ru
> Cc: Paul Cotton; Takeshi Yoshino; Jerry Smith (WINDOWS); public-webapps;
> public-html-media@w3.org
> Subject: Re: [streams-api] Seeking status of the Streams API spec
>
>
> On Oct 23, 2014, at 15:10 , chaals@yandex-team.ru wrote:
>
> > - annevk@, feras.moussa@, domenic@, acolwell@, art.barstow@
> >
> > 23.10.2014, 15:06, "Arthur Barstow" <art.barstow@gmail.com>:
> >> On 10/22/14 6:27 PM, Paul Cotton wrote:
> >>>>  given the magnitude of the changes in [changeset], a new WD should
> >>>> be
> >>>  published.
> >>>
> >>>  Can we please wait until after the TPAC week to publish the
> >>> proposed  Streams heartbeat? Given the substantive changes being
> >>> made here I  think it would be best to have a WebApps WG discussion
> >>> as proposed by  Art [1] BEFORE publishing such a heartbeat.
> >>
> >> I think the draft WD captures the recent developments and discussions
> >> (certainly much better than the previous WD) so I prefer to go ahead
> >> with the publication and if there are any issues, bugs, etc., they
> >> should be raised
> >
> > Seconded. Note there is no reason not to raise the topic in discussion
> at TPAC, with the two drafts available for comparison.
> >
> > Working Drafts do not reflect consensus...
>
> well, they do and they don't
>
> editor's drafts do not reflect consensus of any kind
>
> working drafts (roughly) reflect where the WG thinks it is, not all of
> which is done or has consensus (in terms of content), but it does have
> consensus that the draft reflects the WG's current 'best thinking'
>
>
> >
> > cheers
> >
> > --
> > Charles McCathie Nevile - web standards - CTO Office, Yandex
> > chaals@yandex-team.ru - - - Find more at http://yandex.com
> >
>
> David Singer
> Manager, Software Standards, Apple Inc.
>
>
>