- From: Alan Ruttenberg <alanruttenberg@gmail.com>
- Date: Thu, 2 Jul 2009 16:42:06 -0400
- To: Dan Brickley <danbri@danbri.org>
- Cc: "www-tag@w3.org WG" <www-tag@w3.org>
On Tue, Jun 30, 2009 at 8:54 PM, Dan Brickley<danbri@danbri.org> wrote: > Hello TAG, > > Talking with some SW folk about OpenID, and whether my "me-the-person" URI > could be practically usable as my OpenID, I came up with this corner-case: > > Could http://danbri.org be a URI for "me the person", and http://danbri.org/ > be a document about me (and also serve as my OpenID)? > > As I understand HTTP, any client must request something, so the former isn't > directly de-referencable. The client has to decide to ask for / from > danbri.org instead. But they're still different URIs, aren't they? > > Is... > > <Person xmlns:foaf="http://xmlns.com/foaf/0.1"/ > rdf:about="http://danbri.org"> > <openid> > <Document rdf:about="http://danbri.org/"/> > </openid> > </Person> > > ...at all feasible? I guess it depends on how exactly we think about the > "add a / to the end" step... >From an RDF point of view the URI strings are different means that they can denote different things. I guess the question I have about this is: Why be so "clever"? -Alan
Received on Thursday, 2 July 2009 20:43:01 UTC