tag:blogger.com,1999:blog-6894552.post2610880835565772082..comments2008-07-27T02:14:15.169-07:00Comments on JMPInline: How I have taken control of my own identity, part ...Andrew Arnotthttps://profiles.google.com/114635397638720587251noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6894552.post-15322054054679067372008-07-27T02:14:00.000-07:002008-07-27T02:14:00.000-07:00Hi Derigel,<br><br>First of all thanks for the fee...Hi Derigel,<BR/><BR/>First of all thanks for the feedback on DotNetOpenId. You bring up an interesting suggestion about the xri:// prefix that I will have to investigate more fully. But my understanding of the URI spec means that xri:// stuck in front of an XRI does not necessarily make it a valid URI -- but I'm not certain. So putting the xri:// prefix just might be misleading. But I'll lookAndrewhttp://www.blogger.com/profile/13632400519774640095noreply@blogger.comtag:blogger.com,1999:blog-6894552.post-88031730640105190672008-07-24T02:22:00.000-07:002008-07-24T02:22:00.000-07:00Greate article Andrew!<br>A little questions about...Greate article Andrew!<BR/>A little questions about your excellent library dotnetopenid. It returns for I-Names, for mine for example, follow =!F03.B700.8A22.C1E8, but others implementation of OpenID, from python for example, returns xri://=!F03.B700.8A22.C1E8. Is any standard of presentation XRI in OpenID? Second option is better IMHO, it's valid URI.derigelhttp://team23.ru/noreply@blogger.com