<HTML dir=ltr><HEAD></HEAD>
<BODY>
<DIV id=idOWAReplyText45227 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>If I got the message loud and clear, we must not assume that the localid is a URI - it is merely a key (in the database sense) - in the context of openid auth and those extensions currently defined.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>We know from the localid in XRI resolution, that the key can take the form of an i-number rather than a URI - and IS an i-number if one has relies on the "trusted resolution" mode of the XRI resolver.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>On the one hand, this leads one to the conclusion that the localid is an opaque type. It has no type, in a formal logic describing all the properties of openid auth . The protocol engine of the RP should thus not make any assumptions about typing, other than relying upon non-ambiguity (in untrusted resolution) or uniqueness in i-space (trusted resolution).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Now, an RP is more than a protocol engine; its also a message handling process. The above is somewhat obviously contradicted in the case of the localid being an i-number when RP is itself an i-broker - an entity that knows and relies upon addiional semantics of i-numbers when delivering i-services - including "XRI-enhanced " OP services.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>So on the grounds that one contradiction often leads to interesting others, other schemes for localid could similarly be interpreted by classes of RP other than those in the i-broker class. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Perhaps we see this notion of an implicitely-typed localid already standardized in AX, where n RPs can conform a RP-community linked by localid (from a common OP, nominally) - allowing them to coordinate their own services based on the common persistent key value (e.g. some keyed-hash of the Yahoo-copyright localid, say)</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Its tempting to fall into the trap of looking at the localid as a reference-key into the distributed database of attributes maintained about objects maintained by OPs. With a little thought, you see how, the properties of uniqueness and non-ambiguity also make it (like any key) a linking value - between two disconnected identity spaces. This leaves behind the notion that the localid is merely a control value, issued by an OP authority. An RP can belong (like a trust bridge) in two worlds at once. This could be (1) the world of the OPs (generally, domineering federations full of policy wonks selling privacy services), and (2) the world of many sets of RPs cooperating (the mashup space(s), to use a modernism, full of individualists).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV></DIV>
<DIV id=idSignature43940>
<DIV><FONT face=Arial color=#000000 size=2><SPAN style="FONT-SIZE: 7.5pt">_________________________<BR></SPAN><B>Peter Williams<BR></B></FONT><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Webbee eSolutions (P) Ltd.<BR><B>Sent:</B> Mon 5/19/2008 7:13 AM<BR><B>To:</B> Peter Williams<BR><B>Cc:</B> Jonathan Daugherty; general@openid.net<BR><B>Subject:</B> Re: [OpenID] Fwd: Yahoo open id URL and which PHP Library<BR></FONT><BR></DIV></DIV>
<DIV><BR><BR>
<DIV class=gmail_quote>2008/5/18 Peter Williams <<A href="mailto:pwilliams@rapattoni.com" target=_blank>pwilliams@rapattoni.com</A>>:<BR>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>The testimonial is that you are not afraid to try, not afraid to fail, and not afraid to seek advice in public. I do all of those things, all the time (particularly, the failing bit). This publicity of success is all the testimonial one can really hope for. From your example, you can be assured that someone else will now also try...and probably succeed.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV></DIV></DIV></BLOCKQUOTE>
<DIV><BR>One last question from me at this topic,<BR>I have successfully integrated but the identifier i receive from yahoo is like <SPAN class=customoid><A href="https://me.yahoo.com/a/ZZNIxYUnztRe6GC7wNo5sEf6212J#4234" target=_blank>https://me.yahoo.com/a/ZZNIxYUnztRe6GC7wNo5sEf6212J#4234</A><BR><BR>Can it be changed by some user whose identifier it is and do i have to store in this form, i mean it has # sign also.<BR></SPAN></DIV></DIV>Regards,<BR>Abhi </DIV></BODY></HTML>