CfC: publish LCWD of File API; deadline October 22

All - this is a Call for Consensus to publish a Last Call Working Draft 
of the File API spec <http://dev.w3.org/2006/webapi/FileAPI/>. Note bug 
17125 ([1] below) is open and Arun proposes it be postponed for v.next. 
Additionally, Arun notes below bug 19554 ([2] below) is a related 
feature request for HTML and he proposes the LC comment period be used 
to gather input on that bug.

This CfC satisfies the group's requirement to "record the group's 
decision to request advancement" for this LCWD. Note the Process 
Document states the following regarding the significance/meaning of a LCWD:

[[
http://www.w3.org/2005/10/Process-20051014/tr.html#last-call

Purpose: A Working Group's Last Call announcement is a signal that:

* the Working Group believes that it has satisfied its relevant 
technical requirements (e.g., of the charter or requirements document) 
in the Working Draft;

* the Working Group believes that it has satisfied significant 
dependencies with other groups;

* other groups SHOULD review the document to confirm that these 
dependencies have been satisfied. In general, a Last Call announcement 
is also a signal that the Working Group is planning to advance the 
technical report to later maturity levels.
]]

The proposed LC review period is 4 weeks.

If you have any comments or concerns about this CfC, please send them to 
public-webapps@w3.org by October 22 at the latest. Positive response is 
preferred and encouraged and silence will be considered as agreement 
with the proposal.

-Thanks, AB

-------- Original Message --------
Subject: 	Re: [admin] Publishing specs before TPAC: CfC start deadline 
is Oct 15
Date: 	Tue, 16 Oct 2012 17:29:17 -0700
From: 	ext Arun Ranganathan <aranganathan@mozilla.com>
To: 	Arthur Barstow <art.barstow@nokia.com>
CC: 	<public-webapps@w3c.org>


----- Original Message -----
> On 10/9/12 4:13 PM, ext Arun Ranganathan wrote:
> > On Sep 26, 2012, at 10:27 AM, Arthur Barstow wrote:
> >
> >> * File API - Arun can you get this spec ready for LC by October
> >> 15?
> >
> > Yes.
>
> ATM, File API has 8 open bugs [1].


I've rationalized these down to 2 bugs.

1. Bug 17125[1] is a feature that we should mark v.next; it calls for the ability to retroactively "unselect" an erroneous selection that is present in FileList.  I don't think this is a pressing feature.

2. Bug 19554[2] is a spec. request feature in WHATWG/HTML5, especially useful for autoRevoke semantics for Blob URLs.  I'm not sure whether autoRevoke is at risk because of this bug, since implementations have shown that stable state (what the spec. uses now) is problematic for autoRevoke.  But I'll let this be discussed in LC commentary or in upcoming TPAC discussions.

>P.S. Dom's WebIDL checker reports a bug in the Blob constructor

Thanks for catching that :)  I think that particular bug is fixed.

And I'm sorry this is a day late (e.g. not ready by Oct. 15).  I've gotten it PubReady, using a "push out" date of Oct. 18.  Hope that works:
http://dev.w3.org/2006/webapi/FileAPI/


-- A*

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17125
[2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=19554

Received on Wednesday, 17 October 2012 01:30:06 UTC