RE: RfC: Service Workers and "Portable Web Publications for the Open Web Platform"

2015-10-07 Thread Siegman, Tzviya - Hoboken 
Hi Jake,

Thanks for the offer.  The DPUB IG meets on Mondays at 11:00 EDT/15:00 UTC. We 
would be very happy to have you at our 19 October meeting [1] to discuss 
Service Workers in the context of the Portable Web Publications for the Open 
Web Platform [2].

Markus and I will copy you when we send the agenda.

I will speak with some DPUB-ers who especially interested in Service Workers 
about their availability to attend the Web Apps meeting on Monday and I’ll be 
in touch shortly. Thank you for the offer.

[1] 
http://www.timeanddate.com/worldclock/fixedtime.html?msg=DPUB+IG+meeting=20151019T11=43
[2] http://w3c.github.io/dpub-pwp/

Best,
Tzviya

Tzviya Siegman
Digital Book Standards & Capabilities Lead
Wiley
201-748-6884
tsieg...@wiley.com

From: Jake Archibald [mailto:jakearchib...@google.com]
Sent: Monday, October 05, 2015 12:37 PM
To: public-digipub...@w3.org; public-webapps; Alex Russell; Jungkee Song
Cc: Siegman, Tzviya - Hoboken
Subject: Re: RfC: Service Workers and "Portable Web Publications for the Open 
Web Platform"

On Mon, 5 Oct 2015 at 13:00 Arthur Barstow 
> wrote:
The IG welcomes discussion and feedback during their October 19
conference call (if interested, please contact Tzviya) and/or during
TPAC.

I'm happy to take part in this from a service worker point of view, if 
timezones add up. What time is it?

Although WebApps meets on Monday and Tuesday and the IG meets on
Thursday and Friday, if there is interest in a joint meeting, my
understanding is that some set of IG members can meet during WebApps'
meeting (see agenda at [3] for open slots).

I'm happy to attend either of IG meets, and I intend to be at the the WebApps 
meeting on Monday.

Happy to meet informally too!

Alex, Jake, Jungkee - perhaps you could meet with some of the IG members
during the October 27 Service Worker meeting. WDYT?

I think we're already over subscribed on the 27th, would meeting on the dates 
around that be enough? Happy to make time on evenings if need be.

Re: Reminder regarding normative references

2015-10-07 Thread Mike West 
On Wed, Oct 7, 2015 at 9:30 AM, Steve Faulkner 
wrote:

> hi mike, i think you will find your example is in the W3C HTML 5.1:
>
> http://www.w3.org/TR/html51/webappapis.html#creation-url
>
> not saying there aren't other examples that would be concrete.
>

I am pleasantly surprised!

I assume this means that I ought to be reference HTML 5.1 and not 5 in
whatever snapshots WebAppSec produces?

-mike

Re: Reminder regarding normative references

2015-10-07 Thread Steve Faulkner 
On 7 October 2015 at 08:15, Mike West  wrote:

> As a concrete example, I'm going to send a transition request for Secure
> Contexts shortly. It uses the "creation URL" concept which was recently
> added to WHATWG's HTML (
> https://html.spec.whatwg.org/multipage/webappapis.html#creation-url).
> That concept is not present in the W3C's HTML (nor is it clear to me how to
> get it added :) ). How do you suggest that we proceed?
>

hi mike, i think you will find your example is in the W3C HTML 5.1:

http://www.w3.org/TR/html51/webappapis.html#creation-url

not saying there aren't other examples that would be concrete.

--

Regards

SteveF
Current Standards Work @W3C

Re: Reminder regarding normative references

2015-10-07 Thread Mike West 
On Wed, Oct 7, 2015 at 12:44 AM, Wendy Seltzer  wrote:

> A reminder that has come up in some recent transition calls: When moving
> a spec to Candidate Recommendation, we look to see that the normative
> references are to documents of equivalent stability[1] -- ideally, also
> CR, if they're W3C documents. So if you're moving a document forward,
> it's a good idea to look periodically at the references and ping the
> other working groups where those are being developed to make sure that
> dependencies are moving at the pace we need. (This also helps to satisfy
> the "wide review" requirements.)
>

A corollary to this is that "stability" should be balanced against
"accuracy". That is, http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt
is pretty stable, but we ought not reference it today, as it doesn't
represent what browsers are doing.

What do you/the director/his delegates suggest that we do if we'd like to
reference concepts that aren't yet present in W3C specifications?

As a concrete example, I'm going to send a transition request for Secure
Contexts shortly. It uses the "creation URL" concept which was recently
added to WHATWG's HTML (
https://html.spec.whatwg.org/multipage/webappapis.html#creation-url). That
concept is not present in the W3C's HTML (nor is it clear to me how to get
it added :) ). How do you suggest that we proceed?

+public-webapps, as I believe specs like Service Worker have similar
problems (and, in this case, the exact same problem).

-mike

[Bug 14828] Import Hixie's tests?

2015-10-07 Thread bugzilla 
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14828

Arthur Barstow  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||art.bars...@gmail.com
 Resolution|--- |MOVED

--- Comment #3 from Arthur Barstow  ---
This bug has been duplicated as
https://github.com/w3c/web-platform-tests/issues/2230

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 15279] Update WebSockets tests to remove support for MozWebSocket

2015-10-07 Thread bugzilla 
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15279

Ms2ger  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

2015-10-07 Thread Ivan Herman 
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






signature.asc
Description: Message signed with OpenPGP using GPGMail

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

2015-10-07 Thread Robert Sanderson 
+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

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

2015-10-07 Thread Raphaël Troncy 

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]).


+1 for publishing this document as FPWD but one clarification request: 
the original "Robust Anchoring" had a wide scope covering various types 
of documents while the FindText API document focuses on textual 
documents. Would there be another "umbrella document" produced by the 
Working Group that would refer to various specifications to perform 
robust anchoring on various type of documents, such as listing the 
FindText API, the CSV fragment RFC 7111, the Media Fragments API, etc. ?

Best regards.

  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/

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

2015-10-07 Thread Doug Schepers 

Hi, Raphaël–

Yes, this is one narrowly-scoped piece of generalized functionality that 
we hope can get broad agreement and implementation.


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.


Regards–
–Doug

On 10/7/15 11:56 AM, Raphaël Troncy 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]).


+1 for publishing this document as FPWD but one clarification request:
the original "Robust Anchoring" had a wide scope covering various types
of documents while the FindText API document focuses on textual
documents. Would there be another "umbrella document" produced by the
Working Group that would refer to various specifications to perform
robust anchoring on various type of documents, such as listing the
FindText API, the CSV fragment RFC 7111, the Media Fragments API, etc. ?
Best regards.

   Raphaël

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

2015-10-07 Thread 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/