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

Call for Consensus to Publish First Public Working Draft of FindText API completed with support and no objections

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Wed, 14 Oct 2015 16:05:57 -0400
Message-Id: <B9221EB6-24F2-4AC9-B748-87F77D2A72A7@fjhirsch.com>
To: W3C Public Annotation List <public-annotation@w3.org>, public-webapps <public-webapps@w3.org>
Given support on the Web Annotation WG/Web Apps public mailing lists for publishing a FPWD of the FindText API, and no objections this CfC has concluded successfully in support of publishing a FPWD of the FindText API. (We've also had support in discussions on the teleconferences)

There were some questions asked that will be dealt with as the Working Groups work through questions related to this API, such as Shadow DOM, but this should not preclude FPWD publication.

On behalf of the Web Annotation WG chairs I declare consensus to publish.

(I will not speak for the Web Platform chairs, but there were no objections on the WebApps list that I saw, perhaps they can confirm that this CfC is completed successfully from their point of view as well).

regards, Frederick

on behalf of myself and Rob Sanderson, Web Annotation WG Co-Chairs

www.fjhirsch.com
@fjhirsch


> On Oct 6, 2015, at 4:32 PM, 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
> 
> 
> 
> 
> 
Received on Wednesday, 14 October 2015 20:06:29 UTC

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