W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2015

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

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Thu, 8 Oct 2015 11:50:39 -0400
Cc: Ivan Herman <ivan@w3.org>, W3C Public Annotation List <public-annotation@w3.org>, public-webapps <public-webapps@w3.org>
Message-Id: <D304BF5C-2846-4C68-8FE8-A627593B88A4@fjhirsch.com>
To: Robert Sanderson <azaroth42@gmail.com>
+1 to FPWD of FindText API

> On Oct 7, 2015, at 11:38 AM, Robert Sanderson <azaroth42@gmail.com> wrote:
> 
> +1 to FPWD
> 
> On Wed, Oct 7, 2015 at 8:34 AM, Ivan Herman <ivan@w3.org> wrote:
> I am happy to have this documents published as FPWD.
> 
> Ivan
> 
> 
> > On 06 Oct 2015, at 22:32 , Frederick Hirsch <w3c@fjhirsch.com> 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/0000-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
Received on Thursday, 8 October 2015 15:51:20 UTC

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