W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

RE: [selection-api] Moving toward First Public Working Draft

From: Ben Peters <Ben.Peters@microsoft.com>
Date: Fri, 26 Sep 2014 17:28:10 +0000
To: Kenji Baheux <kenjibaheux@google.com>, Arthur Barstow <art.barstow@gmail.com>
CC: public-webapps <public-webapps@w3.org>, Ryosuke Niwa <rniwa@apple.com>
Message-ID: <423cb01201d1493794f3d098f417e179@BLUPR03MB437.namprd03.prod.outlook.com>
Yes, the spec is ready for that (major API areas and concepts should be covered).

From: Kenji Baheux [mailto:kenjibaheux@google.com]
Sent: Friday, September 26, 2014 1:45 AM
To: Arthur Barstow
Cc: public-webapps; Ryosuke Niwa; Ben Peters
Subject: Re: [selection-api] Moving toward First Public Working Draft

Publishing an FPWD sounds reasonable.

On Sat, Sep 20, 2014 at 9:52 PM, Arthur Barstow <art.barstow@gmail.com<mailto:art.barstow@gmail.com>> wrote:
Hi Ryosuke, Ben, Kenji, All,

I'm looking for feedback about moving the Selection API [ED] to First Public Working Draft (FPWD) ...

A `rule of thumb` I generally use when considering if a spec is ready for a FPWD is if the feature set is mostly complete although there is no expectation all features are fleshed out in detail (IOW, looking for breadth mostly complete but not depth). The breadth question is important because a FPWD is also used as an "attorney snapshot" vis-à-vis the [PP]. Regarding the spec's open [Issues], there is no expectation a FPWD be bug/issue free (in fact, it would be rare if that was the case).

What are your thoughts about publishing a FPWD? Do you consider the latest ED to be feature complete; and if not, what major features are missing?

-Thanks, AB

[ED] http://w3c.github.io/selection-api/

[Issues] https://github.com/w3c/selection-api/issues

[PP] http://www.w3.org/Consortium/Patent-Policy/

Product Manager - Chrome
Google Japan
Received on Friday, 26 September 2014 17:28:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:27 UTC