Thanks Nat, got you. :-) On Thu, Nov 19, 2009 at 8:56 PM, Nat Sakimura <[email protected]> wrote:
> Hi Santosh, > > On Fri, Nov 20, 2009 at 12:11 AM, Santosh Rajan <[email protected]>wrote: > >> My apologies, If i am going to ask what may be two dumb questions. I >> haven't been following the AX/Sreg discussions. >> 1) Why are we having both AX 1.1 and 2.0 discussions. We might as well >> straight go for 2.0 if 1.1 is not yet out? Maybe I must have missed the fact >> that 1.1 release is imminent? >> > > For 1.1, I have posted a draft. It requires only 20 lines or so change in > the spec, small change in the library, and ease the current pain so much. > > >> 2) If OpenID 2.0 is going to use resource descriptors for discovery, can >> we not use the same resource descriptor format for AX request and response? >> After all, attributes are also resources, and we can can have a consistent >> resource format across 2.0? >> > > Yes. It will be, but we have to wait for more time then. > 1.1 is in couple of months framework. > It is an aspirin rather than a cure. > Aspirin does not cure, but will improve the quality of life. > > >> Thanks, >> >> >> On Thu, Nov 19, 2009 at 8:19 PM, John Bradley <[email protected]>wrote: >> >>> Nat, >>> >>> I understand why people want a fetch parameter. I would like it, or >>> something like it as well. >>> >>> However I think that is AX 2.0 work. >>> >>> Anything that requires code changes at the RP will slow adoption. >>> >>> I think we should limit AX 1.1 to practical things we can accomplish >>> through config changes at the RP. >>> >>> Yes OP's will need some changes. >>> >>> My argument is adoption if code changes are required RP's will tend to >>> wait for AX 2.0. >>> >>> There is also the slippery slope argument. Why make a code change that >>> for fetch as opposed to something else. >>> >>> I also have a suspicion that to do fetch properly at the RP it will >>> require rethinking a bunch of things to use it. >>> >>> I think we should add 1 Privacy Policy and 1 TOS in the RP's XRDS, and >>> define the SREG compatible AX attributes (short if possible). >>> >>> I think fetch and the RP sending more specific Privacy policy are AX 2.0 >>> features. >>> >>> I am uncharacteristically making an argument for practicality. >>> Fix what we can quickly, and have it implemented by those that want it in >>> weeks not years. >>> >>> John B. >>> >>> On 2009-11-19, at 1:21 AM, Nat Sakimura wrote: >>> >>> Hi. >>> >>> To separate out the 2.0 and 1.1 discussion, I have created a new separate >>> charter for AX 1.1 >>> >>> https://openid.pbworks.com/OpenID_Attribute_Exchange_Extention_1_1 >>> >>> Regards, >>> >>> =nat >>> _______________________________________________ >>> specs mailing list >>> [email protected] >>> http://lists.openid.net/mailman/listinfo/openid-specs >>> >>> >>> >>> _______________________________________________ >>> specs mailing list >>> [email protected] >>> http://lists.openid.net/mailman/listinfo/openid-specs >>> >>> >> >> >> -- >> http://hi.im/santosh >> >> >> >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs >> >> > > > -- > Nat Sakimura (=nat) > http://www.sakimura.org/en/ > -- http://hi.im/santosh
_______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
