Re: Why MD5 Headers are Imperative

>
>All output representations, in HTML, XHTML, WAP, PDF or what-have-you, are 
>transformed using XSLTC in response to content negotiation.  So yes, we want 
>the Atom entry document to be as persistently cached as possible despite the 
>fact that no user of the system will ever receive an Atom representation of 
>the documents so managed.  Very real-world-today.
>

We could also decide, of course, to be all "Web 2.0" and stuff by assigning 
an .atom extension anyway so that, say, a County website could aggregate 
content from its constituent City's websites and there wouldn't be a <feed> 
in sight.  So please don't narrowly assume that "feed readers don't work like 
that" because I've never seen a spec for a "feed reader".

-EJB