- From: Marcos Caceres <marcosc@opera.com>
- Date: Mon, 8 Jun 2009 20:34:07 +0200
- To: Arthur Barstow <art.barstow@nokia.com>
- Cc: Arve Bersvendsen <arveb@opera.com>, public-webapps <public-webapps@w3.org>
2009/5/12 Arthur Barstow <art.barstow@nokia.com>: > Arve, Marcos, All, > > It would be helpful if we identified the open actions and issues that must be addressed before we can publish a LCWD of the A&E spec [1]. > > There are two Open Actions: > > Action 232 - Check the API spec for compliance with the Web IDL spec: > <http://www.w3.org/2008/webapps/track/actions/232> > > Action 290 - Review changes to HTML5 that may affect API and Events spec and propose a way forward: > <http://www.w3.org/2008/webapps/track/actions/290> > > There are a few Red Block issues and I think these two that must be addressed before LC: > > 1. Section 5.14 "ISSUE: do we need to do some kind of URI normalization to check for equivalency?": > <http://dev.w3.org/2006/waf/widgets-api/#the-hasfeature-method> > > 2. Normative References - This section will be completed as the document matures. > > Other than the above, what else must be done before we can publish a LCWD of the A&E spec? Need to sort out how Preferences work. Need to also define how read only preferences work (i.e., what happens when an author tries to set a preference that is read only). -- Marcos Caceres http://datadriven.com.au
Received on Monday, 8 June 2009 18:34:47 UTC