Dan Brickley | 3 Feb 2009 14:06

Re: [foaf-dev] foaf:accountAccesspage

On 3/2/09 13:57, Benjamin Nowack wrote:
> I think I saw foaf-exporting sites use the profile pages as
> direct identifiers for accounts, e.g.
>
> <foaf:OnlineAccount rdf:about="http://twitter.com/lespacedunmatin">
> ...
>
> and IIRC, DanBri was suggesting (or questioning?) this approach
> here and there recently.
>
> I'm using this in my apps, too (deliberately ignoring the
> "can a URL denote a FOAF account?" metaphysics ;).

Yes. I am a bad person for not writing up a clear proposal for this.

FWIW I believe some use of sioc:User is also in this direction. And it 
is close to the deployment style of XFN and Google SGAPI.

Metaphysics aside, if we think of OnlineAccount as a kind of (informally 
speaking) semi-annotational "role" class, one that many kinds of thing 
can play, then I think it can work. Needs test cases at least though, 
very easy too get confused here. Just as many many kinds of thing are 
Buyable, and have prices, vendors etc., many many kinds of thing can be 
Log-in-able, ... and have usernames, service providers etc. The class 
OnlineAccount is a name for that class of thing. So ... what would a 
xyz:creation_date of http://some-online-account.example.com/ be? Well 
I'm not 100% sure. But note that we already have this problem with 
normal Web pages, due to content and language negotiation. It is often 
noted in SW circles, but rarely disasterous in practice...

Am I making some sense here?

cheers,

Dan

--
http://danbri.org/

Gmane