[foaf-dev] Fwd: [WRFS] Prototype: Early Stage 1

[Peter Williams]

If I fancifully guess at the architecture of what's going on:
 
1 foaf stream can be generated on the fly from a merge of the openid2 XRD and the typical foaf file "profile" of n end-users. The sreg sub-service URL of any OP entity in the XRD is rewritten to be the foaf file's URI endpoint
 
2 foaf version of XRD entities associated with openid-named enduser is used by the "foaf-enhanced" openid2 relying party website, which seeks user authentication. Relying Party (target) Site completes "openid2 auth" with an Openid Provider selected from the foaf stream
 
3 During that openid2 authentication flow, user requests "sreg" attribute set (AX)  passing URL of sreg service to "foaf-aware" OP (ie. sreg attribute's own namespace declaration in RP's message is identified using the foaf stream URL, indicating "foaf extension" of std sreg lookup practices)
 
4. "foaf-aware" OP/sreg service recognises enhanced request,  and then fullfills AX/sreg value lookup against the foaf stream before returning values to Relying Party (target) website accoding to openid2, to fill out account registration form on target site.

in this way, its not "henry's website" serving foaf streams, but the OP agent
 
5. the foaf-aware OP can be enforcing any access guyards expressed in Henry's base foaf file, as it understand them
 
6. One AX attribute value returned via AX/sreg could be a URL of the static foaf file of a user, like Henry. This allows foaf-aware RP websites to do more with the basic(foaf file) profile data such as "personalize" the resulting website , after account registration (first time) and login. 
 
Just guessing.
________________________________

From: foaf-dev-bounces at lists.foaf-project.org on behalf of Danny Ayers
Sent: Sat 1/26/2008 12:12 AM
To: foaf-dev
Subject: [foaf-dev] Fwd: [WRFS] Prototype: Early Stage 1



fyi, from one of the DataPortability.org projects

---------- Forwarded message ----------
From: Josh Patterson <jpatterson at floe.tv>
Date: 26 Jan 2008 08:21
Subject: [WRFS] Prototype: Early Stage 1
To: WRFS <wrfs at googlegroups.com>

Guys,
Well, I finally carved out some time  to begin hacking away at a few
rudimentary concepts, and I know Paul is hard at work on a more fully
realized wNode prototype.

What I've done so far is created a js REST script that queries a very
rough + static wNode; It doesnt do much, and is more than likely
breaking XRDS laws of some sort, but its there.

http://cowbell.floe.tv/wrfs/wrfs_demo.html

There is an experimental mode on the wNode, which can be triggered via
the html form interface; It allows for a FOAF render mode from the
wNode, which may or may not ever make it into any sort of spec, its
more of a way to say "hey. this is what we were talking about" to the
RDF and FOAF communities --- "this is what it could look like, and now
we have a common reference point." ( and there again, some of the
terminology  I really wanted to describe a data container [ flickr,
myspace ] in FOAF didnt exist, as far as i could see. however, its
based on RDF, so I'm sure I could just make assertions about a
resource, etc )

[ foaf render mode ]
http://cowbell.floe.tv/wrfs/wNode.ashx?mode=foaf

[ default xrds render mode ]
http://cowbell.floe.tv/wrfs/wNode.ashx

I think the next question begs to ask: ok, so how do you further
define this resource? how is it controlled? how is it queried? wtf is
that random "wrfs" namespace you imported into xrds? (I employed a
creative license there.) -- and where the hell is the data container
example? (coming? er. sometime soon?)

This "prototype", even if you can call it that, is simply a beginning,
a needed spark. I expect everyone to constructively tear this thing
apart and make it better 10,000 times over --- and only then can it
becomes a fraction of its potential.

ToDo:
Rudimentary Data Container Example Records (hard coded for now, just
to show mechanics)
Parsing of xml XRDS data into data structure which generates the
queries for each Data Container.
Setup 3 Data Containers that spit out records (static is fine), so
that the demo can pull some "live" data from different servers.
Information coming out of Data Containers is more than likely
something dead simple like ATOM for now, or even just some stock XML,
I dont care --- as long as it functions, and shows the mechanics of
what we want to do. This will more than likely change over time.

Longer Range Todo:
Setup an openID 2.0 server with AX
Setup OAuth + Discovery, get headers working decently, weave in
Implement a wNode that supports REST  { GET / PUT } with support for
querying subsets.

Thoughts?

Josh Patterson

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "WRFS" group.
To post to this group, send email to wrfs at googlegroups.com
To unsubscribe from this group, send email to wrfs-unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/wrfs?hl=en
-~----------~----~----~----~------~----~------~--~---



--

http://dannyayers.com <http://dannyayers.com/> 
_______________________________________________
foaf-dev mailing list
foaf-dev at lists.foaf-project.org
http://lists.foaf-project.org/mailman/listinfo/foaf-dev