W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2012

Re: Comment BB-1 draft response (was RE: SPARQL TC 2012-09-04 Agenda)

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Tue, 04 Sep 2012 11:04:29 +0100
Message-ID: <5045D22D.4060705@epimorphics.com>
To: public-rdf-dawg@w3.org


On 04/09/12 11:00, Polleres, Axel wrote:
> Hi Andy,
>
> Thanks for the remarks, I have addressed 1/ and 3/ in the draft as follows:
>
> http://www.w3.org/2009/sparql/wiki/index.php?title=CommentResponse%3ABB-1&diff=4910&oldid=4905
>
> As for 2/, I wouldn't really want to add a discussion on how this relates to SD since my impression is
> that this is orthogonal to his question and wasn't really what he had asked for.

OK - my point was that the variability of endpoint offerings is 
partially covered by publishing a description of the endpoint.

	Andy

>
> Best,
> Axel
>
>> -----Original Message-----
>> From: Andy Seaborne [mailto:andy.seaborne@epimorphics.com]
>> Sent: Dienstag, 04. September 2012 11:46
>> To: public-rdf-dawg@w3.org
>> Subject: Re: Comment BB-1 draft response (was RE: SPARQL TC
>> 2012-09-04 Agenda)
>>
>>
>>
>> On 04/09/12 08:38, Polleres, Axel wrote:
>>>
>>> The comment BB-1 (Querying only the default graph from the
>> data store)
>>> Has now a draft response at:
>>>    http://www.w3.org/2009/sparql/wiki/CommentResponse:BB-1
>>>
>>> Please support/comment,
>>> Thanks,
>>>
>>> Axel
>>>
>>
>> A couple of points:
>>
>> 1/ The response discusses the comment - and asks some
>> implicit questions e.g. "it might be the case that you
>> suggest here" seems to asking for further discussion.  Is
>> that the intent?
>>
>> 2/ Service description is important here in describing what
>> data is in an endpoint.  It would point to the VOiD defn of
>> the default graph.
>>
>> If we're happy with that, add text to refer to the service
>> description work.
>>
>> 3/ The portable way to query only the default graph is to not
>> use GRAPH in the query.  I think the confusion here is that
>> someone coming from a world where the default graph is the
>> union of named graphs.
>>
>> I suggest stressing this by changing you example to
>>
>> """
>> SELECT *
>> WHERE { ..... }         <-- No use of GRAPH.
>> """
>>
>>
>> 	Andy
>>
>> Just discussion on:
>>
>> SELECT *
>> FROM DEFAULT
>>
>> I don't know that it means! Maybe there is an assumption
>> there is a real storage default graph that can be masked for
>> query by the union of named graphs.  This seems to be getting
>> into defining what is intentional a reflection of variability.
>>
>> The real, concrete default graph can also be put in the
>> dataset as a named graph, so it is accessible via FROM and
>> FROM NAMED. (c.f. Anzo?)
>>
>>
Received on Tuesday, 4 September 2012 10:05:00 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:49 GMT