Skip to content
StandardsData and EvidenceCross-cutting capabilities
Area · in the catalogue (in progress)

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).

Identification (the UNI)
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).Source: the Nexus Standards registry: the area record.
  • 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
Status
Proposedin the catalogue · in progress · scope STD
Last reviewed
area profile
Cite this page

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.

Download the profile

Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.

01Omvang

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.

02Standards architecture

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.

03Proses

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.

Prosesverkenner · Standards · kodifiseer en korrigeer

Lewensiklus van 'n standaard

17 stappe6 fases

Standards · kodifiseer en korrigeer

Lewensiklus van 'n standaard

Lewensiklus van 'n standaard · NS-13-spoor · Bydraekanale · IETF-spoor · W3C-spoor · OGC-spoor · OASIS-spoor · ISO- en IEC-fases · Konformiteit · Rekordlewensiklus · Roetering · Monitering.

Siklusbevindings word veranderingsvoorstelle, die Wêreldwye Standaarderaad aanvaar ná 'n openbare laaste oproep, en elke land besluit oor sy eie aanvaarding.

  1. 01 Lei sendings

    1. 01Lei sendings na standaarde en profieleStap · Nexus StandardsNexus Standards lei elke kandidaatsending na die standaarde en profiele wat van toepassing is.
  2. 02 Profiele en ooreenstemming

    1. 02Stel sendingprofiele saamStap · Nexus StandardsNexus Standards stel sendingprofiele saam en teken enige nasionale aanvaarding aan waarvan die sendings afhang.
    2. 03Valideer bou-uitsette teen die profieleStap · Nexus StandardsNexus Standards valideer bou-uitsette teen die saamgestelde profiele en teken die bewyse aan.
    3. 04Moniteer konformiteit en teken verseëlde bewyse aanStap · Nexus StandardsGedurende die Aksieweek monitor Nexus Standards konformiteit en teken afwykings aan.
  3. 03 Voorstelle en beoordeling

    1. 05Afwykings en regstellings word veranderingsvoorstelleStap · Nexus StandardsAfwykings word veranderingsvoorstelle, en die regstelling word as 'n verandering aan die bewyse aangeteken.
    2. 06Siklusbevindings word veranderingsvoorstelleStap · Nexus StandardsBevindings uit 'n siklus word veranderingsvoorstelle: metode- en korreksiebevindings uit Verslae (F06) en dokketitems uit Nexus…
    3. 07Stel op en hersien in die openbaarStap · Komitees en werkgroepeTegniese komitees en werkgroepe stel die standaarde op en hersien dit in die oop proses van NS-13.
    4. 08Beoordeel met die oog op 'n raadsbesluitStap · Nexus StandardsNexus Standards beweeg veranderingsvoorstelle deur beoordeling met die oog op 'n raadsbesluit.
  4. 04 Raadsbesluit

    1. 09Openbare laaste oproepStap · Global Standards CouncilDie Global Standards Council aanvaar by 'n tweederdemeerderheid ná 'n laaste oproep van negentig dae.
    2. 10Wêreldwye aanvaarding van 'n standaardBesluit · Global Standards CouncilDie Wêreldwye Standaarderaad besluit oor die aanvaarding van elke standaard ná 'n openbare laaste oproep.
  5. 05 Publiseer en identifiseer

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12'n UNI identifiseer en sertifiseer nooit nieRekord · Nexus StandardsElke objek van die programjaar dra een identifiseerder, 'n UNI onder NS-1, sodat dit aangehaal, geweergaweer en opgelos kan word.
    3. 13Publiseer die jaar se aanvaarde veranderingeStap · Nexus StandardsBy hernuwing publiseer Nexus Standards die jaar se aanvaarde veranderinge en die nasionale aanvaardingstatus.
  6. 06 Nasionale aanvaarding en toepassing

    1. 14Nasionale aanvaarding deur die Nasionale StandaarderaadBesluit · Nasionale StandaarderaadElke land se Nasionale Standaarderaad besluit oor nasionale aanvaarding: aanvaar soos dit is, aanvaar met 'n profiel (NS-16), pas aan, of verwys slegs.
    2. 15Aangenome standaarde bereik kursusse en uitgawesStap · Nexus StandardsElke aangenome standaard of profiel word 'n kursusmodule by Risk Academy (F09), en standaarde word in Reports-uitgawes (R1) toegepas.
    3. 16Aanvaarding is finaal vir elke jurisdiksieStandaard · Nasionale StandaarderaadAanvaarding is finaal vir elke jurisdiksie, en die GSC het geen veto oor 'n nasionale besluit nie. Geen globale liggaam hou 'n veto nie.
    4. 17Nasionale aanvaardingsrekordsRekord · Nexus StandardsSaamgestelde missieprofiele en nasionale aanvaardingsrekords gaan na die Foundry by gereedheidsvoorbereiding (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
Process · the service pipeline8 operations · 5 phases
StepPhaseOperationWhoDecision ruleRecordImplements
01RequestRequest (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 machinethe context is explicit in the request or on the record, never inferreda request naming its context and inputsNS16-R20
02RequestIdentify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal.the serviceinputs are cited by UNI and versioninputs resolved to their UNIs and versionsNS1-R5, NS2-R2, NS0-P12
03ValidationValidate 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 validatorvalidated against the open standard’s own schema or validator where one existsa validation run against DataCite Metadata Schema 4.5 and Research Organization Registry (ROR)NS14-R2
04ProcessingProcess (model). Processing is reproducible from the inputs, the method version and the configuration.the servicethe method and version are recorded with the resultCatalogue allocation for artefacts (command-line minting) and record-service allocation for data records (append-only, scoped to each tenant)NS12-R1
05ProcessingWrite records (record). Results are written append-only; a correction adds a version.the serviceevery result carries what it was derived fromresult records with provenance and a record UNINS0-P7, NS1-R3
06PublicationPublish and resolve (step). Results are discoverable and citable by UNI.the servicewrites return the allocated UNI; citations resolveresults reachable through the resolver, with the X-Nexus-UNI headerNS1-R5, NS2-R5
07MoniteringMonitor (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 servicemonitoring records are observations with record UNIsobservations of availability, drift and RDA FAIR Data Maturity Model RDA-F1-01MNS11-R4
08MoniteringCorrection (end). Products that used a corrected record are listed and recomputed.the data stewarda correction never overwrites; dependent results are replayeda correction record that reaches every dependent resultNS1-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.

04Standaarde

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.

  1. 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.

  2. 02

    NS-3 · Risk record UNIs (grammar, legacy crosswalk, allocation authority)

    Status: proposed · 0 requirements stated. Read NS-3 · Requirements for this area.

  3. 03

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status: proposed · 5 requirements stated. Read NS-9 · Requirements for this area.

  4. 04

    NS-6 · Surface wiring (API header, panel provenance, passports, OpenAPI)

    Status: in progress · 0 requirements stated. Read NS-6 · Requirements for this area.

  5. 05

    NS-7 · Resolver landing pages, page meta tags, sitemap

    Status: in progress · 0 requirements stated. Read NS-7 · Requirements for this area.

05System model

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.

Controls

  • NS-1Die UNI en die artefakkatalogus (grammatika v0.2: domein-, sektor-, streek- en omgewingsegmente)
  • NS-3 Risikorekord-UNI's (grammatika, oorerflike kruisverwysing, toewysingsgesag)
  • NS-9 Kontekstuele UNI's (ontplooiings, instansies, programinstansies)
  • NS-6 Oppervlakbedrading (API-kop, paneelherkoms, paspoorte, OpenAPI)
  • NS-7 Landingsbladsye van die oplosser, bladsy-metamerkers, werfkaart
  • NRS-A5 Ingeboude lisensiëring en regte
  • NRS-H114 Hazard family: Macroeconomic and fiscal shocks (NHS-1 soc.macro-fiscal)
  • NRS-A1 Standaarde as kode: masjienleesbare standaarde, vereistes en toetse
  • NRS-C4 Risikodatamodel, identifiseerders en uitruiling
  • NRS-H106 Gevarefamilie: Ruimtetegnologie en wentelbaaninfrastruktuur (NHS-1 tech.space-systems)
  • NRS-U16Universe-platformprofiel: 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)
08Sistemiese koppelings

Sistemiese koppelings

4 couplings link this area to other areas and programmes, each with the mechanism of the link.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
10Data sources

Data sources

4 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

Data sources are listed for reference; live data is displayed once licence review is complete.

Lewendig
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

11Restricted standards

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.

12Werkgroep

Working group charter

A proposed charter for this area, open to institutions and experts.

Omvang

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).

Deliverables · 3
  1. NS-1 edition with conformance classes and executable tests
  2. Crosswalk tables UNI to DataCite, ROR, ORCID, SWHID and DID
  3. Federated allocation profile for national resolvers
Liaison targets · 5
  • DataCite liaison sought
  • ROR liaison sought
  • Software Heritage liaison sought
  • W3C Credentials Community Group liaison sought
  • RDA PID Interest Group liaison sought
13Gereedheid

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.

Evidence pathway

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.

Read the evidence pathway

Erkenningsroete

Die 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.

Read the recognition pathway

Kapitaalroete

Die 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.

Read the capital pathway

Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.

14Research questions

Open research questions

3 questions identified as priorities for the working group.

  1. Federated serial allocation across national resolvers without a global lock and without collisions that must later be reported and resolved.
  2. Binding a contextual UNI to a DID method (did:web versus did:key) without making key rotation change the identifier.
  3. Retrofitting UNIs onto legacy data records whose original identifiers were reused or ambiguous.
15Teikengroepe

Intended users

The area profile identifies 4 user communities.

  1. Data stewards and repository managers
  2. Software and platform engineers
  3. Research librarians and publishers
  4. National statistical and mapping agencies
16Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

This area draws on the hazards of the areas it is coupled with.

Sektore 0

This area serves all sectors through the areas it is coupled with.

17Registry

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.

Crosswalk graph · identification (the uni)Nexus Standards registry
Identification (the UNI): crosswalk to external standards24 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 23 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 10 external standards by domain
DomainExternal standardIssuing bodyRelation
Identifiers and cataloguingDataCite Metadata Schema 4.5DataCite Metadata Working Groupadopt
Identifiers and cataloguingDigital Object Identifier system – ISO 26324ISO/TC 46/SC 9; International DOI Foundationcrosswalk
Identifiers and cataloguingInternational Standard Name Identifier (ISNI) – ISO 27729ISO/TC 46/SC 9; ISNI International Agencycite
Identifiers and cataloguingISO 3166-1 Codes for the representation of names of…ISO/TC 46; ISO 3166 Maintenance Agencyadopt
Identifiers and cataloguingOpen Badges 3.01EdTech Consortiumadopt
Identifiers and cataloguingORCID iD (subset of ISNI, ISO 27729)ORCID Inc.adopt
Identifiers and cataloguingResearch Organization Registry (ROR)ROR (California Digital Library, Crossref, DataCite)adopt
Identifiers and cataloguingSoftWare Hash IDentifier (SWHID) Specification V1.2…Software Heritage; ISO/IEC JTC 1adopt
Identifiers and cataloguingUN M49 Standard country or area codes for statistical useUnited Nations Statistics Divisionadopt
Identifiers and cataloguingW3C Decentralized Identifiers (DIDs) v1.0W3C DID Working Groupprofile

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.

Standards globe · Identification (the UNI): issuing bodiesNexus Standards registry
Seats of the bodies that issue the external standards in the registerA world map with coastlines and equal-area cells at the public seats of 9 issuing bodies and one dot per seat. 10 register entries.
Issuing bodies’ seats (9)Equal-area cells (8); darker, more register entriesProgrammes, repositories and standards: not mapped
Issuing bodies and their seats (9)
BodySeatRegister entries
DataCite Metadata Working GroupHannover, Germany1
ISO/TC 46; ISO 3166 Maintenance AgencyGeneva, Switzerland1
ISO/TC 46/SC 9; International DOI FoundationOxford, United Kingdom1
ISO/TC 46/SC 9; ISNI International AgencyLondon, United Kingdom1
ORCID Inc.Bethesda, Maryland, United States1
ROR (California Digital Library, Crossref, DataCite)Hannover, Germany1
Software Heritage; ISO/IEC JTC 1Paris, France1
United Nations Statistics DivisionNew York, New York, United States1
W3C DID Working GroupCambridge, Massachusetts, United States1

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.

18Bronne

Bronne

4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.

19Research hub

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.

20Onderwys en opleiding

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.

21Oor die netwerk

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.

Capital, finance and markets

Die 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 Alliance
22Kernterme

Kernterme

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
voorgestel
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.
24Navorsing

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

Related standards and frameworks

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.

25Vrae

Questions and answers.

What is the status of the Identification (the UNI) area?
The area profile is a proposal to the Nexus Standards registry, and the area is in the catalogue. Standards are adopted by the Global Standards Council after last call; in each country, adoption is a decision of its National Standards Council (NSC).
How are data sources presented?
Each data source is listed with its provider, licence, update frequency and delivery path, and links to the provider’s own publication.
How can this brief be amended?
Through a public change record under NS-13: a proposed amendment to the area profile or the registry, decided by the editors with written reasons.
VerslaeDra by

Dra bewyse vanaf hierdie bladsy by.

Reports is die Konsortium se kwartaallikse publikasie. Wat jy oor hierdie onderwerp weet, kan bewyse, 'n saak of 'n korreksie in die volgende uitgawe word, aan jou toegeskryf en onder CC BY 4.0 gepubliseer waar dit jou eie werk is.

Nexus Standards
Standaarde

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.

Status en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.

Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.