On 8/5/15 10:53 AM, Takeshi Yoshino wrote:

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


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:


    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

Reply via email to