This issue was mentioned in Leigh Dodds' earlier comments and addressed in
the response to it:
http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2010Feb/0007.ht
ml
[[
> * General question re: scope. The document at present describes a
> mechanism for coarse grained graph updates, and does not attempt to
> offer the fine-grained access that SPARQL 1.1 Update offers. But
> there's a wide spectrum between those extras. For example the Talis
> Changeset format and protocol provides a RESTful way to manage updates
> to RDF graphs that is more expressive than the protocol described here
> but less so that SPARQL Update. Are the WG likely to consider
> something like Changesets too? (I note as an aside that there's at
> least one completely independent implementation using Changesets).
Unfortunately, the initial scope of the document was to cover the minimal
behavior covered by an intuitive interpretation of the HTTP protocol
specification. As a result the granularity is quite coarse and more
fine-grained interactions were delegated to the SPARQL Update language.
]]
-- Chime
On 3/24/10 6:35 AM, "Ivan Herman" <ivan@w3.org> wrote:
> I am not an HTTP expert, but found this blog this morning:
>
> http://www.semanticuniverse.com/blogs-http-patch-and-tracking-rdf-changes.html
> ?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SemanticUniverse+%
> 28Semantic+Universe%29
>
> Apologies if this is already known to the group and I just missed it...
>
> Ivan
===================================
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
locations.
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.