Re: Your comments on Device Description Repository Simple API ( LC-1951)

 Dear Rotan Hanrahan ,

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/D5306DC72D165F488F56A9E43F2045D3018B1053@FTO.mobileaware.com
 2. http://www.w3.org/TR/2008/WD-DDR-Simple-API-20080404/


=====

Your comment on 4.4 Exceptions:
> In the DDR Simple API Exceptions:
> 
>   http://www.w3.org/TR/2008/WD-DDR-Simple-API-20080404/#sec-exceptions
> 
> several integer values are defined to represent status or cause of
> exceptions. The following numbers are observed (in the following
> order):
> 
> 500, 400, 65536, 300, 100, 800, 200, 900, 600, 10000.
> 
> On behalf of our development team, here is a question relating to
> these
> integers:
> 
> Are these integer values intended to be unique across all of the DDR
> Simple API exception classes? If so, then implementations that extend
> the API will require guidance on the choice of custom integer values
> for
> exception codes. Such extensions are anticipated in the text of
> section
> 4.4.
> 
> Proposed remedy:
> 
> State in the specification that exception codes below "some number"
> are
> reserved for this and future editions of this specification, and that
> numbers above "some number" are recommended for custom implementations
> that extend this specification.
> 
> On behalf of MobileAware Ltd, Development Team,
> 
> Dr Rotan Hanrahan
> Chief Innovations Architect
> MobileAware


Working Group Resolution (LC-1951):
The API permits codes whose value is IMPLEMENTATION_ERROR+1 or higher to
be used for implementation-specific purposes. These are the only code
values that are permitted for such purposes. This information, already
mentioned, addresses the comment. Guidance on the choice of values within
the indicated range is out of scope for the API. The group resolves not to
change the text.

----

Received on Thursday, 29 May 2008 15:55:10 UTC