RE: PROPPATCH responses

What's the semantics behind the PROPPATCH response.?

One propstat per subcommand of propertyupdate?
Or one per property?

I'm asking for the sake of future subcommands like insert that might partially
update a property.  The question still applies though but is somewhat of a
redherring in the current state of the spec.  That is, the current spec seems to
allow a request to set/delete a property multiple times, but this doesn't seem
like something folks/clients would do.  Especially due to the ambiguity of the
response one would get back.


Also is the following PROPPATCH response valid?  Note... all the href's specify
the same URI.

<?xml version="1.0" encoding="UTF-8"?>
 <D:multistatus xmlns:D="DAV:">
  <D:response>
   <D:href>http://amarillo.watson.ibm.com:8080/rdest.tmp.txt</D:href>

<D:propstat><D:prop><D:getlastmodified>1999-06-12T18:55:10-04:00</D:getlastmodified></D:prop>

    <D:status>HTTP/1.1 403 Forbidden</D:status>
   </D:propstat>
  </D:response>
  <D:response>
   <D:href>http://amarillo.watson.ibm.com:8080/rdest.tmp.txt</D:href>
   <D:propstat><D:prop><D:supportedlock/></D:prop>
    <D:status>HTTP/1.1 403 Forbidden</D:status>
   </D:propstat>
  </D:response>
  <D:response>
   <D:href>http://amarillo.watson.ibm.com:8080/rdest.tmp.txt</D:href>
   <D:propstat><D:prop><D:getcontentlength/></D:prop>
    <D:status>HTTP/1.1 403 Forbidden</D:status>
   </D:propstat>
  </D:response>
  <D:response>
   <D:href>http://amarillo.watson.ibm.com:8080/rdest.tmp.txt</D:href>
   <D:propstat><D:prop><D:creationdate/></D:prop>
    <D:status>HTTP/1.1 403 Forbidden</D:status>
   </D:propstat>
  </D:response>
 </D:multistatus>

------------------------------------------
Phone: 914-784-7569,   ccjason@us.ibm.com