Tim Bray wrote:
On Mar 24, 2006, at 3:32 PM, James M Snell wrote:
1. MUST should be SHOULD
2. Rather than "the representation", it should be something like "an
Atom Entry document as it would appear in the collection's feed".
I agree about the representation, but why not MUST? It's a simple
enough rule. -Tim
I agree. Should (equivocation) needs a stronger argument.
[[[
If the server includes a body in the response, the body MUST be the
representation of the newly-created resource.
]]]
This echoes the HTTP spec in that a) all entities are representations
and b) the spec starts with "If", which is reasonably interpreted as MAY
- ergo no new design constraints have been added (and as an editor I
won't see the point of adding this text).
Presumably we want to constrain that a) an entity is always returned, b)
it's an Atom thingy.
cheers
Bill
