The openId spec doesn't specify best practice on exact format of identity urls. So it is impartial to:<br><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://id.mayfirst.org/username" target="_blank">
http://id.mayfirst.org/username</a> or <br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://id.mayfirst.org/username" target="_blank">http://username.id.mayfirst.org</a> or <br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://id.mayfirst.org/username" target="_blank">
http://username.mayfirst.org</a><br><br>Personally I wouldn't use the 2nd one because it seems confusing to me. I am using the equivalent of <a href="http://mayfirst.org/id/username">http://mayfirst.org/id/username</a>
, because I don't think normal users get subdomains. <br><br>The subdoman username id is used by a few providers now but is in no way a convention you need to follow a few do the equivalent of <a href="http://mayfirst.org/username">
http://mayfirst.org/username</a> (so if you can get away with that its a good option).<br><br>Immad<br><br>ps: I am basing my knowledge on the 1.1 spec, I assume it's not been changed for 2 but correct me if I am wrong.
<br><br><div><span class="gmail_quote">On 31/07/07, <b class="gmail_sendername">Peter Williams</b> <<a href="mailto:pwilliams@rapattoni.com">pwilliams@rapattoni.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How about typing in:-<br><br>javascript:WebForm_DoPostBackWithOptions(new<br>WebForm_PostBackOptions("ctl00$ctl85$ManageMySubscriptionLink", "",<br>false, "",<br>"<a href="https://msdn2.microsoft.com/en-US/subscriptions/manage/default.aspx">
https://msdn2.microsoft.com/en-US/subscriptions/manage/default.aspx</a>",<br>false, true))<br><br>I think the rule is that it is any URL that produces an HTML/XRDS stream<br>back.<br><br>Obviously its limited to any URL that the consumer has a URL resolver
<br>for. IN the case above, one would actually be required to first complete<br>webSSO.... so one gets rights to access the HTML/XRDS file for the<br>associated subscription at MSDN.<br><br>As I have just happen to have a USB security device that fills out my
<br>login web-form fields for me, it actually stuffed that string in my demo<br>Consumer when the sites OpenID-login form was presented :-) I just now<br>need to get a javascript resolver registered.<br><br>It's always useful to stress designs, to identify where limits are... or
<br>identity where they SHOULD be.<br><br><br><br>-----Original Message-----<br>From: <a href="mailto:general-bounces@openid.net">general-bounces@openid.net</a> [mailto:<a href="mailto:general-bounces@openid.net">general-bounces@openid.net
</a>] On<br>Behalf Of Jamie McClelland<br>Sent: Tuesday, July 31, 2007 4:39 PM<br>To: <a href="mailto:general@openid.net">general@openid.net</a><br>Subject: [OpenID] identity url suggested formats?<br><br>-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1<br><br>Hi all -<br><br>I'm very excited about the openid stuff - great work to everyone who has<br>contributed to this protocol!<br><br>I've just completed a test implementation of a server for May<br>
First/People<br>Link members.<br><br>The URL format we are using is:<br><br><a href="http://id.mayfirst.org/username">http://id.mayfirst.org/username</a><br><br>However, it seems like most folks are using:<br><br><a href="http://username.domain.org">
http://username.domain.org</a><br><br>For legacy reasons, we can't use:<br><br><a href="http://username.mayfirst.org">http://username.mayfirst.org</a><br><br>But we could use:<br><br><a href="http://username.id.mayfirst.org">
http://username.id.mayfirst.org</a><br><br>Hm.<br><br>I prefer<br><br><a href="http://id.mayfirst.org/username">http://id.mayfirst.org/username</a><br><br>Because it more cleanly separates out the domain from the username.
<br>However,<br>it seems like most people use the <a href="http://username.domain.org">http://username.domain.org</a> format and<br>I<br>don't want to adopt a format that is different from what most people are<br>using
<br>because it seems like it might confuse our members.<br><br>I was wondering...<br><br>Is <a href="http://id.mayfirst.org/username">http://id.mayfirst.org/username</a> valid? If so, are there reasons to go<br>with<br>one scheme over another scheme?
<br><br>Any suggestions would be welcome (including a link to RTFM :).<br><br>thanks,<br>jamie<br><br><br>- --<br>Jamie McClelland<br>718-303-3204 ext. 101<br><br>May First/People Link<br>Growing networks to build a just world
<br><a href="http://www.mayfirst.org">http://www.mayfirst.org</a><br>Members Local 1180, Communications Workers of America, AFL-CIO<br><br>PGP Key: <a href="http://mayfirst.org/jamie-pgp">http://mayfirst.org/jamie-pgp</a>
<br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.6 (GNU/Linux)<br><br>iD8DBQFGr8gBnq83YnbMBX0RAtNBAKCfbPkm7SoE4caQFxn2LGp16/ekHQCcCDxv<br>/7Oz7+DIZ1bfeMyFFpBj8ZQ=<br>=gbXC<br>-----END PGP SIGNATURE-----<br>_______________________________________________
<br>general mailing list<br><a href="mailto:general@openid.net">general@openid.net</a><br><a href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a><br>_______________________________________________
<br>general mailing list<br><a href="mailto:general@openid.net">general@openid.net</a><br><a href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a><br></blockquote></div>