[rdfweb-dev] inverse of knows:
Marc Canter
marc at broadbandmechanics.com
Thu Oct 16 20:15:24 UTC 2003
We're working hard on getting the PeopleAggregator code going. I'm here
in Denver at DigitalID World - spreading the FOAF meme.
I've just recruited Simon Grice and his Midentity service (U.K. based
http://www.midentity.com <http://www.midentity.com/> ) as another
participant in some form of a federated social network (our code-name is
FSN) relying upon FOAF. Simon's real interested in working with ecademy
(as an example) day one.
So here's what we've been talking about. The exact interop
possibilities that we'd like to start off simply with:
- Import FOAF
- end-user identifies which system they're importing from (from
those participating systems supporting the single sign-on technology)
- profile data is then imported (which includes BOTH attributes
and friends list) (i.e. everything in a FOAF file)
- this data is converted from FOAF to the internal representation
that the system utilizes
- as changes happen in that "external" FOAF file - a notification
and data update is sent
- the new updated data is then synced within the system
- Export FOAF
- the end-user specifies which system they wish to export to (from
the list of participating systems (which support the single sign-on
technology))
- the profile data and friends lists are converted from internal
representation to FOAF
- the FOAF file is sent to the external system
- that external system syncs to that FOAF file
- if any changes are made to this profile data and friends list,
then the process is repeated, keeping the internal info in sync with the
external system
==============
Architecture notes:
- it's not a coincidence that Simon and I have met at DigitalID
World. The place is filled with web services, ID management, Liberty
Alliance and WS-Security wonks.
- we've identified the PingID open source implementation of the
Liberty Alliance (which is called SourceID) - as a means of implementing
single sign-on. That's what the v 1.0 does of the LA spec. V 2.0 will
get us control over individual attributes (due by end of the year.)
- the combination of our PeopleAggregator, the SourceID and some
"customer tracking" code - will make up the code-base of the FSN.
- the idea is to make the FSN a 501-c3 org - where all
contributors to the code base get attribution - in perpetuity.
================
Revenue model:
- there's an idea of web service sharing, where a system like The
Tribe might offer a web service (like their listings service) which
they'd like other systems to "flow" people into.
- if any money is spent by an end-user (turning them into a
customer) then the Tribe would send a royalty/commission check to the
originating system.
- this would work with any kind of web service participating in
the FSN (digital downloading, multi-player gaming, photo printing,
business networks, etc.)
- the code that tracks where the customer comes from and where
they spent their money - will hopefully get written by the Tribe and
contributed to the FSN.
====================
UI considerations:
- we want to provide a basic mechanism for end-users to control
whether or not their name is exported and hot-linked to external
systems.
- that should probably come in the guise of a checkbox which says
"allow export of FOAF" - (or something like that) - which, when checked
would have that end-users FOAF sent along with any "friends" social net.
- however if the end-user has NOT checked the checkbox, then we
propose that a simple stub gets exported - with just he person's name
and say, weblog address. This is what happens when TypePad creates FOAF
files (from their blogroll.)
- Marc Canter
-----Original Message-----
From: rdfweb-dev-bounces at vapours.rdfweb.org
[mailto:rdfweb-dev-bounces at vapours.rdfweb.org] On Behalf Of Eric
Vitiello
Sent: Wednesday, October 15, 2003 6:45 PM
To: 'Eric Sigler'; 'Julian Bond'
Cc: rdfweb-dev at vapours.rdfweb.org
Subject: RE: [rdfweb-dev] inverse of knows:
> as Marc just wanted them up for demo/testing ideas. I
> figured at some point we'd talk things over and probably make
> a more formal sort of request / dialog for things in that
> namespace. (And PeopleAgg is not there yet).
Let me know when you're interested in expanding -- I would love more
input
on how people would like to use the relationship schema, and I'm very
open
to expansion!
--
Eric Vitiello
Perceive Designs <http://www.perceive.net <http://www.perceive.net/> >
_______________________________________________
rdfweb-dev mailing list
rdfweb-dev at vapours.rdfweb.org
wiki: http://rdfweb.org/topic/FoafProject
http://rdfweb.org/mailman/listinfo/rdfweb-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.usefulinc.com/pipermail/foaf-dev/attachments/20031016/be0e358d/attachment-0001.htm
More information about the foaf-dev
mailing list