W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > December 2011

Re: Indirect Graph Identification

From: Kjetil Kjernsmo <kjekje@ifi.uio.no>
Date: Thu, 08 Dec 2011 13:37:36 +0100
To: public-rdf-dawg-comments@w3.org
Cc: Sandro Hawke <sandro@w3.org>, James Leigh <james@3roundstones.com>
Message-id: <1482663.OURGu58TYi@owl>
On Tuesday 29. November 2011 00.12.12 Sandro Hawke wrote:
> With indirect identification, those graph containers each get nice,
> normal, RDF IRIs again.  Let's say you, me, and David each have sparql
> stores on the same host, and we all use that IRI to tag OUR OWN COPY of
> some data fetched from that URL.   (I think it's a terrible practice,
> but its clear from discussions in the RDF WG that people like it and we
> can't stop it.)

It is terrible, terrible, TERRIBLE practice, and it should be explored what 
can be done to stop it... They should be saying 
http://example.org/my-graph-copies/http://www.example.com/other/graph
instead and use that URI in their FROM clauses. Hmpf.

At the very least, if the WG persists on using this any reference to REST 
should be removed, as this is very clearly not RESTful. It makes the community 
look silly for referencing Fielding's dissertation when it goes against what's 
there.

But seriously, it is my opinion that the whole 4.2 indirect graph 
identification thing should be dropped and the specification adjusted 
accordingly to be RESTful.

Cheers,

Kjetil
-- 
Kjetil Kjernsmo
Ph.D. Research Fellow, Semantic Web
Department of Informatics, University of Oslo
kjekje@ifi.uio.no
Received on Friday, 9 December 2011 02:42:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 9 December 2011 02:42:04 GMT