W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2010


From: Chimezie Ogbuji <ogbujic@ccf.org>
Date: Wed, 24 Mar 2010 10:22:22 -0400
To: "Steve Harris" <steve.harris@garlik.com>
cc: "Ivan Herman" <ivan@w3.org>, "W3C SPARQL Working Group" <public-rdf-dawg@w3.org>
Message-ID: <C7CF985E.107CB%ogbujic@ccf.org>
On 3/24/10 10:06 AM, "Steve Harris" <steve.harris@garlik.com> wrote:
> My (admittedly brief) reading of the PATCH semantics are that it would
> be a more appropriate verb to use inplace of/in addition to POST for
> additive updates.

I see it differently.  The semantics of POST are to accept the entity
enclosed as a 'subordinate'.  The analogy of the relationship between a file
and a directory is used to explain what is meant by a subordinate.  This
suggests an additive operation.  The semantics of PATCH - on the other hand
- are actually more inline with the general intent of the SPARQL Update
language itself, since it says "With PATCH, however, the enclosed entity
contains a set of instructions describing how a resource currently residing
on the origin server should be modified to produce a new version"

So it seems to me that the PATCH operation is equivalent to a SPARQL Update
request at 'graph-level' granularity and that additive operations on an RDF
graph (i.e. POST currently) are a subset of this.

-- Chime


P Please consider the environment before printing this e-mail

Cleveland Clinic is ranked one of the top hospitals
in America by U.S.News & World Report (2009).  
Visit us online at http://www.clevelandclinic.org for
a complete listing of our services, staff and

Confidentiality Note:  This message is intended for use
only by the individual or entity to which it is addressed
and may contain information that is privileged,
confidential, and exempt from disclosure under applicable
law.  If the reader of this message is not the intended
recipient or the employee or agent responsible for
delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If
you have received this communication in error,  please
contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy.  Thank you.
Received on Wednesday, 24 March 2010 14:23:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:00 UTC