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

Re: Making progress on graphs

From: Dan Brickley <danbri@danbri.org>
Date: Fri, 18 May 2012 08:46:57 +0200
Message-ID: <CAFfrAFobeXm2-o-68VGJ0UmDpuUkH=Eti7=4HCj61gbAsKrS2w@mail.gmail.com>
To: Kingsley Idehen <kidehen@openlinksw.com>
Cc: "public-rdf-wg@w3.org" <public-rdf-wg@w3.org>
On Friday, 18 May 2012, Kingsley Idehen wrote:

> On 5/17/12 8:17 PM, Sandro Hawke wrote:
>
>> On Thu, 2012-05-17 at 18:34 -0400, Kingsley Idehen wrote:
>>
>>> On 5/17/12 4:21 PM, Sandro Hawke wrote:
>>>
>>>> So, what should an app developer do, if they want their code to be
>>>> portable between different sparql engines?
>>>>
>>>> (answer: they should avoid using empty named graphs.  right?)
>>>>
>>>>      -- Sandro
>>>>
>>> circa 2012. There are lots of developers, end-users, power-users already
>>> working across SPARQL endpoints without issue. Of all the problems there
>>> might be, empty named graphs just isn't one of them :-)
>>>
>> What does that mean?   That there are much bigger problems?   Of course,
>> but does that really mean we should cause one more?
>>
>>      -- Sandro
>>
>
> My response means: people are writing portable SPARQL that's working just
> fine. Nobody is complaining about SPARQL portability across DBMS engines
> and/or stores right now.
>
>>
>>
I've complained (in a friendly way I hope) when system-specific SPARQL+SQL
examples aren't clearly distinguished from pure SPARQL...

Dan


>
>
> --
>
> Regards,
>
> Kingsley Idehen
> Founder&  CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/**blog/~kidehen<http://www.openlinksw.com/blog/~kidehen>
> Twitter/Identi.ca handle: @kidehen
> Google+ Profile: https://plus.google.com/**112399767740508618350/about<https://plus.google.com/112399767740508618350/about>
> LinkedIn Profile: http://www.linkedin.com/in/**kidehen<http://www.linkedin.com/in/kidehen>
>
>
>
>
>
>
>
Received on Friday, 18 May 2012 06:47:29 GMT

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