Priorities and expectations for 2012

Hi All,

I've been thinking a bit about realistic expectations for 2012 for those 
specs that are already in scope in the WG's current charter (complete 
spec list is at [PubStatus]).

Below is a list (in alphabetical order) of what I consider the WG's 
higher priority specs including my expectations for the new year and 
some related open tasks for the specs. One criteria for putting 
something on the list is the spec's relative maturity i.e. has at least 
one LC been published and/or is there already some implementation. 
Maturity level is relevant because the WG's IP commitments are not 
finalized until a spec reaches the Recommendation status.

* CORS (WD) - address open bugs; publish LCWD; create comprehensive test 
suite; this spec needs some tutorial/primer/how-to type documentation

* DOM 3 Events (LCWD) - complete LC#2 comment processing; publish new 
LCWD; if clear implementation commitment from at least Mozilla and 
Microsoft, move the spec to CR

* File API (WD) - address open bugs; integrate Microsoft's Stream API 
features <http://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm>; 
move to feature complete and publish LCWD; start test suite

* Indexed Database API (WD) - move to feature complete and publish LCWD 
(comment period is likely to be relatively long and/or multiple LCWDs 
are published)

* Server-sent Events (WD) - address open bugs; publish LCWD when Zarro 
Boogs; publish CR by 2H-2012

* Web IDL (LCWD) - complete LC#2 comment processing; publish LC#3 in 
Jan/Feb 2012; publish CR by 2Q-2012

* Web Messaging (WD) - address open bugs; publish LCWD when Zarro Boogs; 
publish CR by 2H-2012

* Web Sockets (CR) - complete the test suite; test Implementations 
against the test suite to meet the CR exit criteria

* Web Storage (CR) - start and complete the test suite; test 
Implementations against the test suite to meet the CR exit criteria

* Web Workers (WD) - address open bugs; publish LCWD when Zarro Boogs; 
publish CR by 2H-2012

Comments on the above are encouraged! Several of the specs above have no 
Test Facilitator and volunteers are welcome. Additionally, if you want 
to proactively push a spec forward, consider this an open request for 
bug fixes, test cases and whatever else needs to be done.

If a spec is not on the list, it does *not* mean the spec is not 
important. It just means the spec is still in the preliminary stages 
and/or I simply do not know what the Editor(s) and/or proponents are 
planning/expecting for 2012. As such, feedback on plans, etc. for the 
specs not listed above is also welcome.

Lastly, please don't interpret this e-mail as an attempt to "rush" our 
specs. That isn't my goal, although I am interested in everyone's frank 
feedback about realistic expectations for the new year.

-AB

[PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus#API_Specifications

Received on Friday, 23 December 2011 17:38:24 UTC