[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda:Joint XRI & XDI TC Telecon 10AM PT Thursday 2007-12-13
Following is the agenda for a joint unofficial telecon of the XRI and XDI TCs at: Date: Thursday, 13 December 2007 USA Time: 10:00AM - 11:00PM Pacific Time *** NOTE: IT IS PROPOSED THAT THIS WEEK'S TELECON ONLY LAST ONE HOUR *** Event Description: Weekly unofficial joint call of the XRI and XDI Technical Committees. TO ACCESS THE AUDIO CONFERENCE: Dial In Number: 571-434-5750 Conference ID: 5474 AGENDA 1) INTERNET IDENTITY WORKSHOP RECAP Those of use who attended IIW in Mountain View last week will summarize the highlights from an OASIS, XRI, and XDI perspective, including: * Finalization of the OpenID 2.0 specifications. * Discussion of OAuth using XRDS for discovery. * Session on VRM (Vendor Relationship Management) which included XDI. * Session on XDI RDF. * Proposal for an OASIS Open Reputation Management System (ORMS) TC. 2) OAUTH DISCOVERY The OAuth community (see http://oauth.net/) is now developing a discovery protocol and proposing to use XRDS. Gabe sent the message below to the TC list yesterday. We'll review it on the call and see who wants to volunteer to help. ******* MESSAGE FROM GABE TO THE XRI TC LIST ********* This relies on XRDS quite a bit - Eran reproduces a lot of our text - volunteers here to make sure there are no issues? -Gabe ---------------------------------------------------------------------------- From: oauth-extensions@googlegroups.com [mailto:oauth-extensions@googlegroups.com] On Behalf Of Eran Hammer-Lahav Sent: Tuesday, December 11, 2007 9:28 PM To: oauth-extensions@googlegroups.com Subject: [oauth-extensions] OAuth Discovery 1.0 Draft 1 http://oauth-specs.googlecode.com/svn/discovery/drafts/1/spec.html I am happy to announce my first draft of the proposed Discovery specification. Somewhere along the road it got really big and somewhat complicated and I am hoping to trim it down a bit during the next few drafts. The goal is to figure out which areas can be made less flexible in exchange for simplicity and easy of development. Unlike OAuth Core, I do not expect Discovery to be implemented by novice developers. At the same time, it shouldn't require years of experience to figure out. What I've attempted to do was provide the ability to enable full discovery from a Protected Resource URL without knowing anything else about the Service Provider except that it supports OAuth. This is not a small task. For this draft I would like to get more content feedback and less (really none) editorial. There is little point in editorial feedback so early when the spec is going to change significantly. Please start with the example in the appendix to get a general idea of what the discovery document looks like. There are a bunch of new terms to get used to, and if you never looked at an XRDS document before, maybe take a few minutes to read a quick tutorial. I think we have two camps here, one with the idea of fully automated discovery, and the other looking for a simple format (maybe HTML) to just list the endpoints and maybe a tiny bit of detail about them. I tried to do both but gave up on the second, especially after the feedback from IIW. Please note the new spec SVN depot. I copied all the Core 1.0 drafts in there but will keep the old depot specs for now (to maintain blog links). If you need write access let me know. EHL
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]