Excellent arguments Martin. I concede. :)<br>
<br>
Do you see value in using the <a href="http://OpenID.name">OpenID.name</a>? <br>
<br>
If you consider that .name invokes an identification then this domain
could very easily represent a way of labeling and identifying system
nodes, and if a common naming convention were to be agreed upon
then it seems the task of software distribution, bug
reporting, feature requests, development status, etc... could be built
out and propogated from the very beginning and as such develop a system
that is easy to become a member of, easy to syncronize with the latest
bits, report bugs to a common tracking system, check code in and out,
exchange coding ideas across the entire system, etc.. <br>
<br>
using naming conventions such as:<br>
<br>
<a href="http://dev.channelxml.com.OpenID.name">dev.channelxml.com.OpenID.name</a><br>
<a href="http://test.channelxml.com.OpenID.name">test.channelxml.com.OpenID.name</a><br>
<a href="http://prod-1.channelxml.com.OpenID.name">prod-1.channelxml.com.OpenID.name</a><br>
<a href="http://prod-2.channelxml.com.OpenID.name">prod-2.channelxml.com.OpenID.name</a><br>
<br>
Could lend really well to ensuring that software updates, bug fixes,
security holes, etc... find there way to the right environment in every
node on the system. Forgive me if I am thinking too grandeur
here. This is the exact system I have been designing for the
ChannelXML project and what makes sense for that project might be total
overkill for this. Still, its better to put things out there to
allow for proper consideration as the reverse tends to lend well to
digression where as progression is all I can imagine any of us
have ever wanted.<br>
<br>
Thanls again for your excellent counterpoints Martin! :)<br>
<br><div><span class="gmail_quote">On 5/27/05, <b class="gmail_sendername">Martin Atkins</b> <<a href="mailto:mart@degeneration.co.uk">mart@degeneration.co.uk</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;">
M. David Peterson wrote:<br>> Separation of trivial is all a matter of who you are talking to. People<br>> understand <a href="mailto:foo@bar.com">foo@bar.com</a> to mean an individual email address. Most think of a
<br>> website when they see <a href="http://foo.bar.com">foo.bar.com</a> <<a href="http://foo.bar.com">http://foo.bar.com</a>> or<br>> <a href="http://foo.bar.comand">http://foo.bar.comand</a>, as a technical detail to you or me, causes them
<br>> to wonder why they have<br>> to go to that site first and then what they have to do when they get there<br>> and.... the unsurities and anxietys of the unknown technology are more than<br>> worth the effort to regex an @ to . if it now means "oh, Ive used my email
<br>> address before to log in to a site... thats easy...<br>><br>> all of this means higher adoption rate and I would bet that rate difference<br>> to be quite considerable<br>><br><br>Most users aren't going to know it's a URL. For example, LiveJournal's
<br>documentation will say "Type <a href="http://username.livejournal.com">username.livejournal.com</a> into the OpenID<br>Login box, where 'username' is your LiveJournal username". Users will<br>then go ahead and do that, blissfully unaware of what is going on behind
<br>the scenes.<br><br>What I *would* like is a way to clean up URLs which have slashes in<br>them. Some sites aren't going to want the wildcard DNS, perhaps because<br>they already have one or more real hostnames in the zone which conflict
<br>with usernames, so they're going to have identity URLs like<br><a href="http://mysite.com/username">mysite.com/username</a>, which looks quite odd.<br><br>However, adding lots of little URL preprocessing rules isn't the answer.
<br>If that route is taken, inevitably every consumer will implement them a<br>little differently and users will wonder why <a href="mailto:username@livejournal.com">username@livejournal.com</a><br>works on one site but not on another.
<br><br>I think that it looking like an email address would put off a lot of<br>people. I certainly don't like giving my email address to arbitrary<br>sites, as I never know what they're going to do with it. Sure, I know<br>
that in this case it's not really an email address, but most users will<br>not. Also, as soon as we start playing the "it looks like an email<br>address" game, people will wonder why they can't just use their Hotmail
<br>account instead of their LiveJournal account.<br><br>_______________________________________________<br>yadis mailing list<br><a href="mailto:yadis@lists.danga.com">yadis@lists.danga.com</a><br><a href="http://lists.danga.com/mailman/listinfo/yadis">
http://lists.danga.com/mailman/listinfo/yadis</a><br></blockquote></div><br><br><br>-- <br>M. David Peterson <aka:xmlhacker/><br><a href="http://www.xsltblog.com">http://www.xsltblog.com</a>