Dear Vladimir
According RFC 2141, the second element of URN should be the namespace
identifier (NID) followed by namespace specific string (NSS):
from: http://www.ietf.org/rfc/rfc2141.txt
[All URNs have the following syntax (phrases enclosed in quotes are
REQUIRED):
<URN> ::= "urn:" <NID> ":" <NSS>
where <NID> is the Namespace Identifier, and <NSS> is the Namespace
Specific String. The leading "urn:" sequence is case-insensitive.
The Namespace ID determines the _syntactic_ interpretation of the
Namespace Specific String (as discussed in [1]). ]
So, maybe the Martin's example should be codified as:
ID of P.Picasso in 4-dimensional space:
urn:crm:actor:aacr2:picasso.pablo/1881-1973
Best Regards,
Joao Oliveira Lima
On Wed, Dec 17, 2008 at 10:47 AM, Vladimir Ivanov <[email protected]> wrote:
> Dear All,
>
> It is common point of view that,
> real world objects could be represented in a
> multidimensional (data) space
> (I suppose that in our case the space correspond to schema of URN etc.).
>
> Martin's example:
>
> ID of P.Picasso in 4-dimensional space:
> urn:crm_actor:aacr2:picasso.pablo/1881-1973
>
> If I get the idea of discussion correctly, there are
> a lot of proposals for such a (necessary & sufficient) spaces
> that could be used to create(refer to) an unique identifier
> of a given object (e.g. museum).
>
> And we are trying to find one appropriate space (or schema) for
> identification.
>
> Maybe we should talk not about spaces and dimensions themselves, but
> about transformations between different spaces with different dimensions
> that preserve identity.
>
> Best regards,
> Vladimir
>
