Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

2015-10-08 Thread Frederick Hirsch
+1 to FPWD of FindText API

> On Oct 7, 2015, at 11:38 AM, Robert Sanderson  wrote:
> 
> +1 to FPWD
> 
> On Wed, Oct 7, 2015 at 8:34 AM, Ivan Herman  wrote:
> I am happy to have this documents published as FPWD.
> 
> Ivan
> 
> 
> > On 06 Oct 2015, at 22:32 , Frederick Hirsch  wrote:
> >
> > This is a call for consensus (CfC) to publish a First Public Working Draft 
> > (FPWD) of FindText API; deadline 14 October (1 week)
> >
> > This FindText API is joint deliverable of the WebApps WG and Web Annotation 
> > WG (listed as "Robust Anchoring" in the charters [1], [2]).
> >
> > This is a Call for Consensus (CfC) to publish a FPWD of the FindText API, 
> > using the following Editor's Draft as the basis:
> >
> > http://w3c.github.io/findtext/
> >
> > "This specification describes an API for finding ranges of text in a 
> > document or part of a document, using a variety of selection criteria."
> >
> > This API was presented to the WebApps WG last TPAC under a different name, 
> > and with a fairly different design; it was modified to fit the feedback 
> > from that meeting and from others, including narrowing of scope, the 
> > introduction of Promises, and exposing low-level functionality in the 
> > spirit of the Extensible Web.
> >
> > The specification is largely based on the Annotator JavaScript library's 
> > "robust anchoring" code, and a standalone polyfill is under development. 
> > Feedback from possible implementers is especially welcome.
> >
> > This CfC satisfies the group's requirement to "record the groups' decision 
> > to request advancement".
> >
> > By publishing this FPWD, the group sends a signal to the community to begin 
> > reviewing the document. The FPWD reflects where the groups are on this spec 
> > at the time of publication; it does _not_ necessarily mean there is 
> > consensus on the spec's contents and the specification may be updated.
> >
> > If you have any comments or concerns about this CfC, please reply to this 
> > e-mail by 14 October at the latest. Positive response is preferred and 
> > encouraged, even a +1 will do  Silence will be considered as agreement with 
> > the proposal.
> >
> > regards, Frederick & Rob
> >
> > Frederick Hirsch, Rob Sanderson
> >
> > Co-Chairs, W3C Web Annotation WG
> >
> > www.fjhirsch.com
> > @fjhirsch
> >
> > [1] http://www.w3.org/2014/06/webapps-charter.html#deliverables
> >
> > [2] http://www.w3.org/annotation/charter/#scope
> >
> >
> >
> >
> >
> >
> 
> 
> 
> Ivan Herman, W3C
> Digital Publishing Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/-0003-0782-2704
> 
> 
> 
> 
> 
> 
> 
> -- 
> Rob Sanderson
> Information Standards Advocate
> Digital Library Systems and Services
> Stanford, CA 94305

regards, Frederick

Frederick Hirsch
Chair, W3C Device APIs WG (DAP)

www.fjhirsch.com
@fjhirsch






Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

2015-10-08 Thread Ben De Meester
+1 to FPWD

Greetings,
Ben

Ben De Meester
Researcher Semantic Web
Ghent University - iMinds - Multimedia Lab | Faculty of Engineering and
Architecture | Department of Electronics and Information Systems
Gaston Crommenlaan 8 bus 201, B-9050 Ledeberg-Ghent, Belgium
t: +32 9 331 49 59 | e: ben.demees...@ugent.be | URL:
http://users.ugent.be/~bjdmeest/

2015-10-07 21:13 GMT+02:00 Raphaël Troncy :

> Hi Doug,
>
> It's just one of the building blocks of a full set of robust anchoring
>> features, some of which might be standardized, but which may actually be
>> done in script. We'll most likely gather together those pieces in the
>> sort of umbrella document you suggest… maybe something like "Mapping Web
>> Annotation Data Model Selectors to Client-side APIs" (or something more
>> pithy.
>>
>
> Thanks for the clarification, this is exactly what I had in mind. I was
> afraid that the "Robust Anchoring" deliverable defined in the charter was
> reduced to the "FindText API" (which is, between, absolutely necessary and
> useful) and I'm happy to read that there will be other documents produced.
>
>
>   Raphaël
>
> --
> Raphaël Troncy
> EURECOM, Campus SophiaTech
> Multimedia Communications Department
> 450 route des Chappes, 06410 Biot, France.
> e-mail: raphael.tro...@eurecom.fr & raphael.tro...@gmail.com
> Tel: +33 (0)4 - 9300 8242
> Fax: +33 (0)4 - 9000 8200
> Web: http://www.eurecom.fr/~troncy/
>
>