On Jun 14, 2006, at 6:15 PM, Jeffrey Winter wrote:
So again, analogous to the way "text/xml" implies that whitespace between attributes need not conserved, the definition of "application/atom+xml" could imply that atom:id values may not be conserved (as well as anything else that the spec may state explicitly.)
Isn't the real problem here that the ID is somewhat bound to the origin server that owns a given entry? IOW, does a standalone atom entry make sense? If it does not, it is propably the wrong thing to use as a payload anyhow. After all, the server not only acts as a store of entries, it also manages them.
What about using POST instead of PUT and have the server replace the entry data except for the ID?
Cheers, Jan
