Identification (the UNI)
Specifies how every artefact, data record and deployment context receives one permanent UNI (Unique Nexus Identifier) through catalogue or record-service allocation, how versions share it, and how it binds to DOI, ORCID, ROR and SWHID without being typed by hand, reused or treated as a mark. Each artefact of the area carries a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-1, NS-3, NS-6, NS-7, NS-9.
- Open standards: DataCite Metadata Schema 4.5; Research Organization Registry (ROR); ORCID iD; SoftWare Hash IDentifier (SWHID) v1.2; Decentralized Identifiers (DIDs) v1.0; UN M49 standard country or area codes.
- Data and feeds: ROR REST API v2; DataCite REST API (DOIs); ORCID public API v3.0; Wikidata Query Service.
- Couples with: Registries and the resolver; Data and datasets; Documentation and publication; Naming, marks and intellectual property.
- Nexus Standards
- 5
- NS-1, NS-3, NS-6
- Open standards
- 6
- named, never copied
- Data and feeds
- 4
- listed for reference
- Couplings
- 4
- with other areas
- Hali
- Proposedin the catalogue · in progress · scope STD
- Last reviewed
- area profile
Nexus Standards (2026). Identification (the UNI): area brief, Data and Evidence programme. Proposed. https://nexustandards.com/data/identification-standards/ · UNI NXS-STD-DC-000003. Last reviewed 17 October 2026.
Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.
Scope and boundaries
An area of the Data and Evidence programme (cross-cutting capabilities). The area profile sets out 5 matters in scope and 3 matters addressed by other areas.
In scope 5
- NXS-<SCOPE>-<CAT>[-<REGION>]-<SERIAL>[@<VERSION>] grammar, scopes, categories and record categories
- Catalogue allocation for artefacts (command-line minting) and record-service allocation for data records (append-only, scoped to each tenant)
- Contextual UNIs for deployments, instances and programme instances (NS-9)
- Legacy crosswalk (dotted UNI v0, NX-R/P/E/C registry aliases) and external bindings to DOI, ORCID, ROR, SWHID
- Embedding rules for files, pages, APIs (X-Nexus-UNI), datasets and operational workspaces
Out of scope 3
- Asserting truth, quality or authorisation of the identified object (the UNI identifies and resolves only)
- Issuing DOIs, ORCID iDs or ROR ids, which remain with their own registration agencies
- Personal identity of people (handled by identity-and-zero-trust-standards)
Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.
Foundation, referenced and implementing layers
The standards architecture of this context, from the foundation standards to the open standards referenced (grouped by type of relation) and the services and data sources that build on them.
The interactive view requires JavaScript; the sections below present the same records.
The service pipeline
A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against DataCite Metadata Schema 4.5; the service processes them and writes records with provenance; results are published, resolved and monitored, and a correction flows back through the same path. Nexus Standards applied: NS-1, NS-3, NS-9, NS-6, NS-7. 8 operations in 5 phases, built from the area profile: the rows carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the rules it implements (11). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.
Kichunguzi cha michakato · Standards · ratibu na sahihisha
Mzunguko wa maisha wa kiwango
Hatua 17·Awamu 6
Standards · ratibu na sahihisha
Mzunguko wa maisha wa kiwango
Mzunguko wa maisha wa kiwango · Njia ya NS-13 · Njia za michango · Njia ya IETF · Njia ya W3C · Njia ya OGC · Njia ya OASIS · Hatua za ISO na IEC · Ulinganifu · Mzunguko wa maisha wa rekodi · Uelekezaji · Ufuatiliaji.
Matokeo ya mzunguko huwa mapendekezo ya mabadiliko, Baraza la Viwango la Dunia hupitisha baada ya mwito wa mwisho wa umma, na kila nchi huamua upitishaji wake.
01 Elekeza misheni
- 01Elekeza misheni kwenye viwango na wasifuHatua · Nexus StandardsNexus Standards huelekeza kila misheni inayopendekezwa kwenye viwango na wasifu vinavyotumika.
02 Wasifu na ulinganifu
- 02Kusanya wasifu wa misheniHatua · Nexus StandardsNexus Standards hukusanya wasifu wa misheni na hurekodi upitishaji wowote wa kitaifa ambao misheni hutegemea.
- 03Thibitisha matokeo ya ujenzi dhidi ya wasifuHatua · Nexus StandardsNexus Standards huthibitisha matokeo ya ujenzi dhidi ya wasifu ulioundwa na kurekodi ushahidi.
- 04Fuatilia ulinganifu na urekodi ushahidi uliofungwaHatua · Nexus StandardsWakati wa Wiki ya Utekelezaji Nexus Standards hufuatilia ulinganifu na kurekodi mikengeuko.
03 Mapendekezo na mapitio
- 05Mikengeuko na marekebisho huwa mapendekezo ya mabadilikoHatua · Nexus StandardsMikengeuko huwa mapendekezo ya mabadiliko, na marekebisho hurekodiwa kama mabadiliko kwa ushahidi.
- 06Matokeo ya mzunguko huwa mapendekezo ya mabadilikoHatua · Nexus StandardsMatokeo ya mzunguko huwa mapendekezo ya mabadiliko: matokeo ya mbinu na masahihisho kutoka Ripoti (F06) na vipengele vya orodha kutoka Nexus…
- 07Andaa na urekebishe hadharaniHatua · Kamati na vikundi kaziKamati za kiufundi na vikundi kazi huandaa rasimu na kurekebisha viwango katika mchakato wazi wa NS-13.
- 08Pitia kuelekea uamuzi wa barazaHatua · Nexus StandardsNexus Standards huendeleza mapendekezo ya mabadiliko kupitia mapitio kuelekea uamuzi wa baraza.
04 Uamuzi wa Baraza
- 09Mwito wa mwisho wa ummaHatua · Baraza la Viwango la KimataifaBaraza la Viwango la Kimataifa hupitisha kwa wingi wa theluthi mbili baada ya mwito wa mwisho wa siku tisini.
- 10Kupitishwa kwa kiwango dunianiUamuzi · Global Standards CouncilBaraza la Viwango la Dunia huamua upitishaji wa kila kiwango baada ya mwito wa mwisho wa umma.
05 Chapisha na utambulishe
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 12UNI hutambulisha na kamwe haitoi chetiRekodi · Nexus StandardsKila kitu cha mwaka wa programu kina kitambulisho kimoja, UNI chini ya NS-1, ili kiweze kutajwa, kupewa matoleo na kutatuliwa.
- 13Chapisha mabadiliko yaliyopitishwa ya mwakaHatua · Nexus StandardsWakati wa upyaishaji Nexus Standards huchapisha mabadiliko yaliyopitishwa ya mwaka na hali ya upitishaji wa kitaifa.
06 Kupitishwa na kutumika kitaifa
- 14Kupitishwa kitaifa na Baraza la Viwango la KitaifaUamuzi · Baraza la Viwango la KitaifaBaraza la Viwango la Kitaifa la kila nchi huamua upitishaji wa kitaifa: kupitisha kama ilivyo, kupitisha kwa wasifu (NS-16), kurekebisha, au kurejelea tu.
- 15Viwango vilivyopitishwa hufikia kozi na matoleoHatua · Nexus StandardsKila kiwango au wasifu uliopitishwa huwa moduli ya kozi katika Risk Academy (F09), na viwango hutumika katika matoleo ya Reports (R1).
- 16Upitishaji ni wa mwisho kwa kila mamlaka ya kisheriaKiwango · Baraza la Kitaifa la ViwangoUpitishaji ni wa mwisho kwa kila mamlaka ya kisheria, na GSC haina kura ya turufu juu ya uamuzi wa kitaifa. Hakuna chombo cha kimataifa chenye kura ya turufu.
- 17Rekodi za kupitishwa kitaifaRekodi · Nexus StandardsWasifu wa misheni ulioundwa na rekodi za upitishaji wa kitaifa huenda kwa Foundry wakati wa maandalizi ya utayari (F08).
Nexus Standards · Nexus Standards (institution) · National Standards CouncilAn outline of the designed programme cycle, not a record of operation: no cycle has run and every programme is at service level R0. Every Nexus Standard is at the PROPOSED stage and nexustandards.com governs the text and status of each one. A UNI identifies and never certifies; a validator report is evidence for review, not a conformance claim.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record | Implements |
|---|---|---|---|---|---|---|
| 01 | Request | Request (start). The service covers: NXS-<SCOPE>-<CAT>[-<REGION>]-<SERIAL>[@<VERSION>] grammar, scopes, categories and record categories, Catalogue allocation for artefacts (command-line minting) and record-service allocation for data records (append-only, scoped to each tenant) and Contextual UNIs for deployments, instances and programme instances (NS-9). | a client, a person or a machine | the context is explicit in the request or on the record, never inferred | a request naming its context and inputs | NS16-R20 |
| 02 | Request | Identify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal. | the service | inputs are cited by UNI and version | inputs resolved to their UNIs and versions | NS1-R5, NS2-R2, NS0-P12 |
| 03 | Validation | Validate DataCite (gate). Open standards of this area: DataCite Metadata Schema 4.5, Research Organization Registry (ROR), ORCID iD and SoftWare Hash IDentifier (SWHID) v1.2. | the service’s validator | validated against the open standard’s own schema or validator where one exists | a validation run against DataCite Metadata Schema 4.5 and Research Organization Registry (ROR) | NS14-R2 |
| 04 | Processing | Process (model). Processing is reproducible from the inputs, the method version and the configuration. | the service | the method and version are recorded with the result | Catalogue allocation for artefacts (command-line minting) and record-service allocation for data records (append-only, scoped to each tenant) | NS12-R1 |
| 05 | Processing | Write records (record). Results are written append-only; a correction adds a version. | the service | every result carries what it was derived from | result records with provenance and a record UNI | NS0-P7, NS1-R3 |
| 06 | Publication | Publish and resolve (step). Results are discoverable and citable by UNI. | the service | writes return the allocated UNI; citations resolve | results reachable through the resolver, with the X-Nexus-UNI header | NS1-R5, NS2-R5 |
| 07 | Ufuatiliaji | Monitor (exercise). Data sources the service reads: ROR REST API v2, DataCite REST API (DOIs) and ORCID public API v3.0. Data sources are listed for reference; live data is displayed once licence review is complete. | the monitoring service | monitoring records are observations with record UNIs | observations of availability, drift and RDA FAIR Data Maturity Model RDA-F1-01M | NS11-R4 |
| 08 | Ufuatiliaji | Correction (end). Products that used a corrected record are listed and recomputed. | the data steward | a correction never overwrites; dependent results are replayed | a correction record that reaches every dependent result | NS1-R3, NS2-R4 |
Table.Operations in walking order; each row names the phase, the operation, its actor, its decision rule, the record it leaves and the rule identifiers it implements. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: DataCite Metadata Schema 4.5 · Research Organization Registry (ROR) · NS-1: The UNI and the artefact catalogue · NS-3: Risk record UNIs.
Standards that apply
The area profile lists 5 Nexus Standards; the registry lists NS-1, NS-3, NS-9 for this area. Each is a proposed standard under development.
- 01
NS-1 · The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)
Status: proposed · 10 requirements stated. Read NS-1 · Requirements for this area.
- 02
NS-3 · Risk record UNIs (grammar, legacy crosswalk, allocation authority)
Status: proposed · 0 requirements stated. Read NS-3 · Requirements for this area.
- 03
NS-9 · Contextual UNIs (deployments, instances, programme instances)
Status: proposed · 5 requirements stated. Read NS-9 · Requirements for this area.
- 04
NS-6 · Surface wiring (API header, panel provenance, passports, OpenAPI)
Status: in progress · 0 requirements stated. Read NS-6 · Requirements for this area.
- 05
NS-7 · Resolver landing pages, page meta tags, sitemap
Status: in progress · 0 requirements stated. Read NS-7 · Requirements for this area.
How a shock travels through this system
A system model of this area built from the registry: 5 systems, 4 sectors, 11 controls, 4 feeds, 3 indicators. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.
Systems and couplings
- Identification (the UNI)
- Rejista na kisuluhishi Muunganiko
- Data and datasets Coupling
- Nyaraka na uchapishaji Muunganiko
- Majina, alama na mali ya kiakili Muunganiko
Controls
NS-1UNI na katalogi ya vitu (sarufi v0.2: sehemu za kikoa, sekta, kanda na mazingira)NS-3UNI za rekodi za hatari (sarufi, ulinganishi wa urithi, mamlaka ya ugawaji)NS-9UNI za kimuktadha (utekelezaji, matukio, matukio ya programu)NS-6Uunganishaji wa nyuso (kichwa cha API, asili ya paneli, pasipoti, OpenAPI)NS-7Kurasa za kutua za kitatuzi, meta tagi za ukurasa, ramani ya tovutiNRS-A5Leseni na haki zilizojengwa ndaniNRS-H114Hazard family: Macroeconomic and fiscal shocks (NHS-1 soc.macro-fiscal)NRS-A1Viwango kama msimbo: viwango, mahitaji na majaribio yanayosomeka na mashineNRS-C4Modeli ya data za hatari, vitambulisho na ubadilishanajiNRS-H106Familia ya majanga: Teknolojia ya anga za juu na miundombinu ya obiti (NHS-1 tech.space-systems)NRS-U16Wasifu wa jukwaa la Universe: Institutional Funds Nexus
Observation
- ROR REST API v2 (listed for reference)
- DataCite REST API (DOIs) (listed for reference)
- ORCID public API v3.0 (listed for reference)
- Wikidata Query Service (listed for reference)
- Metadata is identified by a persistent identifier
- Metadata can be accessed manually (resolvable identifier)
- Proportion of children under 5 whose births have been registered (context for identity infrastructure, not a UNI measure)
Open standards referenced
6 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
adopt4
Research Organization Registry (ROR)RORlisted in the register · rorORCID iDORCIDlisted in the register · orcidSoftWare Hash IDentifier (SWHID) v1.2SWHID working group / Software Heritagelisted in the register · swhid-iso-iec-18670UN M49 standard country or area codesUN Statistics Divisionlisted in the register · un-m49Routing, monitoring and verification tools
Routing console
Select a sector, hazard family, capability and artefact type; the registry identifies the applicable standards and states the reasons.
Available · from the registryVerification console
Test suites, conformance statements and attestations for each standard, as recorded in the registry.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
Miunganiko ya kimfumo
4 couplings link this area to other areas and programmes, each with the mechanism of the link.
- Registries and the resolverOpen Infrastructure and DevelopersEvery UNI minted under NS-1 and NS-3 must resolve at /uni/{uni} with content negotiation; an identifier that does not resolve is treated as unallocated by the resolver.
- Data and datasetsData and EvidenceRecord UNIs (NS-3) carry recordVersion, so correction dependencies and source releases cite recordUni@recordVersion and a correction re-points dependants instead of overwriting them.
- Documentation and publicationData and EvidenceThe UNI is embedded in front matter, captions and DataCite exports; a DOI is recorded as an external binding only after licence review and is not minted in place of the UNI.
- Naming, marks and intellectual propertyFoundations and GovernanceSCOPE codes are an internal classification under NS1-R7; public labels come from the name architecture, so that a code does not become a product name.
Viashiria
The area profile names 3 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
Data sources
4 data sources named in the area profile, each with provider, licence, update frequency and delivery path.
Data sources are listed for reference; live data is displayed once licence review is complete.
- Hai
- 0
- on completion of licence review
- Listed in the data register
- 0
- licence terms recorded
- Proposed for the register
- 4
- licence terms to be recorded
- Delivery
- 3 governed service · 0 plugin · 0 browser · 1 snapshot · 0 listed for reference
- proposed paths in order of preference: governed data service, plugin, direct browser read, build-time snapshot; sources whose terms do not permit reuse are listed for reference only
DataCite REST API (DOIs)for reference
DataCite · continuous
CC0 1.0 (metadata)
governed data serviceproposed for the data register.
ORCID public API v3.0for reference
ORCID · continuous
Public data under CC0 1.0 per the ORCID public data policy.
governed data serviceproposed for the data register.
ROR REST API v2for reference
Research Organization Registry · data releases roughly monthly.
CC0 1.0 (registry data)
governed data serviceproposed for the data register.
Wikidata Query Servicefor reference
Wikimedia Foundation · continuous
CC0 1.0
build-time snapshotproposed for the data register
Restricted compatibility profiles
2 standards whose text is not openly available, named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.
- ISO 26324 Digital Object Identifier systemISOcompatibility profile (restricted)
- ISO 27729 International Standard Name IdentifierISOcompatibility profile (restricted)
Working group charter
A proposed charter for this area, open to institutions and experts.
Maintain the grammar, allocation, embedding and crosswalks of UNIs and their bindings to existing persistent identifier systems.
Institutions and experts are invited to charter this working group under NS-13 by filing a public change record. National Working Groups (NWGs) contribute national inputs and field exercises through their National Nexus Consortium (NNC).
- NS-1 edition with conformance classes and executable tests
- Crosswalk tables UNI to DataCite, ROR, ORCID, SWHID and DID
- Federated allocation profile for national resolvers
- DataCite liaison sought
- ROR liaison sought
- Software Heritage liaison sought
- W3C Credentials Community Group liaison sought
- RDA PID Interest Group liaison sought
Evidence, recognition and capital pathways
What each institution of the ecosystem draws from this area: The Global Centre for Risk and Innovation (GCRI Canada), as Secretariat, for evidence; The Global Risks Forum (GRF) for recognition; and The Global Risks Alliance (GRA) for capital.
GCRI Canada
GCRI Canada accepts an artefact as evidence only when its UNI resolves to a published record whose versions and correction history are reachable.
Global Risks Forum (GRF)
GRF recognition records cite the contextual UNI of the deployment or programme instance being recognised, rather than a free-text name.
Global Risks Alliance (GRA)
GRA capital-readiness files reference every dataset, model and trigger by UNI@version so that a later correction is traceable to the assessment it affects.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Open research questions
3 questions identified as priorities for the working group.
- Federated serial allocation across national resolvers without a global lock and without collisions that must later be reported and resolved.
- Binding a contextual UNI to a DID method (did:web versus did:key) without making key rotation change the identifier.
- Retrofitting UNIs onto legacy data records whose original identifiers were reused or ambiguous.
Intended users
The area profile identifies 4 user communities.
- Data stewards and repository managers
- Software and platform engineers
- Research librarians and publishers
- National statistical and mapping agencies
Hazards, threats and sectors concerned
Hazards and threats 0
This area draws on the hazards of the areas it is coupled with.
Sekta 0
This area serves all sectors through the areas it is coupled with.
Registry listing and depth pages
This area is in the catalogue (status: in progress; scope STD; 1 crosswalk domain). It has five depth pages and a register crosswalk of its domains.
Standards that apply
The rules of each listed standard, read through the specification reader.
Depth · CrosswalkUlinganifu
Every register entry in the area’s domains, by relation, with the crosswalk graph.
Depth · Records and schemasRecords and schemas
Scope, record, schema explorer and how a UNI resolves.
Depth · ConformanceUlinganifu
Clauses, evidence and attestations for conformance assessment.
Depth · ReadinessUtayari
The area alongside the three pathways, as a matrix.
The crosswalk as a table: 10 external standards by domain
| Domain | External standard | Issuing body | Relation |
|---|---|---|---|
| Identifiers and cataloguing | DataCite Metadata Schema 4.5 | DataCite Metadata Working Group | adopt |
| Identifiers and cataloguing | Digital Object Identifier system – ISO 26324 | ISO/TC 46/SC 9; International DOI Foundation | crosswalk |
| Identifiers and cataloguing | International Standard Name Identifier (ISNI) – ISO 27729 | ISO/TC 46/SC 9; ISNI International Agency | cite |
| Identifiers and cataloguing | ISO 3166-1 Codes for the representation of names of… | ISO/TC 46; ISO 3166 Maintenance Agency | adopt |
| Identifiers and cataloguing | Open Badges 3.0 | 1EdTech Consortium | adopt |
| Identifiers and cataloguing | ORCID iD (subset of ISNI, ISO 27729) | ORCID Inc. | adopt |
| Identifiers and cataloguing | Research Organization Registry (ROR) | ROR (California Digital Library, Crossref, DataCite) | adopt |
| Identifiers and cataloguing | SoftWare Hash IDentifier (SWHID) Specification V1.2… | Software Heritage; ISO/IEC JTC 1 | adopt |
| Identifiers and cataloguing | UN M49 Standard country or area codes for statistical use | United Nations Statistics Division | adopt |
| Identifiers and cataloguing | W3C Decentralized Identifiers (DIDs) v1.0 | W3C DID Working Group | profile |
Nexus Standards in the graph: NS-1, NS-3, NS-9. A relation is a register entry, never a compliance claim.
3 Nexus Standards · 1 domains · 10 external standards · 10 issuing bodies · 0 implementing repositories. Relations (adopt, profile, crosswalk, cite) are as recorded in the register; names and standards remain with their stewards.
Crosswalk graph24 nodes and 23 links from the registry of external standards, programme areas and implementations (the external standards register, the consumers register. Relations (adopt, profile, crosswalk, cite) are shown as recorded in the register.
Areas carry no geography of their own; the map shows where the bodies that issue the area’s external standards are based.
Issuing bodies and their seats (9)
| Body | Seat | Register entries |
|---|---|---|
| DataCite Metadata Working Group | Hannover, Germany | 1 |
| ISO/TC 46; ISO 3166 Maintenance Agency | Geneva, Switzerland | 1 |
| ISO/TC 46/SC 9; International DOI Foundation | Oxford, United Kingdom | 1 |
| ISO/TC 46/SC 9; ISNI International Agency | London, United Kingdom | 1 |
| ORCID Inc. | Bethesda, Maryland, United States | 1 |
| ROR (California Digital Library, Crossref, DataCite) | Hannover, Germany | 1 |
| Software Heritage; ISO/IEC JTC 1 | Paris, France | 1 |
| United Nations Statistics Division | New York, New York, United States | 1 |
| W3C DID Working Group | Cambridge, Massachusetts, United States | 1 |
Issuing bodies are shown at the city of their public seat. The 1 programmes, 0 implementing repositories and 19 Nexus Standards have no location and are not mapped · 1 issuing body has no single public seat and is listed without a location: 1EdTech Consortium.
Standards globe9 issuing bodies with a public seat and 10 register entries, shown in equal-area cells at four levels of detail. Seats are placed at city coordinates; programme areas, implementations and standards have no location and are not drawn. A still world map is shown where scripts are unavailable.
Vyanzo
4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedUnique, Persistent, Resolvable: Identifiers as the Foundation of FAIRData Intelligence · 2020peer-reviewed20 Years of Persistent Identifiers – Which Systems are Here to Stay?Data Science Journal · 2017peer-reviewedIdentifiers for the 21st century: How to design, provision, and reuse persistent identifiers to maximise utility and impact of life science dataPLOS Biology · 2017- standardDecentralized Identifiers (DIDs) v1.0W3C · 2022
Recent research on this area
Recent peer-reviewed articles, preprints, datasets and reports on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.
Search termspersistent identifier; persistent identifiers; digital object identifier; DataCite Metadata Schema; Research Organization RegistryDerived from the title and scope of the area, the NHS-1 hazards it names and the open standards it lists.
- OpenAlexlisted for reference; not queried
- Crossreflisted for reference; not queried
- DataCitelisted for reference; not queried
- Zenodolisted for reference; not queried
arXivlisted for reference; not queried- Europe PMClisted for reference; not queried
- OpenAIRE Graphlisted for reference; not queried
No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.
Risk Academy courses and disciplines
1 course and 2 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.
Kozi
Taaluma
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
Programmes, tracks and courses for this area
GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.
Utafiti na ushahidi
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
RegistryMaintains record provenance and registry interoperability.Apply to this programme Data and ComputeEngineers the data infrastructure on which resolvable identifiers depend.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, policy and convening
Global Risks Forum (GRF)
Tracks that convene public authorities, researchers and institutions on the governance of shared risks.
Research NexusWorks on research integrity and how evidence is interpreted across institutions.Join this track AI and Digital GovernanceExamines data governance and sharing and digital rights.Join this track globalriskforum.comAll tracks of The Global Risks ForumCapital, finance and markets
Global Risks Alliance (GRA)
Industry programmes in which financial institutions build a shared understanding of systemic risk.
Capital Markets NexusExamines market data quality, on which financial risk measurement depends.Join this programme globalriskalliance.comAll programmes of The Global Risks AllianceElimu na mafunzo
Risk Academy
Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.
Technology and DataRAT-204 · Intermediate · 19 learning hoursManaging risk data, AI, digital infrastructure and technology risk responsiblyTake this course All courses and disciplinesListed in the education and training section of this pageIstilahi kuu
- UNI
- Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
- inapendekezwa
- A draft in the open development process that the Global Standards Council has not yet adopted. Each area profile is a proposal to the Nexus Standards registry.
- crosswalk
- Relation in which clauses of these standards are mapped to parts of the external standard by clause number, without reproducing its text.
- adopt
- Relation in which the external standard is used as published and values are validated against it.
- profile
- Relation in which a Nexus profile narrows or extends the external standard for a defined use, validated with the issuing body’s own tools where these exist.
- compatibility profile (restricted)
- Relation to a standard whose text is not openly available: the standard is named and linked only, and any compatibility profile is kept on protected pages.
- change record
- A public record of a proposed change under NS-13, decided by the editors with written reasons.
- attestation
- An evaluator’s recorded result for one clause and one subject under NS-11.
- liaison sought
- A liaison the working group intends to request from the issuing body; a liaison is established only when the body confirms it in writing.
Related areas
Recent research and sources
Peer-reviewed articles, preprints, reports and datasets on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.
Curated references
- Identifiers for the 21st century: How to design, provision, and reuse persistent identifiers to maximise utility and impact of life science data
PLOS Biology · 2017 · Peer-reviewed - 20 Years of Persistent Identifiers – Which Systems are Here to Stay?
Data Science Journal · 2017 · Peer-reviewed - Unique, Persistent, Resolvable: Identifiers as the Foundation of FAIR
Data Intelligence · 2020 · Peer-reviewed - Decentralized Identifiers (DIDs) v1.0
W3C · 2022 · Standard
Related standards and frameworks
- DataCite Metadata Schema 4.5
DataCite - Research Organization Registry (ROR)
ROR - ORCID iD
ORCID - SoftWare Hash IDentifier (SWHID) v1.2
SWHID working group / Software Heritage - Decentralized Identifiers (DIDs) v1.0
W3C - UN M49 standard country or area codes
UN Statistics Division
Search terms, derived from the title and scope of the area: persistent identifier; persistent identifiers; digital object identifier. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.
Questions and answers.
What is the status of the Identification (the UNI) area?
How are data sources presented?
How can this brief be amended?
Changia ushahidi kutoka ukurasa huu.
Reports ni chapisho la kila robo mwaka la Muungano. Unachojua kuhusu somo hili kinaweza kuwa ushahidi, kisa au sahihisho katika toleo lijalo, kikitajwa kwa jina lako na kuchapishwa chini ya CC BY 4.0 pale ambapo ni kazi yako mwenyewe.
- Barua pepeLango GW-STDItume kutoka ukurasa huuUshahidi, masahihisho, kisa, mbinu, mapitio, tafsiri au mchango wa wasifu. Inafika ikiwa na alama ya ukurasa huu, ili mhariri anayeumiliki aipokee.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Usitume kamwe data binafsi, maelezo nyeti ya miundombinu wala chochote ambacho huna haki ya kukishiriki. Mchango hupitiwa kabla ya kutumika; kuutuma hakutoi haki za uandishi wala za uhariri, na udhamini haununui matokeo.
Contribute to Identification (the UNI)
Institutions and experts are invited to propose amendments, join the working group or propose data sources. National participation is organised through each country’s National Nexus Consortium (NNC) and its National Working Groups (NWGs); competent national authorities are engaged through official channels.
Hali na matumizi. Nexus Standards ni viwango vinavyopendekezwa vilivyoandaliwa kupitia mchakato wazi chini ya NS-13 na kuchapishwa kwa matumizi ya hiari; si uthibitisho, uidhinishaji wala idhini ya kidhibiti, na upitishaji unabaki kuwa uamuzi wa Baraza la Viwango la Dunia na, katika kila nchi, wa Baraza lake la Viwango la Kitaifa. UNI (Unique Nexus Identifier) hutambua kitu; haikithibitishi. Majina ya vyombo vya viwango na viwango vyao ni mali ya wasimamizi wake na yanatumika tu kutambua nyaraka; hakuna maandishi ya kiwango cha nje yanayonakiliwa hapa. Nexus Standards haihusiani na, haiidhinishwi wala haithibitishwi na chombo chochote cha viwango kilichotajwa hapa.
Leseni: CC BY 4.0 kwa matini ya viwango, rejista, miundo na data; Apache-2.0 kwa msimbo wa marejeo. Viwango vya nje hunukuliwa kwa jina, namba na kiungo chini ya leseni zake vyenyewe. Data, maktaba na fonti za wahusika wengine huhifadhi leseni zake: tazama Notisi za wahusika wengine.