[urn] URN Namespace Registration for International Standard Na me Identifier
Paul Jessop <[email protected]> Wed, 15 Oct 2025 16:17:43 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
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]>> 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]>> +44 > 7850 685378 > > On 11/09/2024, 19:22, "Peter Saint-Andre" <[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]>> > > > To unsubscribe send an email to [email protected] <mailto:urn- > [email protected]> <mailto:[email protected] <mailto:[email protected]>> > _______________________________________________ urn mailing list -- [email protected] To unsubscribe send an email to [email protected]
Namespace Registration for International Standard Name Identifier - 2024-09-12.txt
(text/plain, 6.4 KB)
Namespace Registration for International Standard Name Identifier (ISNI) Namespace ID: ISNI Requested of IANA. Version: 1.0 Date: 2023-09-12 Registrant: Name: Paul Jessop E-mail: [email protected] Affiliation: Adviser to ISNI International Agency (ISNI-IA) Address: Web URL: https://isni.org Purpose: The purpose of the ISNI namespace is to allow the representation of ISNI identifiers as URNs. An ISNI is an identifier for the public identity of a party in the media content industry - that is the identity presented to the public. ISNI is an international standard under ISO 27729 and ISO has appointed the ISNI International Agency (ISNI-IA) as the registration authority. ISNI-IA publishes documentation explaining how to implement ISNI and revises this from time to time. Advice is available on the ISNI-IA website at https://isni.org and includes information on implementation details that are not contained in the international standard. 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. It is possible to resolve an ISNI by using the website or by prepending https://isni.org/isni/ and performing an http GET. The resolution process may include one or more HTTP redirections. The following benefits are envisaged: 1. When represented as URNs, ISNIs are fully compliant URIs as required by certain systems. 2. When represented as URNs, ISNIs can be easily located within text by machines and humans, even without the resolver address https://isni.org/isni/. 3. When represented as URNs, ISNIs can in the future become technology independent hyperlinks without the proxy address. 4. URN Q- and R-components might in the future be used with ISNI in order to send requests to the target system or resolver, provided that the ISNI resolver is enhanced with support for these URN features. Syntax: The ISNI Namespace-Specific String (NSS) follows the syntax and content of the represented ISNI, as specified in ISO 27729. The NSS comprises a fixed length string of 16 characters consisting of 15 decimal digits and a check digit which is either a decimal digit or the alphabetic character "X". The use of a lower-case "x" is strictly non-conformant but in practice, systems may treat is as its upper-case equivalent. ISO 27729 requires that when an ISNI is "written, printed or otherwise presented in a human-readable format" it is preceded by "ISNI" and a space, and split into blocks of four characters separated by a space. This does not affect the identifier itself which is the sixteen characters. EXAMPLE "0000000121241960" is the ISNI of Elvis Presley. "ISNI 0000 0001 2124 1960" should appear on-screen. "urn:isni:0000000121241960" is the URN-ISNI for the same referent. The following formal definition uses ABNF [RFC5234]. URN-ISNI = "urn:isni:" ISNI-NSS ISNI-NSS = 15DIGIT ISNI-CHECK-DIGIT DIGIT = %x30-39 ISNI-CHECK-DIGIT = DIGIT / %x58 Rules for lexical equivalence: Two URN-ISNIs are equivalent if corresponding characters of each ISNI-NSS are identical. It is recommended that a strictly non-conformant lower case "x" as the check-digit is converted to an upper-case "X" before comparison is made. URN F-, Q- and R-components SHALL be ignored in the comparison since they are not part of the NSS. Because the ISNI-NSS has the same content as the corresponding ISNI, the same test can be applied to the comparison of a URN-ISNI and an ISNI. Where comparison is made between a URN-ISNI and the presentation format of an ISNI, the prefixed "ISNI" and the spaces shall be removed before comparison is attempted. EXAMPLE The following representations of an ISNI name SHALL be regarded as equivalent: 0000000121241960 ISNI 0000 0001 2124 1960 urn:isni:0000000121241960 ISNI assignment: ISNI assignment is managed by ISNI-IA through its registration agencies and the appointed assignment agency. Their roles and responsibilities are documented on the ISNI website. Uniqueness: The assignment of an ISNI requires that the applicant provide sufficient disambiguating information to describe the identity to the degree that is necessary to distinguish it as a separate name within the ISNI system. Where two ISNIs are later discovered to refer to the same identity, these registrations are merged but the unused ISNI is retained but marked as deprecated and aliased to the preferred ISNI. The effect of these policies is that there is exactly one information record associated with each assigned ISNI. This record is managed to represent a single name. Because a single party may present multiple identities (such as personas) with different names, there may be several ISNIs associated with that party. ISNI-IA publishes guidance on when multiple names associated with an entity should (a) be regarded as different identities and assigned different ISNIs and when they should (b) be regarded as name-variants of the same identity. Persistence of ISNI information is a key aim of the ISNI system and is a key objective of ISNI-IA which has sustainability as a prime operating target. Security and Privacy: ISNIs do not have any unmanaged privacy issues. Detailed examination has assured ISO and ISNI-IA that the ISNI system is in compliance with privacy and data protection requirements such as the General Data Protection Regulation of the EU and the California Consumer Privacy Act. Interoperability: ISNIs do not have any known interoperability related problems. ISNI registrations may contain other identifiers relating to the same identity and routinely do so. These other identifiers can be accessed when resolving an ISNI. Resolution: URNs in the URN:ISNI namespace SHALL be resolvable. Each resolution of a URN in the URN:ISNI namespace SHALL return information about the identity represented by the ISNI in the ISNI-NSS. To resolve a URN in the URN:ISNI namespace, the string to the right of "urn:isni: " is prepended with "https://isni.org/isni/" and an https GET performed. The ISNI website contains information on how to use the ISNI resolution process with parameters to allow access to the registered information in specific formats. Additional documentation / information: See ISO 27729 and the ISNI Website at https://isni.org. Revision Information: None