> 8.1 Creating resources with POST [...] > If the server includes a body in the response, the > entity MUST be an Atom Entry Document representing the newly-created > resource, equivalent to that which would appear in the collection's feed > document.
Why the MUST for the format? If the response body is optional (a good thing), then the client will already know how to handle the case when it doesn't get an Atom Entry back. Why can't it apply that logic to the reception of other formats? This severely limits extensibility for no gain, AFAICT. I think "MAY" is plenty, as it calls out a useful scenario. Even "SHOULD" seems overkill. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
