Re: [charter] What is the plan for Streams API?
On Mon, Aug 10, 2015 at 2:07 PM, Arthur Barstow art.bars...@gmail.com wrote: Given Takeshi's status it seems premature to speculate. 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. [TR] http://www.w3.org/TR/streams-api/ So what are the requirements for getting something in the charter? If we don't even know what a given draft might contain, how can folks review the charter? -- https://annevankesteren.nl/
Re: [charter] What is the plan for Streams API?
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. 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. -AB [TR] http://www.w3.org/TR/streams-api/
Re: [charter] What is the plan for Streams API?
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 On Tue, Aug 4, 2015 at 11:13 PM, Arthur Barstow art.bars...@gmail.com mailto:art.bars...@gmail.com wrote: 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. -Thanks, AB
Re: [charter] What is the plan for Streams API?
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? -- https://annevankesteren.nl/
Re: [charter] What is the plan for Streams API?
+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 On Tue, Aug 4, 2015 at 11:13 PM, Arthur Barstow art.bars...@gmail.com wrote: 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. -Thanks, AB
