HTTP Patch proposal

I just noticed this:
  http://www.ietf.org/internet-drafts/draft-dusseault-http-patch-01.txt

[[
   Several applications extending HTTP require a feature to do partial
   resource modification.  Existing HTTP functionality only allows a
   complete replacement of a document. This proposal adds a new HTTP
   method, PATCH, to modify an existing HTTP resource.
]]

And this is a key indicator of its function:
[[
   The PATCH request MUST have a body.  It MUST include the Content-Type
   header with a value indicating what the body type is.  It MUST be a
   format that has the semantics of defining a change to an existing
   document (such as gdiff).
]]

I don't think this poses any fundamental problems for Web architecture, but 
the only reason I can see for not using POST is this:
[[
   The PATCH request is subject to access control, which in turn may
   require authentication.  The PATCH request SHOULD be subject to the
   same access control permissions as the PUT request.
]]

#g


------------
Graham Klyne
For email:
http://www.ninebynine.org/#Contact