Re: Proposal to close ISSUE-19: Adressing more error cases, as is

**ISSUE-19 Addressing more error cases**

I agree that this is an overly broad issue; but feel a need for more
clarification regarding HTTP status codes that may or may not be
appropriate for this specification.

Coming from a framework with clearly defined exceptions, I am still
not clear on what the appropriate HTTP status codes should be for
typical exceptions encountered with each particular HTTP Method
invocation. Should there be ISSUES requesting enumeration of [common]
HTTP status/error code (ranges?) for each particular HTTP Method, or
is it sufficient to say that any LDP HTTP Method invocation may return
any HTTP status code?

These are the HTTP status codes:
https://www.iana.org/assignments/http-status-codes/http-status-codes.xml


**re: "Problem Details for HTTP APIs"**

There are defined JSON and XML representations of
https://tools.ietf.org/html/draft-nottingham-http-problem-03 , which
specifies a Problem Details JSON Object and a Problem Details XML
Object.

In order for https://tools.ietf.org/html/draft-nottingham-http-problem-03
to be applicable to LDP, there must be a Turtle representation.


**HTTP-in-RDF**

HTTP-in-RDF may also be useful for (re-)specifying HTTP status codes
and reason Phrases in response to agent inputs, app stack errors,
exceptions, and application logic.

http:StatusCode -- http://www.w3.org/TR/HTTP-in-RDF/#StatusCodeClass
  http:statusCodeNumber --
http://www.w3.org/TR/HTTP-in-RDF/#statusCodeNumberProperty
  http:statusCodeValue --
http://www.w3.org/TR/HTTP-in-RDF/#statusCodeValueProperty

http:reasonPhrase -- http://www.w3.org/TR/HTTP-in-RDF/#reasonPhraseProperty


**An Application Perspective**

* http://www.w3.org/wiki/LDP_Implementations
* http://cwe.mitre.org/data/definitions/209.html
* https://github.com/Pylons/pyramid/blob/master/pyramid/exceptions.py
* https://github.com/Pylons/pyramid/blob/master/pyramid/httpexceptions.py
* https://github.com/Pylons/pyramid/blob/master/pyramid/interfaces.py


--
Wes Turner
http://linkedin.com/in/westurner

Received on Monday, 3 June 2013 19:09:47 UTC