W3C home > Mailing lists > Public > public-ldp-wg@w3.org > October 2012

Re: Adressing more error cases ?

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Mon, 01 Oct 2012 16:10:04 +0100
Message-ID: <5069B24C.2080205@epimorphics.com>
To: public-ldp-wg@w3.org
I think this is an issue worth adding to the issues list.

SPARQL-WG had a comment asking for defined error responses over and 
above HTTP Status code and message.  e.g. query parse error details - be 
more helpful to the end user than "400 Bad Request".

A brief search of existing practice showed no common community approach 
(even of status code) and decided to do nothing about it due to time 
pressures and also not wanting to create a SPARQL-specific solution. It 
was recognized as a valid feature request though.


On 28/09/12 15:41, Olivier Berger wrote:
> Hi.
> I have the impression that the current status of the editor's draft
> mainly tells how to perform right, but not so much what to do in other
> cases.
> For instance, I see very few mentions of HTTP error codes.
> Do we intend to explicitely cover error conditions like insufficient
> privileges or wrong formats, or incorrect syntax for methods
> invocations, or is it already covered by existing specs ?
> Just wondering if this is intentionally missing as out of scope or needs
> to be addressed.
> Thanks in advance.
> Best regards,
Received on Monday, 1 October 2012 15:10:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:32 UTC