W3C home > Mailing lists > Public > public-rdf-wg@w3.org > May 2012

Re: Making progress on graphs

From: Richard Cyganiak <richard@cyganiak.de>
Date: Tue, 22 May 2012 15:26:00 +0100
Cc: Guus Schreiber <guus.schreiber@vu.nl>, RDF Working Group WG <public-rdf-wg@w3.org>
Message-Id: <F1371B6A-8067-40E5-9532-B469AFBF2882@cyganiak.de>
To: Pat Hayes <phayes@ihmc.us>
On 22 May 2012, at 15:10, Pat Hayes wrote:
>>>> ISSUE-28 Syntactic nesting of g-texts http://www.w3.org/2011/rdf-wg/track/issues/28
>>>> PROPOSED: Close ISSUE-28 ("Do we need syntactic nesting of graphs (g-texts) as in
>>>> N3?"), saying No, we do not -- they are useful, but we can provide the same
>>>> functionality with datasets.
>> Let's assume the abstract syntax supported nested graphs. Then we can convert that to a “flat” dataset like this: For any nested graph G, replace it by a new IRI i, and add a new pair <i,G> to the dataset.
> I was afraid of that. That works only if we give the datasets a semantics in which the graph 'name' really does denote the named graph, in the 2004 semantics sense of 'denote'.

Why? Can you give an example where this does not work?

> So, I am cool with this PROVIDED that we all understand, and accept, that this is now an absolute requirement on any proposed dataset semantics. This rules out Antoine's proposal, for example. 
>>>> ISSUE-33 Mechanism to refer to sub-graphs and/or individual triples
>>>> http://www.w3.org/2011/rdf-wg/track/issues/33
>>>> PROPOSED: Close ISSUE-33 ("Do we provide a way to refer to sub-graphs and/or
>>>> individual triples?"), with the understanding that datasets can be used to refer to
>>>> sub-graphs and individual triples.
>>> Again, how does this work? Consider the graph G = { <:a :b :c> <:d :e :f> <:g :h :i>} and the subgraph G1 consisting of just the first two triples, and then the first triple alone, call that T. That is a total of three triples and two (or perhaps three) graphs. How would these relationships be represented using datasets? 
>> <G> { :a :b :c. :d :e :f. :g :h :i. }
>> <G1> { :a :b :c. :d :e :f. }
>> <T> { :g :h :i. }
>> Meaning: If you want to talk about a subgraph or individual triple, you need to stuff the subgraph or triple into a named graph of its own. (What exactly <G>, <G1> and <T> name, identify, refer to or denote is still open; the above just means that these IRIs are somehow associated with those triples.) One could then define entailment regimes where the following triples can be inferred:
>> <G> ex:subgraph <G1>. <G> ex:subgraph <T>. <G> ex:unionOf (<G1> <T>). <G> ex:entails <G1>.
>> And so on. But whether this WG actually wants to define any such relationships remains an open question.
> OK, so this is pretty trivial. I guess I am left wondering what ISSUE-33 was supposed to be about, since if this is all it means, why was it ever an issue in the first place? But never mind, lets not get into historical reconstruction. 

I believe there was a proposal that each triple should have its own separate identifier, and graphs could essentially be “assembled” from the triples by making statements about them. I recall that I argued against such a design, saying that it can be handled in RDF datasets as a degenerate case where each graph contains only a single triple.

Received on Tuesday, 22 May 2012 14:26:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:05 UTC