Yahoo available AX attrs - more on numeric validation level

[Joseph A Holsten]

On Dec 8, 2009, at 12:26 PM, Peter Watkins wrote:

> On Tue, Dec 08, 2009 at 09:55:20AM -0800, Breno de Medeiros wrote:
>
>> When Allen, myself, and others proposed the original scope for AX  
>> 2.0,
>> providing meta-data about attributes (e.g., validation status, time  
>> of
>> most recent validation, even type of validation) was one of the main
>> drivers (and also to provide a mechanism for RP to discover which
>> attributes/schemas the OP supports). I think since then the issue of
>> containing the URL length in AX requests has been identified as
>> equally pressing.
>
> URL length is another argument for numeric representation of  
> validation
> level. A new AX spec could specify that the response be in the format
>
> NNN:MMM:XXX
>
> where NNN is the numeric validation level, MMM is how many days have  
> passed
> since validation, and XXX is the value. AX requests would be no longer
> than in AX 1.0, and responses would grow by very little.
>
> Request (also showing "type" reduced to "t" -- the request/response  
> syntax
> is far too chatty given the 2k limit for GET requests):
> openid.ax.t.c=http://axschema.org/contact/phone/cell
>
> Response:
> openid.ax.t.c=http://axschema.org/contact/phone/cell
> openid.ax.d.c=50:707:+1-555-555-1212
>
> or simply the following -- I don't see why the current AX fetch  
> response
> echoes the "type" parameter from the request:
> openid.ax.d.c=50:707:+1-555-555-1212

Clever. You won't be able to just not include the N:M: for assertions  
that haven't been validated, someone somewhere will want a string with  
integers, a colon, integers and a colon. You could escape colons (that  
sounds foul) or you could have a prefix of ::

Certainly can't compete with anything of the form
openid.ax.verification={openid.ax.x.y=NNN:MMM, ...}
--
e