On May 1, 2006, at 10:50 PM, James M Snell wrote:

The problem here is that application/atom+xml can be used to identify
both Atom Feed Documents and Atom Entry Documents.  There is no way of
differentiating the two based solely on the media type.  If I said
<accept>application/atom+xml</accept>, I'd basically be saying that
clients could post either of the two document types to the collection,
which would be incorrect.

Well, do we envision a scenario in which you'd post an atom:feed to an APP end-point? So why don't we just say in the APP spec "application/atom+xml" means it accepts Atom Entry docs? And if they did, couldn't you just return code 409 or 415? -Tim


- James


Reply via email to