- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Thu, 17 May 2012 22:01:02 -0400
- To: public-rdf-wg@w3.org
- Message-ID: <4FB5AD5E.8080005@openlinksw.com>
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. > > > > > -- Regards, Kingsley Idehen Founder& CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Friday, 18 May 2012 02:01:27 UTC