<html>
<body>
<font size=3><br>
<blockquote type=cite class=cite cite="">Apply that same concept to a
global namespace and it actually becomes rather easy for every human on
the planet to have a relatively easy-to-remember, easy-to-say,
easy-to-transcribe address</font></blockquote><br>
This has an interesting relationship to our idée fixe that names are
composed from first-or-given-name and last-or-surname. (with possible
additional parts). <br><br>
Out in the Sahara, my name is not 'Joaquin Miller', but 'Joaquin
Coulterville' (this would be written by the blue (ladies and) men in the
alphabet of Tamasheq, with sufficient squiggles to get the unfamiliar
pronunciation right). <br><br>
There are lots of people in Burma named, 'Nu'. The famous one might have
used i-name, '=U.Nu' ("Mr." Nu), if he got there first, or
maybe ='Nu.United.Nations'. Another, might use a name, in Myanma
script, which we would translate as "equal
Nu.Shwedagon.South.Entrance.Candy" because most people know him as
the gent who has the little tray of unusual candies for sale near the
Southern mouk to Shwedagon Paya. <br><br>
So what's my point? Three:<br><br>
The only practical schema for person names is a free-form character
string. <br>
While xri.net-rooted i-names can serve as temporary identifiers for
people, <br>
we need to turn to i-numbers for permanent identifiers.<br>
The only practical overall schemes I have heard tell of are those
like <br>
<a href="http://www.skyhunter.com/marcs/petnames/IntroPetNames.html" eudora="autourl">
<font size=3>
http://www.skyhunter.com/marcs/petnames/IntroPetNames.html</a> .<br><br>
</font>Cordially, Joaquin Coulterville<br><br>
<br><br>
</body>
</html>