Re: Well Behaved RDF - Taming Blank Nodes, etc.

Hi Henry,

On Wed, 2012-12-19 at 20:05 +0100, Henry Story wrote:
[ . . . ]
> Now one could go further and see what are the fundamental differences
> between URLs and blank nodes. Perhaps that would be useful.
> 1. With bnodes there is no intension associated with the name.
> 2. with well functioning URIs there is an intension associated with
> it, such that you can GET their meaning in the document in which they
> are defined - and there relative URIs play an important role!

That is an interesting philosophical view on the role of blank nodes,
and it goes pretty deep.  But I fundamentally disagree with it, as I
think it is too limiting.  I'll explain why in a moment, but first an
unrelated (non-philosophical) comment on point 2.

I think point 2 unnecessarily bundles the use of "cool",
dereferenceable, follow-your-nose http: URIs with the use of URIs in
general, which could simply be URNs whose definition you may not be able
to easily determine (by dereferencing), but which nonetheless still
avoid the problems that bnodes present of being unstable across
serializations, difficulties querying, non-lean graphs, etc.  I think it
is better to separate the bnode issue from the issue of whether an RDF
consumer can easily find an appropriate definition for a given URI.

Now turning to your philosophical point criterion for minting URIs:

> 1. With bnodes there is no intension associated with the name.

which you also described in: 

> - bnodes: you know there is something but you can only refer to 
>   it by description
> - relative URIs: you can speak of something but you don't yet 
    know the full publication context
> - full URIs: there is agreement between different people one 
    how to resolve the meaning of it.

In the semantic web, nearly *everything* is identified by description --
in essence, RDF properties.  We have almost no other way to define
things, except by listing their properties.  So if the criterion for
minting a URI instead of a bnode is that you must have some means beyond
a description -- ostension? -- for identifying that thing, then I think
that sets the bar for minting a URI far too high, because in a practical
sense descriptions are often all that we have.  We would be allowed VERY
few URIs if the bar were so high.  

Even if you only know a few properties of something, it can still be
very useful to mint a URI for that thing, as I illustrated in the
previous temperature measurement example:

On Wed, 2012-12-19 at 20:54 +0100, Henry Story wrote:
> I think a document that summarises some of the different pragmatic
> uses of bnodes, URLs relative urls still needs to be written.

Yes, good point!

David Booth, Ph.D.

Opinions expressed herein are those of the author and do not necessarily
reflect those of his employer.

Received on Wednesday, 19 December 2012 20:35:26 UTC