On 4/5/06 7:50 PM, "Toru Marumoto" <[EMAIL PROTECTED]> wrote:
> HTTP/1.x 500 Internal Server Error > Content-Type: application/xml > > <error>couldn't connect to the DB server.</error> > > Could we standardized this? > I've amused myself with thoughts along the lines of something like this: ------------------------------------------------ HTTP/1.x 500 Internal Server Error Content-Type: application/atom+xml <?xml version="1.0" encoding="utf-8"?> <entry xmlns="http://www.w3.org/2005/Atom";> <title>Internal Server Error</title> <summary>couldn't connect to the DB server.</summary> <content type="html">[long winded explanation or trace log]</content> <link href="http://example.org/FooPublish/Docs/Errors/283.html"/> <category scheme="http://w3c.org/http/errors/"; term="500" label="Internal Server Error" /> <category scheme="http://example.com/FooPublish/"; term="error-283" label="DB connect failed" /> <generator uri="http://www.example.com/FooPublisher"; version="1.0">Foo Publisher 1.0</generator> <author><name>Foo Publisher</name></author> <id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id> <updated>2003-12-13T18:30:02Z</updated> </entry> ------------------------------------------------ What's particularly interesting is the capability of progressive disclosure of error details (title, summary, content), links to online documentation (rel=alternate), links to online support (rel=related), identification of the software involved (atom:generator), and the potential of having the error categorised according to various popular schemas (which might or might not be useful for automated error handling). e.
