Hi Santosh, <br><br><div class="gmail_quote">On Fri, Nov 20, 2009 at 12:11 AM, Santosh Rajan <span dir="ltr"><<a href="mailto:santrajan@gmail.com">santrajan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
My apologies, If i am going to ask what may be two dumb questions. I haven't been following the AX/Sreg discussions. <div>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?</div>
</blockquote><div><br></div><div>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. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>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?</div>
</blockquote><div><br></div><div>Yes. It will be, but we have to wait for more time then. </div><div>1.1 is in couple of months framework. </div><div>It is an aspirin rather than a cure. </div><div>Aspirin does not cure, but will improve the quality of life. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>Thanks,</div><div><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 8:19 PM, John Bradley <span dir="ltr"><<a href="mailto:john.bradley@wingaa.com" target="_blank">john.bradley@wingaa.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Nat,<div><br></div><div>I understand why people want a fetch parameter. I would like it, or something like it as well.</div><div><br></div><div>However I think that is AX 2.0 work.</div>
<div><br></div><div>Anything that requires code changes at the RP will slow adoption.</div><div><br></div><div>I think we should limit AX 1.1 to practical things we can accomplish through config changes at the RP.</div><div>
<br></div><div>Yes OP's will need some changes.</div><div><br></div><div>My argument is adoption if code changes are required RP's will tend to wait for AX 2.0.</div><div><br></div><div>There is also the slippery slope argument. Why make a code change that for fetch as opposed to something else. </div>
<div><br></div><div>I also have a suspicion that to do fetch properly at the RP it will require rethinking a bunch of things to use it.</div><div><br></div><div>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). </div>
<div><br></div><div>I think fetch and the RP sending more specific Privacy policy are AX 2.0 features.</div><div><br></div><div>I am uncharacteristically making an argument for practicality.</div><div>Fix what we can quickly, and have it implemented by those that want it in weeks not years.</div>
<div><br></div><div>John B.</div><div><br><div><div><div></div><div><div>On 2009-11-19, at 1:21 AM, Nat Sakimura wrote:</div><br></div></div><blockquote type="cite"><div><div></div><div>
<div bgcolor="#ffffff" text="#000000">
<span style="border-collapse:separate;font-family:'Times New Roman';font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:'MS UI Gothic';font-size:12px;white-space:pre">Hi.
<br>
<br>
To separate out the 2.0 and 1.1 discussion, I have created a new
separate charter for AX 1.1<br>
<br>
<a href="https://openid.pbworks.com/OpenID_Attribute_Exchange_Extention_1_1" target="_blank">https://openid.pbworks.com/OpenID_Attribute_Exchange_Extention_1_1</a><br>
<br>
Regards, <br>
<br>
=nat<br>
</span></span>
</div></div></div>
_______________________________________________<br>specs mailing list<br><a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
</blockquote></div><br></div></div><br>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
<br></blockquote></div><br><br clear="all"><br></div></div>-- <br><a href="http://hi.im/santosh" target="_blank">http://hi.im/santosh</a><br><br><br>
</div>
<br>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br>