Re: Registration request for urn:eris: namespace

> To restate what I meant in a way that hopefully is clear, what I don't
> like about the current proposal is that the identifiers aren't
> *location-independent*.

To flesh out some aspects of this:  On one hand, I'm objecting that the
design of the namespace doesn't allow, doesn't conceptualize, that the
URNs are location-independent names.  On the other hand, I'm proposing
ways that the namespace can reserve a subspace for identifiers that,
indeed, aren't location-independent names.

This is like what happens with IP addresses.  IP addresses, of course,
are globally unique.  Except for 10.0.0.0/8 addresses et al., which only
have a meaning within a local context that defines it.

The current Eris proposal, both in concept and in details, is like the
identifiers passed around in all distributed file systems:  "filesystem
ID"/"file ID"/"block offset".  None of those consider their identifiers
to be *names*.  But while I want y'all to reconceptualize the namespace
as names and add details to support that, I don't want you to have to
adjust your experimental implementations to have to support real names
yet.

Dale