Re: Skolemization and RDF Semantics

On 19/04/11 15:24, Alex Hall wrote:
> FWIW, some (many? most?) triple store implementations provide what might
> be called a weak form of skolemization at the API level, in that the
> bNode object ('object' in the programming language sense of the word)
> often encodes the internal identifier.  When the object is passed back
> to the store in a subsequent query or update, the store can recognize
> the object as a bNode that originated from a local graph and dereference
> the identifier to find the internal node.
>
> Using bNode identifiers this way is probably an abuse of how they were
> originally intended, but it's also extremely useful for following your
> nose within the context of a single graph without having to formulate a
> monstrous SPARQL query to find the bNode you're looking for and pull in
> all of its properties in one fell swoop.  As a consumer of RDF data, if
> the same feature were exposed via SPARQL then I don't really care how it
> happens, I'll jump for joy.  As a WG member, I do recognize that it's
> our task to work out the "how it happens" part :-)
>
> -Alex

Difficult to see how data is ever created otherwise :-)

Not all data comes from reading in a document.  Sometimes code builds 
it; like an editor.

	Andy

Received on Tuesday, 19 April 2011 16:11:37 UTC