- From: Polleres, Axel <axel.polleres@siemens.com>
- Date: Mon, 11 Jun 2012 23:14:57 +0200
- To: "sandro@w3.org" <sandro@w3.org>, "chimezie@gmail.com" <chimezie@gmail.com>
- CC: "public-rdf-dawg@w3.org" <public-rdf-dawg@w3.org>
I have made the following change in update: s/ the SPARQL 1.1 Graph Store HTTP Protocol provides means to perform certain operations to manage collections of graphs more directly, via the direct use of HTTP operations following REST principles. / the SPARQL 1.1 Graph Store HTTP Protocol provides means to perform certain operations to manage collections of graphs directly via HTTP operations. / cf. http://www.w3.org/2009/sparql/docs/sparql11-overview/Overview.xml#sparql11-graphstore-http-protocol Best, Axel -- Dr. Axel Polleres Siemens AG Österreich Corporate Technology Central Eastern Europe Research & Technologies CT T CEE Tel.: +43 (0) 51707-36983 Mobile: +43 (0) 664 88550859 Fax: +43 (0) 51707-56682 mailto:axel.polleres@siemens.com > -----Original Message----- > From: Sandro Hawke [mailto:sandro@w3.org] > Sent: Monday, 11 June 2012 4:48 PM > To: Chimezie Ogbuji > Cc: SPARQL Working Group > Subject: Re: Updates to GSP removing references to REST > > Note that Overview needs to be updated, too, since it uses > the word REST > in relation to GSP. (Alexandre Bertails just pointed this > out to me.) > > -- Sandro > > On Sun, 2012-06-03 at 23:19 -0400, Chimezie Ogbuji wrote: > > Per our discussion in the last teleconference, I have removed > > references to the REST architectural style in the editor's > draft and > > replaced them (where necessary) with text describing it's > concordance > > with HTTP, instead: > > > > http://www.w3.org/2009/sparql/docs/http-rdf-update/ > > > > A summary of the changes is below. > > > > ---------------- > > > > First paragraph of abstract > > "This document describes the use of HTTP operations for the > purpose of > > managing a collection of RDF graphs in the REST > architectural style." > > > > -> > > > > "This document describes the use of HTTP operations for the > purpose of > > managing a collection of RDF graphs." > > > > First 2 paragraphs of Introduction > > > > "This document describes updating and fetching RDF graph > content from > > a Graph Store over HTTP in the REST style [REST]. In doing so, it > > appeals to the following interface constraints that > comprise the REST > > architectural style:" > > > > -> > > > > "This document describes an application protocol for the > distributed > > updating and fetching of RDF graph content in a Graph Store via the > > mechanics of the Hypertext Transfer Protocol (HTTP) [RFC2616]. In > > doing so, it appeals to the following interface constraints that > > emphasize the core, architectural components underlying HTTP:" > > > > Removed the first sentence (below) of paragraph immediately > after list > > of interface constraints: > > > > "The REST architectural style specifically conceives of a > hypermedia > > application framework through the prism of these > constraints and the > > parenthetical remarks in the list above demonstrate how each > > constraint is met." > > > > Removed Representation State Transfer architectural style > (REST) from > > terminology > > > > Removed last sentence of second paragraph in 5.7 HTTP PATCH > > (Informative) that describes the counter-intuition of a > PATCH request > > that modifies more than one RDF graph with respect to REST. > > > > Removed informative reference to Fielding REST architectural style > > dissertation chapter > > > > I will modify the draft response to James accordingly. > > > > -- Chime > > > > > > > >
Received on Monday, 11 June 2012 21:16:14 UTC