AX and Artifact Binding Charter Proposal

[Allen Tom]

+1

Definitely would love to see AX 1.1 released, hopefully eliminating any 
need for SREG.

To reach parity with SREG, AX 1.1 needs to have a standard way for RPs 
to pass their privacy policy URL, and it would be great to have a 
standard schema with very short attribute names.

It's very costly for OPs (and RPs) to support dual SREG and AX 
interfaces, when only one interface is necessary. It also hurts the 
interop story if there's no standard and widely implemented way to share 
basic profile data.

Allen


Dick Hardt wrote:
> +1!
> On 2009-11-12, at 8:05 AM, Nat Sakimura wrote:
>
>> Hi. 
>>
>> In anticipation of the Working Group creation process gets simplified 
>> in a couple of days, I have edited AX charter proposal to add "1.1" 
>> for a quick fix of things like privacy policy url and fetch 
>> parameters, which requires only few lines of additions, so that we 
>> can finish it quickly and then work more substantial 2.0, which 
>> includes the data structure change. 
>>
>> Also I have created Artifact Binding Charter, which will allow the 
>> use of OpenID in limited browsers (e.g., mobile) and improves 
>> security. Please feel free to add your names to the list of proposers. 
>>
>> Best,  
>>
>> -- 
>> Nat Sakimura (=nat)
>> http://www.sakimura.org/en/
>> _______________________________________________
>> specs mailing list
>> specs at lists.openid.net <mailto:specs at lists.openid.net>
>> http://lists.openid.net/mailman/listinfo/openid-specs
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> specs mailing list
> specs at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20091112/dd362561/attachment.htm>