- From: Florian Stegmaier <stegmai@dimis.fim.uni-passau.de>
- Date: Mon, 26 Sep 2011 11:52:02 +0200
- To: public-media-annotation@w3.org
Hi Thierry, Yes, i will elaborate this issue. Maybe it would be really good, to align to the WebDAV spec (if possible). I will send my findings tomorrow morning. Best. Florian Am 26.09.2011 um 08:13 schrieb Thierry MICHEL: > Florian, > > Could you please take a look at Yves's proposal > > We could dicuss it tomorrow during the MAWG telecon. > > Thierry. > > > > -------- Message original -------- > Sujet: Re: our own status code 562 in HTTP ... > Date : Sun, 25 Sep 2011 02:27:01 -0400 (EDT) > De : Yves Lafon <ylafon@w3.org> > Pour : Thierry MICHEL <tmichel@w3.org> > Copie à : public-media-annotation@w3.org <public-media-annotation@w3.org > > > > On Thu, 22 Sep 2011, Thierry MICHEL wrote: > >> 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 > > I'd like to understand clearly what is the intended meaning of this. > I noted as well a 462 "Property not defined in Source Format" which > seems > to be really a 404. > You should take a look at WebDAV, RFC4918 and the way they retrieve > properties <https://tools.ietf.org/html/rfc4918> . > > You should also take a look at RFC5988 for HTTP linking. > https://tools.ietf.org/html/rfc5988 > > > >> --------------------------------- >> >> 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. >> >> >> >> >> >> > > -- > Baroula que barouleras, au tiéu toujou t'entourneras. > > ~~Yves
Received on Monday, 26 September 2011 09:50:11 UTC