W3C home > Mailing lists > Public > public-rdf-wg@w3.org > April 2011

Re: ISSUE-30: How does SPARQL's notion of RDF dataset relate our notion of multiple graphs?

From: Pat Hayes <phayes@ihmc.us>
Date: Fri, 15 Apr 2011 22:49:50 -0500
Cc: public-rdf-wg@w3.org
Message-Id: <37D1CFC9-1C3B-4E5C-A17F-2D943205B688@ihmc.us>
To: antoine.zimmermann@insa-lyon.fr

On Apr 15, 2011, at 3:47 AM, Antoine Zimmermann wrote:

> Le 14/04/2011 23:32, Pierre-Antoine Champin a écrit :
>> Pat,
>> 
>> I hadn't notivece this proposal either, I must confess.
>> 
>> Aside note: I have a minor problem with that proposal: does the
>> graph:import statement *have* to be in the default graph? Why not in the
>> importing graph? Why not in another graph that is trusted to contain
>> that kind of metadata?
> 
> The graph:imports stuff is meant to be an imaginary term that /would/ serve as a way to bring the triples of a graph into another graph. There is currently no issue asking whether we should introduce a graph:imports or not. In any case, this decision can't be taken before we know how we can identify a graph (or a g-box) in RDF.

Fair enough. But I just wanted to point out that with the current decision, *any* use of URI inside an RDF triple will have no connection at all to the use of the URI as a SPARQL 'tag' used to identify a graph. The point is not restricted to :imports; it is quite general. Pierre-Antoine's suggestion below does not address the central issue.

Pat

> 
> In my opinion, it can be made fairly simple and what you write below would be exactly what I think would be done in practice.
> 
>> 
>> By raising the problem, I assume you are referring to my scenario, where
>> I want to "name" a graph with, e.g., the URI of the foaf:Person it describe.
>> 
>>   <foaf.rdf#pa>  { [[triples of my foaf profile]] }
>> 
>> If I want another graph to import my foaf profile, it would be tempting
>> to state
>> 
>>   <other-graph>  {<>  graph:imports<foaf.rdf#pa>   }
>> 
>> which, I agree, would be a problem (because I refuse to be considered as
>> a graph ;). The correct way to do it would be to write instead:
>> 
>>   <other-graph>  {<>  graph:imports<foaf.rdf>   }
>> 
>> and you seem to imply that it would also be a problem. But you make
>> assumptions here:
>> 
>> * that the dataset does *not* also contain a graph named<foaf.rdf>,
>> with the same content
>> 
>> * that the engine processing the graph:imports only uses the named
>> graphs of the dataset to access the imported graph
>> 
>> I believe that it is possible to falsify at least one of those
>> assumptions, and to make graph:impots work. The most natural thing to do
>> would be to have at least *some* graphs "named" with a proper
>> identifier, even if that mean some reduncancy in the dataset...
>> especially if we have graph:import to manage this redundancy without too
>> much overhead !
>> 
>>   <foaf.rdf>     {  [[some-triples-gere]] }
>>   <foaf.rdf#pa>  {<>  graph:imports<foaf.rdf>   }
>>   <other-graph>  {<>  graph:imports<foaf.rdf>   }
>> 
>> et voila!
>> 
>> Granted, this would have to be carefully explained along with the
>> graph:imports proposal, should we keep it. But I don't think it is too bad.
>> 
>>   pa
>> 
>> On 04/14/2011 07:09 PM, Pat Hayes wrote:
>>> Well, the use of a URI inside an RDF triple assumes that the URI is being used as a name, to refer to something. Using a URI which is the name of a named graph, for example, would refer to the graph. But in this decision we *explicitly* say that this is *not* how the SPARQL association of URIs to graphs works: that the 'associated' graph which is 'tagged' (if I have that right) by a URI might well not be the entity referred to by the URI. The example was given in which the URI is the name of a person, ie refers to a person, and still can be used to 'tag' a graph for SPARQL purposes. If such a URI is used as the object of an RDF triple, it will refer to the person, not to the SPARQL-tagged graph. As there is no way to know whether the graph that is SPARQL-tagged by a URI is, or is not, the referent of the URI, any use of that URI as a name inside an RDF triple must be basically unrelated to its use as a SPARQL graph tag; or at any rate, that is the only safe assumption to 
> ma
>> ke.
>>> 
>>> In a nutshell, RDF uses URIs as referring names. Apparently, SPARQL does not, when it comes to identifying graphs. So the uses of URIs in RDF triples and in SPARQL tags are dissociated from one another, and need have no relationship. So, no relationship can be relied upon. The 'naming' of graphs in SPARQL is a wholly SPARQL-local business, unrelated to RDF semantics and therefore to any RDF content.
>>> 
>>> I assumed this was obvious at the time we were discussing this, by the way. But I confess I had not at that time read the Wiki proposal fully, and not seen the 'imports' examples.
>>> 
>>> Pat
>>> 
>>> On Apr 14, 2011, at 11:55 AM, Ivan Herman wrote:
>>> 
>>>> Pat,
>>>> 
>>>> sorry, but you will have to explain (me) what the problem is.
>>>> 
>>>> Ivan
>>>> 
>>>> ----
>>>> Ivan Herman
>>>> web: http://www.ivan-herman.net
>>>> mobile: +31 64 1044 153
>>>> 
>>>> On 14 Apr 2011, at 18:43, Pat Hayes<phayes@ihmc.us>  wrote:
>>>> 
>>>>> I note in passing that the Proposed WG Decision dated 14 April has the consequence that the IRi associated with a graph in SPARQL cannot be used inside an RDF triple to reliably refer to the graph. This means in particular that uses such as those contemplated in
>>>>> http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs/RDF-Datasets-Proposal, which use the SPARQL name as the object in an 'imports' triple, are ruled out by this decision.
>>>>> 
>>>>> Pat
>>>>> 
>>>>> On Apr 13, 2011, at 4:29 AM, RDF Working Group Issue Tracker wrote:
>>>>> 
>>>>>> 
>>>>>> ISSUE-30: How does SPARQL's notion of RDF dataset relate our notion of multiple graphs?
>>>>>> 
>>>>>> http://www.w3.org/2011/rdf-wg/track/issues/30
>>>>>> 
>>>>>> Raised by:
>>>>>> On product:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> ------------------------------------------------------------
>>>>> 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
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>> 
>>> ------------------------------------------------------------
>>> 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
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
> 
> 
> -- 
> Antoine Zimmermann
> Researcher at:
> Laboratoire d'InfoRmatique en Image et Systèmes d'information
> Database Group
> 7 Avenue Jean Capelle
> 69621 Villeurbanne Cedex
> France
> Tel: +33(0)4 72 43 61 74 - Fax: +33(0)4 72 43 87 13
> Lecturer at:
> Institut National des Sciences Appliquées de Lyon
> 20 Avenue Albert Einstein
> 69621 Villeurbanne Cedex
> France
> antoine.zimmermann@insa-lyon.fr
> http://zimmer.aprilfoolsreview.com/
> 
> 

------------------------------------------------------------
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, 16 April 2011 03:50:23 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:41 GMT