W3C home > Mailing lists > Public > semantic-web@w3.org > May 2015

Re: deterministic naming of blank nodes

From: David Booth <david@dbooth.org>
Date: Wed, 20 May 2015 22:26:57 -0400
Message-ID: <555D4271.1070201@dbooth.org>
To: Gregg Kellogg <gregg@greggkellogg.net>
CC: "henry.story@bblfish.net" <henry.story@bblfish.net>, ahogan@dcc.uchile.cl, semantic-web@w3.org
On 05/20/2015 07:08 PM, Gregg Kellogg wrote:
>> On May 20, 2015, at 2:55 PM, David Booth <david@dbooth.org> wrote:
>> [ . . . ] currently there
>> is no standard way to directly refer to a bnode from a separate
>> SPARQL operation.  This is a known problem already with SPARQL,
>> which causes grief when doing followup queries.  But if SPARQL
>> servers were enhanced to (optionally) enable subsequent queries or
>> update operations to refer directly to blank nodes by their
>> *original* labels, then both PATCH and followup queries would work
>> on SPARQL servers.  (In the case of implicit bnodes generated by
>> Turtle/SPARQL [] or () notation the server would assign an original
>> label.)  This seems like a good route to take, though it means
>> adding that feature to SPARQL.  I'll send this to the SPARQL list
>> https://lists.w3.org/Archives/Public/public-sparql-dev/ to see what
>> others there think.
>
> This might only work on SPARQL servers that are capable of
> “remembering” original identifiers, and can rapidly get out of sync
> as the dataset changes.

I don't think it would have to get out of sync any more than URIs get 
out of sync.  The servers would have to remember them, just as they 
remember URIs.

> Alternatively, some SPARQL servers may use
> stable internal identifiers that could serve this purpose (still
> requiring normative normalization), but I suspect that there are some
> implementations that don’t guarantee such stable identifiers).

Right, it would involve enhancing SPARQL servers.

David Booth
Received on Thursday, 21 May 2015 02:27:27 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:42 UTC