Add DOI, ISNI, ORCID iD, ROR ID entries to ExternalIdentifierType

[bact]

To resolve #1185, add these new external identifier types to support identification of person, organization, document (artifact), and dataset, in the context of open science, FAIR (Findability, Accessibility, Interoperability, and Reusability) data management, and intellectual property-related use cases (some of these can also be used for supply chain use cases):

Entry	Full name	Defined in	Can be use with these Element subclasses	Domains
ark	Archival Resource Key	ARK Identifier Scheme	File	Dataset (intellectual property declaration)
bic	Business Identifier Code	ISO 9362	Organization	Operations, SupplyChain
doi	Digital Object Identifier	ISO 26324	Artifact, Package, DatasetPackage, Requirement, Specification	AI, Dataset, open science
ecli	European Case Law Identifier	ECLI	Regulation	Any
eli	European Legislation Identifier	ELI	Regulation	Any
ibid	International Business Identifier	ISO/DIS 25500-3	Organization	Operations, SupplyChain
ibrn	International Business Registration Number	ISO 8000-116	Organization	Operations, SupplyChain
isan	International Standard Audiovisual Number	ISO 15706	File, DatasetPackage	AI, Dataset (intellectual property declaration)
isbn	International Standard Book Number	ISO 2108	File, DatasetPackage, Specification	AI, Dataset (intellectual property declaration)
iscc	International Standard Content Code (ISCC)	ISO 24138	File, Dataset	AI, Dataset
isci	International Standard Collection Identifier	ISO 27730	Bundle, DatasetPackage	AI, Dataset (intellectual property declaration)
isil	International Standard Identifier for Libraries and Related Organizations	ISO 15511	Organization	Open science
ismn	International Standard Music Number	ISO 10957	File, DatasetPackage	AI, Dataset (intellectual property declaration)
isni	International Standard Name Identifier	ISO 27729	Person, Organization	Any
isrc	International Standard Recording Code	ISO 3901	File, DatasetPackage	AI, Dataset (intellectual property declaration)
issn	International Standard Serial Number	ISO 3297	Bundle	AI, Dataset (intellectual property declaration)
iswc	International Standard Musical Work Code	ISO 15707	File, DatasetPackage	AI, Dataset (intellectual property declaration)
lexid	LEX Identifier	RFC 9676	Regulation	Any
nli	Natural Location Identifier	ISO 8000-118	PhysicalLocation	Operations, SupplyChain
orcidid	Open Researcher and Contributor ID (ORCID) iD	ORCID	Person	Open science
rorid	Research Organization Registry (ROR) identifier	ROR	Organization	Open science

IDs and related use cases:

1. doi, orcidid, rorid, isbn and other identifiers of documents support the use of SBOM in open science (same area as CodeMeta and Zenodo) and will support the AI model classification under Model Openness Framework (MOF, another Linux Foundation project)
2. ecli, eli, lexid are useful for requirement/specification documentation
3. isan, isbn, isci, ismn, isrc, and other identifiers for creative works can be used to facilitating the intellectual property documentation.
4. doi, ibid, isni, nli are generic and can be applied to domains

The (1) and (2) are main use cases when this PR started - primary use case is MOF classification. (3) is more of an expansion for non-text creative works. (4) is generic and can be applied outside the domains of the original proposal.

[kestewart]

@bact - I don't think we need to wait for 3.2 for these. The types look well defined. I've marked for 3.1-rc2, so if you remove draft we can consider after -rc1 goes out.

[rgopikrishnan91]

LGTM

[bact]

• Remove IBAN which can be sensitive, based on feedback from 21 Jan 2026 AI WG call.
  • The rest of the list are good. No objections.
• Update PR description to make it clearer about potential use cases, based on questions from 21 Jan 2026 AI WG call.
• A concern from the call: Should this be in 3.1? as it adds something to Core and it is not in 3.1-rc1.
  • In defense, that 3.1-rc2 is possible, this PR does not introduce new class or property or vocabulary, only additions to existing vocabulary and all of the entries are well-defined/backed by reputable authority. No change or removal of existing class/property.
  • But 3.2 (the original target) is fine too.
  • The AI WG suggests we should bring this to the Tech call on Tuesday.

[bact]

@bennetkl updated as agreed in yesterday call / 21 Jan 2026 AI WG, please review.

[bact]

Note: Victor has suggested resources for FAIR principles and related identifiers:

• https://direct.mit.edu/dint/article/2/1-2/30/9992/
• https://fair-checker.france-bioinformatique.fr/

[bennetkl]

Thanks for updating the PR based on Jan 21 WG meeting. It looks good, but we should still just check that integrating in SPDX 3.1 RC2 is ok with Tech group

[bact]

This report - "Interoperable, trustworthy, and machine-readable copyright data in the AI era : Report of the CITF First Project" - discussed about the use of "asset identifiers" (DOI, ISBN, ISSN, ISCC) and "agent identifiers" (ISNI), together with assertion information (C2PA) for EU regulation compliance. https://okm.fi/julkaisu?pubid=URN:ISBN:978-952-415-143-6

[stevenc-stb]

LGTM

[ElyasRashno]

I suggest adding a short illustrative example in the spec or model documentation to improve clarity for adopters.

[ElyasRashno]

@bact, I’d be happy to help provide illustrative examples if you think that would be helpful.

[bact]

@ElyasRashno sure, please. That will be fantastic.

[bennetkl]

@ElyasRashno Do you plan to add an example for this PR?