FW: [rdfweb-dev] PPD
marc at broadbandmechanics.com
Fri Feb 6 16:54:15 UTC 2004
So the use case is:
I want to join a social network using some FOAF to pre-fill all that
information you need from me.
The problem is:
I might point you to a document containing information about many
And the solution is:
You ask me for my email address and send me a confirmation token like
every current online signup does today. At the same time you ask me
for the location of my FOAF. When I send the confirmation token back
you fetch the FOAF and read the triples that pertain to the person
with the mailbox I just proved I owned.
Or am I missing something very obvious?
Yes - that's kind of it - but I think we're doing it a little cleaner or
more straight forward.
1. You come to a social network - in our case the PeopleAggregator.
2. We give you a choice of either - a) having us create your FOAF for
you or b) you bringing in your own FOAF
3. If you provide us an email to work with - we can do all sorts of
fancy social networky kind of things (invites, messages, confirmation,
validation.) If not - we can't.
4. In your FOAF is people - right? Well they get imported to. Each
social network (we're assuming they'll be others like us - say Plink) -
will decide what to do with these 'other' people. In our case, the
PeopleAggregator will treat these 'external' people as if they are
'there' and render them within our UI. It actually works out great - as
now folks can establish relationships to other folks - without those
other folks having 'joined' the system.
5. In all cases - it's imperative that we can confirm - that THIS FOAF
is about YOU.
More information about the foaf-dev