- From: <rotan.hanrahan@mobileaware.com>
- Date: Thu, 29 May 2008 15:54:33 +0000
- To: José Manuel Cantera <jmcf@tid.es>
- Cc: public-ddwg-comments@w3.org
Dear José Manuel Cantera , The Mobile Web Initiative Device Description Working Group has reviewed the comments you sent [1] on the Last Call Working Draft [2] of the Device Description Repository Simple API published on 4 Apr 2008. Thank you for having taken the time to review the document and to send us comments! The Working Group's response to your comment is included below, and has been implemented in the new version of the document available at: http://www.w3.org/2005/MWI/DDWG/drafts/api/080529. Please review it carefully and let us know by email at public-ddwg-comments@w3.org if you agree with it or not before 9 June 2008. In case of disagreement, you are requested to provide a specific solution for or a path to a consensus with the Working Group. If such a consensus cannot be achieved, you will be given the opportunity to raise a formal objection which will then be reviewed by the Director during the transition of this document to the next stage in the W3C Recommendation Track. Thanks, For the Mobile Web Initiative Device Description Working Group, Matt Womer W3C Staff Contact 1. http://www.w3.org/mid/93AA9E47B82F684A868C217766F48905039F883386@EXCLU2K7.hi.inet 2. http://www.w3.org/TR/2008/WD-DDR-Simple-API-20080404/ ===== Your comment on 3 Vocabularies: > It could be good for the benefit of implementors, a clarification about > how vocabularies IRIs are going to be treated. > > Particularly things like case-sensitiveness could cause trouble > > Proposed amendment: Reference normatively XML Namespaces Spec and in > particular Section 2.3 of that spec Working Group Resolution (LC-1977): The issue of canonical representation of IRIs as strings is beyond the scope of the API. The specification indicates that the strings are representations of IRIs. Developers should seek elsewhere for guidance on such representations. The work of the W3C i18n group is one such source of guidance. The XML Namespace specification is already referenced in the API, and is another source of guidance. ----
Received on Thursday, 29 May 2008 15:55:12 UTC