Aaron,My open question: What does one do with a patch document that describes actions on multiple resources? Should we leave it assumed that this just doesn't make sense in the HTTP context? Or does it make sense, if, say, the resource of the PATCH method maps to a directory and the patch document applies to several files within that directory? In that case, does anything need to be said about the behavior of PATCH for this type of patch? Here I think the draft is pretty specific: The PATCH method affects the resource identified by the Request-URI, and also MAY have side effects on other resources; i.e., new resources may be created, or existing ones modified, by the application of a PATCH. So to me that says, 'yeah, patch might monkey with groups of files'. It's left to the server to decide whether that's allowed. I would imagine this would be based on who is requesting the operation, and whether the operation would succeed on the individual files separately. It's a pretty well written draft. Eliot |