On 7/5/06 3:31 PM, "James Holderness" <[EMAIL PROTECTED]> wrote:
>> <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 type="text/html" rel="alternate" href="http://example.org/FooPu >> blish/Docs/Errors/283.html"/> > > This is cool if the server wants to produce nice comprehensive error > messages, but what if they just want to do something simple? They can't just > include an atom:title element, because RFC4287 requires either an > atom:content element or an alternate link, neither of which can really be > regarded as "simple". atom:summary is defined as a construct to hold a summary of longer content, not as a container for brief/simple content. If there is no long-form content, there being instead just a short message, surely that would be what would go into atom:content. Like this: <title>DB Error</title> <content type="text">couldn't connect to the DB server</content> Very brief content. No atom:[EMAIL PROTECTED]'alternate' required. No atom:summary required. e.
