Arthur Barstow <art.bars...@gmail.com>, 2015-08-10 08:07 -0400: > Archived-At: <http://www.w3.org/mid/55c893e4.8050...@gmail.com> > > On 8/7/15 8:32 AM, Anne van Kesteren wrote: > >On Fri, Aug 7, 2015 at 1:56 PM, Arthur Barstow <art.bars...@gmail.com> wrote: > >>Given this status, and in the absence of other feedback, I think the Streams > >>API should remain in WebApps' charter (at least for now). Then later, the > >>work may proceed (if there is still agreement an additional API would be > >>useful); otherwise, if there is agreement to stop the work, the work can be > >>stopped (and a WG Note published). > >What would this additional API do? > > Given Takeshi's status it seems premature to speculate.
Given that Takeshi said: > I don't have bandwidth to maintain W3C version of the spec even briefly > currently... ...it seems we can’t actually claim to even have an active editor for the spec. And the https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm source hasn’t had any changes in more than 10 months, which was also when the https://www.w3.org/TR/streams-api/ WD was last updated. > The current [TR] is now mostly void of content although it might be good to > gut it even more as well as to add a clear note that indicates that work has > stopped and might not resume. On their own, the two facts that we lack of an active editor and that the ED hasn’t had any changes in more than 10 months would normally be more than sufficient grounds for moving the WD to Note right now, and to either completely gut the ED or just make its URL redirect to the upstream spec. But if we lack the collective will to go ahead and move that WD to Note now, and to do the right thing with the ED, then we should at least as soon as possible clearly mark both the WD and ED with big bold warnings saying “Do not use this for anything, do not link to it as if it were representative of current implementation plans.” or whatever. Because in the mean time we have some widely-read pages such as the one at https://dev.modern.ie/platform/status/streamsapi/ that are referencing the https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm document, and that thus are giving misleading information to people (including implementors who I’ve personally seen confused by it in discussions) about which spec it is that UAs are actually implementing (or planning on implementing). And experience tells us that’s never a good thing to have happening. —Mike Arthur Barstow <art.bars...@gmail.com>, 2015-08-07 07:56 -0400: > Archived-At: <http://www.w3.org/mid/55c49cf1.8040...@gmail.com> > > On 8/5/15 10:53 AM, Takeshi Yoshino wrote: > >+domenic > > > >We've recently finished the ReadableStream part of the spec and > >experimenting integration with the Fetch API. Most of the spec is still > >unstable. I don't have bandwidth to maintain W3C version of the spec even > >briefly currently... > > Hi Takeshi, All, > > Given this status, and in the absence of other feedback, I think the Streams > API should remain in WebApps' charter (at least for now). Then later, the > work may proceed (if there is still agreement an additional API would be > useful); otherwise, if there is agreement to stop the work, the work can be > stopped (and a WG Note published). > > -Thanks, AB Takeshi Yoshino <tyosh...@google.com>, 2015-08-05 23:53 +0900: > Archived-At: > <http://www.w3.org/mid/cah9hsjavzjhnb2s3hourfu0wsnuot38wmif8e+r6qc6xgre...@mail.gmail.com> > > +domenic > > We've recently finished the ReadableStream part of the spec and > experimenting integration with the Fetch API. Most of the spec is still > unstable. I don't have bandwidth to maintain W3C version of the spec even > briefly currently... > > Takeshi Arthur Barstow <art.bars...@gmail.com>, 2015-08-04 10:13 -0400: > Archived-At: <http://www.w3.org/mid/55c0c86d.9070...@gmail.com> > > On 7/30/15 8:46 AM, Arthur Barstow wrote: > ><http://w3c.github.io/charter-html/group-charter.html> > > The WebApps + HTML WG draft charter says the following about WebApps' > Streams API: > > [[ > Streams API <https://w3c.github.io/streams-api/> > An API for representing a stream of data in web applications. > ]] > > I believe the previously agreed "plan of record" for this spec was to create > an API on top of <https://streams.spec.whatwg.org/>. Is that still something > this group wants to do, and if so, who can commit to actually doing the > work, in particular: editing, implementation, and test suite? > > If we no longer have committed resources for doing the above tasks then this > spec should be removed from the draft charter. -- Michael[tm] Smith https://people.w3.org/mike
signature.asc
Description: Digital signature
