- From: Pat Hayes <phayes@ihmc.us>
- Date: Fri, 7 Oct 2011 21:46:48 -0500
- To: Ian Davis <ian.davis@talis.com>
- Cc: Richard Cyganiak <richard@cyganiak.de>, Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr>, "public-rdf-wg@w3.org" <public-rdf-wg@w3.org>
On Oct 7, 2011, at 5:06 AM, Ian Davis wrote: > On Wed, Oct 5, 2011 at 9:14 PM, Pat Hayes <phayes@ihmc.us> wrote: > > But every time you use the name to refer to the graph, you are making an inference. And the way we have set things up with graph labels (see above) it is an *invalid* inference. So forget having RDF 'metadata' using graph labels/names: that is literally impossible, with the current conventions about the fourth IRI in a quad store. There is NO WAY to refer to a graph in RDF, with the current semantics. If we want to do this, we have to change the semantics rules so that the graph label denotes the graph it labels. This is trivial to do, of course, and to me it seems like a no-brainer, but apparently the WG does not agree. Which is fine, but then we all have to live with the consequences. > > > Can I not refer to a graph indirectly with a blank node? > > [ rdf:type rdf:Graph ; rdf:graphName "http://example.com/mygraph" ] Sure, you could do this if you had any confidence that rdf:Graph had some semantic relationship to actual RDF graphs. That however would take a (pretty hefty) semantic extension to the current semantics. And, even if we had this extension, this RDF would, AFAIKS, simply make the bnode denote *some* graph, but would not specify what the graph was. That isn't what I mean by 'naming' a graph. Pat > > > > -- > Ian Davis, Chief Technology Officer, Talis Group Ltd. > http://www.talis.com/ | Registered in England and Wales as 5382297 ------------------------------------------------------------ IHMC (850)434 8903 or (650)494 3973 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 mobile phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Saturday, 8 October 2011 02:47:22 UTC