PROPOSAL schema.openid.net for AX (and other extensions)

[Recordon, David]

Yes, I agree an upgrade path from SREG is needed.  We could however do
something as simple as
http://openid.net/specs/openid-simple-registration-extension-1_0.html#ni
ckname for the existing SREG fields.

For new fields, is there a reason we can't use the ldap.com URLs Mark
posted as a starting point?  I know Dick said they didn't cover all the
needed attributes, but would it be good enough to start with and then
expand from there possibly on schema.openid.net?  Dick, do you have a
list of attributes you see as needed for the first implementations of AX
(I couldn't find one in the current AX specs though I fully admit I may
be looking in the wrong place)?

--David

-----Original Message-----
From: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On
Behalf Of James Walker
Sent: Monday, April 09, 2007 1:10 PM
To: Martin Atkins
Cc: OpenID specs list
Subject: Re: PROPOSAL schema.openid.net for AX (and other extensions)

On 4/9/07 3:55 PM, Martin Atkins wrote:
> James Walker wrote:
>> As an implementor - there would be extremely positive benefits from 
>> having a base set of attributes defined and available @ 
>> schema.openid.net . I agree that the people most interested right now

>> are the OpenID community & implementors and it makes sense (to me) 
>> for openid.net to offer something - even just as a 'getting started
point'.
>>
> [snip]
>> What we need now (from my point of view) is a base set that we can 
>> work against to build momentum behind AX (building on the momentum 
>> already behind OpenID).
>>
> 
> If our goal is to not reinvent the wheel, then let's just identify 
> some AX mappings for the existing SREG fields, thus killing two birds 
> with one stone: people migrating from SREG get some fields that offer 
> one-to-one mappings, and these fields can be defined just by 
> referencing the existing SREG specification so we avoid having to
define anything.
> 
> SREG seems to be working well in the common case, so it seems like a 
> reasonable place to start.

I agree it's an excellent place to start - upgrade path + as you point
out it's working well in several cases today.

--
James Walker :: http://walkah.net/ :: xmpp:walkah at walkah.net
_______________________________________________
specs mailing list
specs at openid.net
http://openid.net/mailman/listinfo/specs