[OpenID] OpenID schemas

[John Bradley]

The first thing is the Board or whomever deciding that the OIDF is  
going to run a schema registry for AX.

If they don't want to then it is a different problem.

The we need to establish a standard set of URI that map to SREG.

We could start with the process defined in
http://www.axschema.org/specs/openid-attribute-types-1_0-02.html

The doc needs to change schema.openid.net to schemas.openid.net

We need top decide if we want to define types as well.
http://www.axschema.org/specs/identity-attribute-metadata-1_0-01.html

I think we could adopt the 9 common URI almost immediately
http://schemas.openid.net/contact/email/namePerson/friendly	Alias/ 
Username	openid.sreg.nickname
http://schemas.openid.net/contact/email						Email			openid.sreg.email
http://schemas.openid.net/contact/email/namePerson			Full name		 
openid.sreg.fullname
http://schemas.openid.net/contact/email/birthDate			Birth date		 
openid.sreg.dob
http://schemas.openid.net/contact/emailg/person/gender		Gender			 
openid.sreg.gender
http://schemas.openid.net/contact/email/contact/postalCode/home	Postal  
code	openid.sreg.postcode
http://schemas.openid.net/contact/email/contact/country/home	Country			 
openid.sreg.country
http://schemas.openid.net/contact/email/pref/language		Language		 
openid.sreg.language
http://schemas.openid.net/contact/email/pref/timezone		Time zone		 
openid.sreg.timezone

The process for registering new URI is very similar to the one that  
the  ICF uses for claim types.

We do need to check that all of the Sxip documents are covered under  
there contribution agreement.

The important thing is to officially define the above table so that we  
have one common set of URI and not two as we do now.

The longer term schema and registration process could be a WG or a  
Board committee of some sort.

The administrative process of running the registry doesn't really have  
IPR so could be separate from the WG.

I pointed out the problem during the OSIS interop testing.   The state  
of AX interop is embarrassing.

Would Google support a standard set of AX attribute URI if they are  
defined.

Currently you are using the original Sxip ones at axshema.org.

Regards
John B.

On 17-Jun-09, at 7:18 PM, Breno de Medeiros wrote:

> Agreed. What work needs to be done today?
>
> On Wed, Jun 17, 2009 at 4:13 PM, John  
> Bradley<john.bradley at wingaa.com> wrote:
>> Leave the other parts of AX 2.0 like defining structured attributes  
>> etc to
>> the AX 2.0 work group if it gets going.
>>
>> We need a standard set of attributes for AX 1.0 now,  not in a year.
>>
>> John B.
>> On 17-Jun-09, at 6:57 PM, Breno de Medeiros wrote:
>>
>>> Context failure: Too many unresolvable acronyms.
>>>
>>> On Wed, Jun 17, 2009 at 3:35 PM, John Bradley<john.bradley at wingaa.com 
>>> >
>>> wrote:
>>>>
>>>> Leave the other bits to the AX 2.0 WG.
>>>>
>>>
>>>
>>>
>>> --
>>> --Breno
>>>
>>> +1 (650) 214-1007 desk
>>> +1 (408) 212-0135 (Grand Central)
>>> MTV-41-3 : 383-A
>>> PST (GMT-8) / PDT(GMT-7)
>>
>>
>
>
>
> -- 
> --Breno
>
> +1 (650) 214-1007 desk
> +1 (408) 212-0135 (Grand Central)
> MTV-41-3 : 383-A
> PST (GMT-8) / PDT(GMT-7)