Re: Why MD5 Headers are Imperative

Here's the server-side resource, no "representation" to it, this is the whole 
enchilada:

http://canuck.bisonsystems.net/dev/atom/entry-server-2.xml

Here's the client-side, writable representation retrieved by an APP client:

http://canuck.bisonsystems.net/dev/atom/entry-server-2.xml

Here's the read-only representation with eTag=atom:id+atom:updated for the 
majority of use cases, which are read-only and do not even see the <p/> tag:

http://canuck.bisonsystems.net/dev/atom/entry-server-3.xml

In my implementation, editors can move that <p/> tag around all they want 
without altering the published read-only representation, provided an Atom-
friendly publishing protocol...

Go back to my first post.  All other conversations aside, this is why I'm 
here despite my desire to have remained an anonymous lurker.  I'm still 
working this out myself, but I think I've nailed down the basic contradiction.

-EJB