This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Right now the spec is a bit contorted when it comes to Put and Create. It talks about using the coming XML (or empty XML) as the new representation of the resource. And then in a separate paragraph talks about doing schema validation. This could be misread to imply that you MUST update/create the resource with an invalid representation - or that we have two conflicting MUSTs. We need to fix the text to make it clear that the incoming XML should be checked against the representation's allowable schema(s) and only be updated if it passes that test (assuming of course schema validation checking is done at all - which is optional). a proposal should be coming soon...
Agreed that support for empty resources are not required
Created attachment 949 [details] a proposal Made it clear that an empty constructor is just a request to create an empty resource, and not something that MUST be supported. Both Put and Create had similar text - so I aligned them since they same concept applies to both.
Created attachment 950 [details] proposal #2 New proposal based on Gil's suggested wording tweak
Created attachment 952 [details] Proposal I like with the general direction of the proposal attached to comment #3. I suggest the following additions. In the description of wst:Put/wst:Representation and wst:Create/wst:Representation, I suggest adding "If an implementation does not support the case where this element has no children, it MUST generate a wst:InvalidRepresentation fault". The revised proposal is attached.
Created attachment 956 [details] #3
resolved as proposed in comment 5