Re: [xdi] reserved words disallowed for e-names

[Fen Labalme <fen@idcommons.org>]

My thinking about why some names ought to be reserved regards 
documentation, similar to RFC2606 that reserves e.g. example.com.  Being 
able to write documentation that includes examples like 
'@community/member' and '=user' without these names referring to actual 
entities is, IMO, valuable.

I agree that if any names are reserved at all, it would be most 
important that they are reserved at the root, e.g., the = and @ name spaces.

Note that I also pose the question of disallowing one and two-character 
e-names, and e-names with any xri-reserved character in them (though the 
ABNF allows (e.g) this subset:  ;!*@&=+$,

Fen


Loren West wrote:
> I'm not sure why we need to reserve any of these names.
> If so, maybe only at the root.  Remember, XDI resources
> describe people (identities) as well as data within
> those identities (business cards, etc).
> 
> Although it doesn't make much sense to register people
> with those restricted words, I could imagine a few 
> thousand other words that don't make much sense, but
> I wouldn't know why we would want to disallow them.
> 
> Can you describe to me why you want to restrict e-names,
> and if so, in what namespace (=/$/@ - or some other namespace)?
> 
> Thanks,
> 
> =Loren
> 
> -----Original Message-----
> From: Fen Labalme [mailto:fen@idcommons.org] 
> Sent: Wednesday, May 12, 2004 10:55 PM
> To: XDI TC
> Subject: [xdi] reserved words disallowed for e-names
> 
> 
> At the TC meeting in New Orleans, I mentioned that we may want to 
> disallow some words as e-names in the same way the DNS Registries 
> disallow single letter names and (e.g.) example.com
> 
> I have taken a stab at an initial set of reserved words here:
> http://xrixdi.idcommons.net/moin.cgi/EnamesAndEnumbers#head-bb873c830605d42e
> 40754efd118bfc9bcdb75c17
> 
> Please read and comment.
> 
> Thanks,
> Fen
> 
> PS: I'm not a member of the XRI list - perhaps this note should be 
> forwarded there, too?
>