RE: [selection-api] Moving toward First Public Working Draft
Yes, the spec is ready for that (major API areas and concepts should be covered). From: Kenji Baheux [mailto:kenjibah...@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 mailto:art.bars...@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/ -- Kenji BAHEUX Product Manager - Chrome Google Japan
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 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/ > > -- Kenji BAHEUX Product Manager - Chrome Google Japan
Re: [selection-api] Moving toward First Public Working Draft
On 9/22/14 3:55 PM, Ryosuke Niwa wrote: I think the latest documentation is pretty complete except it’s missing one major feature: selection.modify [1]. There was a discussion that took place in WHATWG [2] and there was a disagreement on the use case and the purpose of this particular API among UA implementors. I can add that note to the specification for completeness before FPWD is published for the patent protection purposes. OK, please do. Shortly, I'll start the CfC for FPWD. -Thanks, ArtB [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=9514 [2] http://lists.w3.org/Archives/Public/public-whatwg-archive/2011Mar/0297.html
Re: [selection-api] Moving toward First Public Working Draft
On Sep 20, 2014, at 5:52 AM, Arthur Barstow 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? I think the latest documentation is pretty complete except it’s missing one major feature: selection.modify [1]. There was a discussion that took place in WHATWG [2] and there was a disagreement on the use case and the purpose of this particular API among UA implementors. I can add that note to the specification for completeness before FPWD is published for the patent protection purposes. [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=9514 [2] http://lists.w3.org/Archives/Public/public-whatwg-archive/2011Mar/0297.html - R. Niwa
