By centralized namespace I assume you mean having a centralized system
that each node relies upon to complete a transaction? This is not
what I am suggesting at all. This is a backdoor, lets keep things
solid and tight and allow easy access to each other without requiring
anything. Think of it as more of a Subversion-styled system where
everything is independent and yet with the proper credentials can be
given access to the latest tagged bits or check code into a stream,
etc... <br>
<br>
You can be independent without being severed completely from a system. Having backdoor access allows for exactly this.<br><br><div><span class="gmail_quote">On 5/27/05, <b class="gmail_sendername">Evan Martin</b> <<a href="mailto:evan.martin@gmail.com">
evan.martin@gmail.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;">On 5/27/05, M. David Peterson <<a href="mailto:xmlhacker@gmail.com">
xmlhacker@gmail.com</a>> wrote:<br>> Excellent arguments Martin. I concede. :)<br>><br>> Do you see value in using the <a href="http://OpenID.name">OpenID.name</a>?<br><br>The whole point of OpenID as opposed to [insert system name here] is
<br>that there isn't a centralized namespace.<br></blockquote></div><br><br><br>-- <br>M. David Peterson <aka:xmlhacker/><br><a href="http://www.xsltblog.com">http://www.xsltblog.com</a>