Re: Person Identifier

Hi Andreas,

>  interesting opinions here. Both I can acquire taste for. I think the
> problem that I need an HTTP request first is less and less there from now on
> because of mobile access everywhere.

That depends on what you think 'the problem' is. :) In RDF, I can
write triples down on the back of an envelope. Any statements I make
are in some sense true (at least in the world I have created that is
described by my envelope), regardless of the presence of a network.

To put it a different way, RDF is a way of making statements about
anything you like. Obviously, some of the things we want to make
statements about are web-pages, but most of them are not. So the
argument being pursued (and I know it's not just your position, but
one that is widely held) is that we need to establish a connection to
the internet before we can deduce that some person is *not* a

That is so back to front as to be frightening!

> The fact, that I can figure out
> anything about a thing by doing a simple GET request is very very appealing.
> I think it makes things really easier.

GET requests may be simple, but how can making one be easier than
*not* making one?

>  Another suggestion whould be to inject a protocol hint into the URI by the
> convention of a special sub-domain like
>  http://doi.yourdomain.tld/somePath/resource/foo

URIs are transparent to RDF. They are simply identifiers. You can hack
them up all you like, but you can't expect RDF to start unpacking the
hacks.  The problem with URIs comes when using one identifier to
represent two different things. That's a problem whichever way you
look at it, whatever the two things are, not just web-pages and



 Mark Birbeck | +44 (0) 20 7689 9232 | Ltd. is registered in England and Wales, number 03730711
 The registered office is at:

 2nd Floor
 Titchfield House
 69-85 Tabernacle Street

Received on Monday, 21 April 2008 10:17:16 UTC