[urn] Re: URN Namespace Registration for International Stand ard Name Identifier

[email protected] (Dale R. Worley)
Newsgroups gmane.ietf.urn
Message-ID <[email protected]>
There seems every reason to approve this registration.  However, I
suggest these small changes:

- There are occurrences of the character "?" in the document that seem
to replace non-ASCII characters in an original version.  These should
either be replaced with appropriate ASCII characters, or the document
revised to use UTF-8 encodings of the original characters.

- Add a note for implementors that the resolution process may include
one or more HTTP redirections.  Implementors should be prepared for this
anyway, but it's useful to warn them.

- I notice that the current registration template in RFC 8141 doesn't
have an explicit "uniqueness and persistence" section, but I recommend
adding a section on uniqueness to assemble these points, as there are
certain subtleties involved:

    [as already in Background] ISNI does not identify the underlying
    natural or legal person and several ISNIs may be associated with
    such a person if it presents multiple identities (such as personas)
    to the public.

    [as already in Assignment] Where two ISNIs are later discovered to
    refer to the same identity, these registrations are merged, the
    unused ISNI is retained but marked as deprecated and it is linked to
    the other ISNI.

    [It seems to me that what constitutes an "identity" is a *cultural*
    question, and specifically not a technical one.  Perhaps ISNI-IA or
    the ISO standard has nice boilerplate to state this.]

Dale

_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.