W3C home > Mailing lists > Public > public-media-annotation@w3.org > September 2011

our own status code 562 in HTTP ...

From: Thierry MICHEL <tmichel@w3.org>
Date: Thu, 22 Sep 2011 17:09:23 +0200
Message-ID: <4E7B4FA3.5090706@w3.org>
To: Yves Lafon <ylafon@w3.org>, "public-media-annotation@w3.org" <public-media-annotation@w3.org>
Yves,

Today during the call of the Request for a Transition to CR: API for 
Media Resources 1.0
http://www.w3.org/2008/WebVideo/Annotations/drafts/API10/CR/


The Director has rejected the Transition due to the MAWG response to the 
following comment sent during Last Call: use of HTTP 501
http://lists.w3.org/Archives/Public/public-media-annotation/2011Aug/0031.html

The MAWG response:
http://lists.w3.org/Archives/Public/public-media-annotation/2011Sep/0043.html
------------

We have discussed this issue during the 12th Face-to-Face meeting and 
agreed that the 501 status code does not fit our needs. In order to have 
a clear semantic, we have decided to declare our own status code, as 
follows:
- Numerical Code: 562
- Textual description: Property not supported
- Example: only a subset of GET methods for properties implemented

---------------------------------

as defined in our API spec
http://www.w3.org/2008/WebVideo/Annotations/drafts/API10/CR/Overview.html#api-status-codes



The Director said that we should have your agreement Yves, as HTTP spec 
editor, for this declaration of our own status code 562.

This is not part of the main HTTP 1.1 protocol, are there guidelines 
anywhere for implementing proprietary HTTP error codes?
If you agree we can proceed the Transition.

Or would you suggest another solution ?

We must solve this issue before moving the API spec forward.

Thanks for your help,

Thierry.
Received on Thursday, 22 September 2011 15:09:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 September 2011 15:09:49 GMT