[urn] Re: URN Namespace Registration for International Stand ard Name Identifier
Peter Saint-Andre <[email protected]> Wed, 15 Oct 2025 15:37:01 -0600
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
The delay is my fault. It appears I dropped the ball, perhaps waiting to see if other expert review team members had feedback. I'll submit this to IANA very soon! Peter On 10/15/25 10:17 AM, Paul Jessop wrote: > Hi Peter, all, > > Can I enquire where this has got to? I may well have dropped the ball > myself but having been in and out of hospital over the last 12 months it > wouldn’t be the only thing. I cannot find anything more recent than the > message below. > > All the relevant experts seem to be very comfortable with the text and I > have reviewed it to make sure nothing has become invalid in the past > year. Rather to my surprise, what was a somewhat academic “completeness” > exercise has acquired real-world urgency as some deepfake driven > initiatives are asking that participating identifiers be expressible as > URNs. > > Can Peter let me know? > > Best regards, > > Paul Jessop > Adviser to ISNI International Agency. > > *From: *Peter Saint-Andre <[email protected]> > *Date: *Monday, 16 September 2024 at 21:20 > *To: *Paul Jessop <[email protected]>, Dale R. Worley > <[email protected]> > *Cc: *[email protected] <[email protected]>, [email protected] <[email protected]> > *Subject: *Re: [urn] Re: URN Namespace Registration for International > Standard Name Identifier > > Hi Paul, > > Your edits look good. I'm in favor of registering this namespace with > all due speed. > > Peter > > On 9/12/24 6:54 PM, Paul Jessop wrote: > > Hi, > > > > Here is the updated registration request. It has been extensively > > revised to address the comments made. > > > > I hope the encoding is correct now. I didn’t understand about byte order > > marks, so this has been an education as well! I don’t think the text > > actually needs UTF-8 encoding now anyway. > > > > Best regards, > > > > Paul > > > > Paul Jessop county analytics ltd > > > > --------------------------------------------- > > > > rights - technology - markets - music - media > > > > --------------------------------------------- > > > > ISNI 0000 0005 1119 3335 > > > > --------------------------------------------- > > > > [email protected] +44 7850 685378 > > > > On 12/09/2024, 11:09, "Paul Jessop" <[email protected] > > <mailto:[email protected] <mailto:[email protected]>>> > wrote: > > > > Thanks both. All seems sensible. I will rework and resubmit. > > > > I'm sorry about the text file format. I think I spent my energy on Mac > > CR/LF issues and neglected the character set mis-match! > > > > And now that the experts are aware that the minor revision doesn’t > > affect anything at issue here, it can safely disappear. > > > > Best regards, > > > > Paul > > > > Paul Jessop county analytics ltd > > > > --------------------------------------------- > > > > rights - technology - markets - music - media > > > > --------------------------------------------- > > > > ISNI 0000 0005 1119 3335 > > > > --------------------------------------------- > > > > [email protected] <mailto:[email protected] > <mailto:[email protected]>> > > <mailto:[email protected] <mailto:[email protected] > <mailto:[email protected]>>> +44 > > 7850 685378 > > > > On 11/09/2024, 19:22, "Peter Saint-Andre" <[email protected] > > <mailto:[email protected] <mailto:[email protected]>> > <mailto:[email protected] > > <mailto:[email protected] <mailto:[email protected]>>>> wrote: > > > > In addition to Dale's feedback, which seems sensible to me, I would > > > > suggest the following changes: > > > > - for the registrant, include a role address at isni.org, not Paul's > > > > personal email address; this can help with future communications > > > > - because the RFC 8141 registation template does not have a "Background" > > > > or a "Benefits" section, move that information to the appropriate > > > > sections in the template (mainly "Purpose") > > > > - move the "Character set" information to the "Syntax" section (again, > > > > there is no "Character set" section in the template) > > > > - remove the sentence about current minor revisions to ISO 27729 since > > > > that information is rather ephemeral > > > > Peter > > > > On 9/11/24 10:08 AM, Dale R. Worley wrote: > > > > > 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] <mailto:[email protected] > <mailto:[email protected]>> > > <mailto:[email protected] <mailto:[email protected] <mailto:[email protected]>>> > > > > > To unsubscribe send an email to [email protected] <mailto:urn- > > [email protected]> <mailto:[email protected] <mailto:[email protected] > <mailto:[email protected]>>> > > > _______________________________________________ urn mailing list -- [email protected] To unsubscribe send an email to [email protected]