Skip to content
StandardsOpen Infrastructure and DevelopersInfrastructure services
Area · in the catalogue (planned)

Tomargeh û çareserker

Operates the machine-readable registries, catalogues and the UNI resolver as persistent-identifier infrastructure on the model of DataCite, ROR and ORCID: one stable URL per UNI, content negotiation to JSON-LD, DataCite and STAC, CC0 metadata, resolution receipts and federated delegation to national resolvers. Each artefact of the area carries a UNI (Unique Nexus Identifier).

Tomargeh û çareserker
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.
  • Open standards: DataCite Metadata Schema 4.5; Schema.org; Data Catalog Vocabulary (DCAT) Version 3; FAIR Signposting profile; RFC 8615 Well-Known Uniform Resource Identifiers.
  • Data and feeds: DataCite REST API (DOIs); ROR REST API v2; Software Heritage archive API.
  • Couples with: Identification (the UNI); Sovereign stack; Indexing and discovery.
Nexus Standards
4
NS-1, NS-3, NS-6
Standardên vekirî
5
named, never copied
Data and feeds
3
listed for reference
Girêdan
3
with other areas
Rewş
Proposedin the catalogue · planned · scope STD
Last reviewed
area profile
Jêgirtina vê rûpelê

Nexus Standards (2026). Registries and the resolver: area brief, Open Infrastructure and Developers programme. Proposed. https://nexustandards.com/open-infrastructure/registries-and-resolver/ · 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.

01Çarçove

Scope and boundaries

An area of the Open Infrastructure and Developers programme (infrastructure services). The area profile sets out 4 matters in scope and 2 matters addressed by other areas.

In scope 4

  • /uni/{uni} landing pages, JSON and content negotiation (NS-7)
  • /uni/resolve by alias, DOI, ORCID, ROR or SWHID with resolution receipts
  • Register projections in version control and the authoritative record store, with convergence checks
  • Federation peers and delegation

Out of scope 2

  • Public serving of restricted, secure-access or sealed records
  • Resolving DOIs or ORCID iDs on behalf of their agencies

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.

03Pêvajo

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-7, NS-3, NS-6. 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.

Process explorer · NXS · Process

Çerxa jiyanê ya tomarê

7 steps2 stages1 gate

NXS · Process

Çerxa jiyanê ya tomarê

The catalogue allocates a UNI, the writer creates and versions the record, corrections make new versions, and the ledger archives every version.

  1. 01 Nivîskar

    1. 02RecordRecord · the writer, under a scopeA record carries uni, title, scope, category, status and rights.
    2. 04CorrectionStep · any person, through a change proposalA correction names what was wrong and cites its evidence; the fix is a new version.
    3. 05VersionStep · the writerA new version leaves the previous one unchanged; both resolve.
  2. 02 Registry and ledger

    1. 01UNI allocatedStart · the catalogue or the record serviceThe reference command-line tool allocates the identifier; the serial has six digits.
    2. 03ResolvesGate · the resolverThe resolver returns a landing page or a machine-readable record; for a restricted record it returns the reason for restriction.
    3. 06Later record or withdrawalDecision · a later record or a withdrawal decisionThe later record refers back; the earlier record shows its status and refers forward.
    4. 07ArchivedOutcome · the ledgerThe ledger retains every version and every status change.

NS-1: the UNI and the artefact catalogue · NS-3: records · NS-7: resolver landing pagesAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · the service pipeline8 operations · 5 phases
GavQonaxXebitandinKîDecision ruleTomarImplements
01DaxwazRequest (start). The service covers: /uni/{uni} landing pages, JSON and content negotiation (NS-7), /uni/resolve by alias, DOI, ORCID, ROR or SWHID with resolution receipts and Register projections in version control and the authoritative record store, with convergence checks.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
02DaxwazIdentify 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
03ErêkirinValidate DataCite (gate). Open standards of this area: DataCite Metadata Schema 4.5, Schema.org, Data Catalog Vocabulary (DCAT) Version 3 and FAIR Signposting profile.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 Schema.orgNS14-R2
04ProcessingProcess (model). Processing is reproducible from the inputs, the method version and the configuration.the servicethe method and version are recorded with the result/uni/resolve by alias, DOI, ORCID, ROR or SWHID with resolution receiptsNS12-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
06WeşanPublish 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
07ÇavdêrîMonitor (exercise). Data sources the service reads: DataCite REST API (DOIs), ROR REST API v2 and Software Heritage archive API. 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-A1-02MNS11-R4
08ÇavdêrîCorrection (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 · Schema.org · NS-1: The UNI and the artefact catalogue · NS-7: Resolver landing pages, page meta tags, sitemap.

04Standards

Standardên ku têne sepandin

The area profile lists 4 Nexus Standards; the registry lists NS-1, NS-7 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-7 · Resolver landing pages, page meta tags, sitemap

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

  3. 03

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

    Status: proposed · 0 requirements stated. Read NS-3 · 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.

05Çerxa jiyanê ya tomarê

Record lifecycle from allocation to archive

Each step shows the status a record holds; identifiers are neither deleted nor reused.

Process explorer · NXS · Process

Çerxa jiyanê ya tomarê

7 steps2 stages1 gate

NXS · Process

Çerxa jiyanê ya tomarê

Çerxa jiyanê ya standardê · Rêça NS-13 · Kanalên beşdariyê · Rêça IETF · Rêça W3C · Rêça OGC · Rêça OASIS · Qonaxên ISO û IEC · Lihevbûn · Çerxa jiyanê ya tomarê · Rêkirin · Çavdêrî.

The catalogue allocates a UNI, the writer creates and versions the record, corrections make new versions, and the ledger archives every version.

  1. 01 Nivîskar

    1. 02RecordRecord · the writer, under a scopeA record carries uni, title, scope, category, status and rights.
    2. 04CorrectionStep · any person, through a change proposalA correction names what was wrong and cites its evidence; the fix is a new version.
    3. 05VersionStep · the writerA new version leaves the previous one unchanged; both resolve.
  2. 02 Registry and ledger

    1. 01UNI allocatedStart · the catalogue or the record serviceThe reference command-line tool allocates the identifier; the serial has six digits.
    2. 03ResolvesGate · the resolverThe resolver returns a landing page or a machine-readable record; for a restricted record it returns the reason for restriction.
    3. 06Later record or withdrawalDecision · a later record or a withdrawal decisionThe later record refers back; the earlier record shows its status and refers forward.
    4. 07ArchivedOutcome · the ledgerThe ledger retains every version and every status change.

NS-1: the UNI and the artefact catalogue · NS-3: records · NS-7: resolver landing pagesAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · the record lifecycle7 operations
GavQonaxXebitandinKîDecision ruleTomar
01Registry and ledgerUNI allocated (start). The reference command-line tool allocates the identifier; the serial has six digits.the catalogue or the record serviceserials are allocated by the tool and are not reused (NS1-R2, NS1-R3)an allocated serial
02NivîskarRecord (record). A record carries uni, title, scope, category, status and rights.the writer, under a scoperequired fields, rights and status are set at creationthe record with its required fields
03NivîskarVersion (step). A new version leaves the previous one unchanged; both resolve.nivîskarsemantic versioning for schemas and the registry; dated editions for documentsa new version, the previous kept
04Registry and ledgerResolves (gate). The resolver returns a landing page or a machine-readable record; for a restricted record it returns the reason for restriction.the resolverpublished, non-restricted records resolve (NS-7)HTML or JSON for the UNI
05NivîskarCorrection (step). A correction names what was wrong and cites its evidence; the fix is a new version.any person, through a change proposalcorrections are submitted as change proposals (NS-13) and produce a new version with its historya change proposal, then a new version
06Registry and ledgerLater record or withdrawal (decision). The later record refers back; the earlier record shows its status and refers forward.a later record or a withdrawal decisionthe status displayed is the status recordedsupersededBy set; status updated
07Registry and ledgerArchived (end). The ledger retains every version and every status change.defterretained permanently; history is append-onlythe record, kept

Table.A UNI is allocated by the catalogue; the writer creates and versions the record; a correction is submitted as a change proposal and produces a new version with its history; a later record takes its place, or a decision withdraws it; the ledger archives every version. The status displayed is the status recorded. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: NS-1: the UNI and the artefact catalogue · NS-3: records · NS-7: resolver landing pages.

06System model

How a shock travels through this system

A system model of this area built from the registry: 4 systems, 4 sectors, 8 controls, 3 feeds, 2 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.

Kontrol

  • NS-1UNI û kataloga berheman (rêziman v0.2: beşên qad, sektor, herêm û jîngehê)
  • NS-7 Rûpelên daketinê yên çareserker, etîketên meta yên rûpelê, nexşeya malperê
  • NS-3 UNIyên tomara xetereyê (rêzimanî, nexşeya veguhastina ji pergala kevin, desthilata veqetandinê)
  • NS-6 Girêdana rûberê (sernivîsa API, koka panelê, pasaport, OpenAPI)
  • NRS-A1 Standard wek kod: standard, pêdivî û testên ku makîne dikare bixwîne
  • NRS-C4 Modela daneyên xeterê, nasker û pevguhertin
  • NRS-H52 Hazard family: Information-integrity attacks (NHS-1 cyber.integrity)
  • NRS-A5 Lîsanskirin û maf ji destpêkê ve tê de

Çavdêrî

  • DataCite REST API (DOIs) (listed for reference)
  • ROR REST API v2 (listed for reference)
  • Software Heritage archive API (listed for reference)
  • Metadata can be accessed manually through a resolvable identifier
  • Metadata is guaranteed to remain available after data is no longer available
07Monitoring loop

How a change at a standards body reaches the registry

Each item from a data source becomes a change record, and a version difference becomes a notice and a public change record. Data sources are listed for reference; live data is displayed once licence review is complete.

Process explorer · NXS · Process

Monitoring loop

7 steps4 stages1 gate

NXS · Process

Monitoring loop

A licence-reviewed source is retrieved with digests, each item becomes a change record checked for drift, and editors record a disposition through a change proposal.

  1. 01 Data source register

    1. 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
  2. 02 Data service

    1. 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
    2. 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
    3. 07Feed retrievedStep · the governed data serviceThe data service reads the feed named in the register entry and stores each response with its digest and retrieval time.
  3. 03 Rûpel

    1. 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
  4. 04 Nexus Standards editors

    1. 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
    2. 06Next retrievalOutcome · the data service, on scheduleThe loop continues on the schedule recorded in the register entry.

Feed update register (admitted feeds only) · Licensing rules · Registries and resolverAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · the monitoring loop7 operations
GavQonaxXebitandinKîDecision ruleTomar
01Data source registerSource listed (decision). Data sources are listed for reference; live data is displayed once licence review is complete.the Secretariat, after licence reviewthe entry records the licence terms and the permitted deliveryan entry in the data source register
02Data serviceFeed retrieved (step). The data service reads the feed named in the register entry and stores each response with its digest and retrieval time.the governed data serviceretrieved on the source’s schedule; each response is stored unchangedthe response with digest and retrieval date
03Data serviceChange record (record). Each feed item becomes a change record appended to the transparency log with an inclusion proof.the data servicekind: release, errata, comment period, deprecation or supersession; version, date, URL, digesta change record with a UNI
04Data serviceDrift check (gate). Drift is a comparison of two version strings; the register entry is corrected through a change proposal.the data serviceregistered version compared with the latest release; deprecation and supersession flaggeda drift flag against the registered version
05RûpelNotice (step). The package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.the page buildthe age of the information is stateda notice with date and source
06Nexus Standards editorsDisposition (decision). The editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.Nexus Standards editorseach disposition is a change proposal under NS-13, with written reasonsa change proposal with the disposition
07Nexus Standards editorsNext retrieval (end). The loop continues on the schedule recorded in the register entry.the data service, on schedulethe source’s schedule, subject to the body’s termsthe next response

Table.A source is listed in the data source register once its licence review is complete; the governed data service retrieves the feed and stores each response with a digest; each item becomes a change record; the registered version is checked for drift; the pages show a dated notice; Nexus Standards editors record a disposition through a change proposal; the next retrieval follows the source’s schedule. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: Feed update register (admitted feeds only) · Licensing rules · Registries and resolver.

09Girêdanên pergalî

Girêdanên pergalî

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

  1. Identification (the UNI)Data and EvidenceThe resolver serves exactly what NS-1 and NS-3 allocate: published, unrestricted records only, with superseded and withdrawn identifiers pointing to their successors.
  2. Sovereign stackOpen Infrastructure and DevelopersNational resolvers operate the reference implementation for their own scopes; the global resolver delegates by scope and region and returns the peer’s receipt.
  3. Indexing and discoveryOpen Infrastructure and DevelopersLanding pages emit Schema.org JSON-LD, sitemaps and IndexNow pings so that indexes discover records through the resolver.
11Data sources

Data sources

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

Zindî
0
on completion of licence review
Listed in the data register
0
licence terms recorded
Proposed for the register
3
licence terms to be recorded
Radestkirin
2 governed service · 0 plugin · 0 browser · 0 snapshot · 1 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.

  • ROR REST API v2for reference

    Research Organization Registry · data releases roughly monthly.

    CC0 1.0 (registry data)

    governed data serviceproposed for the data register.

  • Software Heritage archive APIfor reference

    Software Heritage · continuous

    Software Heritage terms of use; archived code keeps its own licences.

    listed for referenceproposed for the data register.

12Koma xebatê

Working group charter

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

Çarçove

Maintain the resolver behaviour, federation rules and convergence between registers and the record store.

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. Resolver conformance tests (content negotiation, states, receipts)
  2. Federation delegation profile
  3. Convergence and divergence incident rules
Liaison targets · 4
  • DataCite liaison sought
  • ROR liaison sought
  • Signposting community liaison sought
  • PIDs for Science (FREYA successor) community liaison sought
13Nîşander

Nîşander

The area profile names 2 indicators, each with its framework and code.

14Amadebûn

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 cites records by resolver URL so that readers reach the current version and its history.

Read the evidence pathway

Rêya naskirinê

Global Risks Forum (GRF)

GRF recognition pages link to the resolver record of the recognised context rather than copying its content.

Read the recognition pathway

Rêya sermiyanê

Global Risks Alliance (GRA)

GRA readiness files link every input to its resolver URL and receipt, so investors can check the state independently.

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.

15Research questions

Open research questions

2 questions identified as priorities for the working group.

  1. Long-term persistence when a federated national resolver is decommissioned.
  2. Resolving identifier collisions across peers without a central authority making an unrecorded choice.
16Restricted standards

Restricted compatibility profiles

Standards whose text is not openly available are named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.

The working group may identify restricted standards relevant to this area; they are listed here by name and link.

17Temaşevan

Intended users

The area profile identifies 4 user communities.

  1. Repository and registry operators
  2. Developers integrating identifiers
  3. Librarians and indexers
  4. National hosts
18Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

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

Sektor 0

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

19Registry

Registry listing and depth pages

This area is in the catalogue (status: planned; scope STD; 1 crosswalk domain). It has five depth pages and a register crosswalk of its domains.

Crosswalk graph · registries and the resolverNexus Standards registry
Registries and the resolver: crosswalk to external standards23 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 22 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 10 external standards by domain
QadExternal standardIssuing bodyTêkilî
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-7. A relation is a register entry, never a compliance claim.

2 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 graph23 nodes and 22 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 · Registries and the resolver: 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)
LaşSeatRegister entries
DataCite Metadata Working GroupHannover, Germany1
ISO/TC 46; ISO 3166 Maintenance AgencyCenêv, Swîsre1
ISO/TC 46/SC 9; International DOI FoundationOxford, United Kingdom1
ISO/TC 46/SC 9; ISNI International AgencyLondon, Keyaniya Yekbûyî1
ORCID Inc.Bethesda, Maryland, United States1
ROR (California Digital Library, Crossref, DataCite)Hannover, Germany1
Software Heritage; ISO/IEC JTC 1Parîs, Fransa1
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.

20Çavkanî

Çavkanî

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

21Research 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 resolution; metadata registry; registry; DataCite Metadata Schema; Schema.orgcombined with: identifier; metadata; data; researchDerived 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.

22Perwerde û rahênan

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.

23Li seranserê torê

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.

Governance, policy and convening

Global Risks Forum (GRF)

Tracks that convene public authorities, researchers and institutions on the governance of shared risks.

AI and Digital GovernanceExamines digital dependence and the governance of public infrastructure.Join this track globalriskforum.comAll tracks of The Global Risks Forum

Capital, finance and markets

Global Risks Alliance (GRA)

Industry programmes in which financial institutions build a shared understanding of systemic risk.

Fintech NexusExamines open finance and application interfaces in financial services.Join this programme globalriskalliance.comAll programmes of The Global Risks Alliance
24Têgehên sereke

Têgehên sereke

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
pêşniyarkirî
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.
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.
26Lêkolîn

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 resolution; metadata registry; registry; combined with: identifier; metadata; data; research. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

27Pirs

Pirs û bersiv.

What is the status of the Registries and the resolver 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.
rêzeya Pergalên StratejîkBeşdar bibe

Ji vê rûpelê delîl bidin.

Reports weşana sê mehane ya Konsorsiyûmê ye. Tiştê ku tu li ser vê mijarê dizanî dikare di çapa pêş de bibe delîl, dosya an rastkirin, bi navê te û di bin CC BY 4.0 de weşandî li cihê ku karê te bi xwe be.

Nexus Standards
Standards

Contribute to Registries and the resolver

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.

Rewş û bikaranîn. Nexus Standards standardên pêşniyarkirî ne ku bi pêvajoyeke vekirî di bin NS-13 de hatine pêşxistin û ji bo bikaranîna dilxwazî hatine weşandin; ew ne belgename, ne akreditasyon û ne pejirandina rêkxistinê ne, û pejirandin biryara Encûmena Standardên Cîhanî û, li her welatî, ya Encûmena Standardên Neteweyî ya wê dimîne. UNI (Unique Nexus Identifier) berhemekê nas dike; wê belgename nake. Navên desteyên standardan û standardên wan aîdî parêzvanên wan in û tenê ji bo naskirina belgeyan têne bikaranîn; tu nivîsa standardeke derve li vir nayê dubarekirin. Nexus Standards bi tu desteya standardan a li vir hatiye binavkirin ve ne girêdayî ye, ji aliyê wê ve nayê piştgirîkirin û belgename nekiriye.

Lîsans: CC BY 4.0 ji bo nivîsa standardan, tomargeh, şema û daneyan; Apache-2.0 ji bo koda referansê. Standardên derve bi nav, hejmar û girêdanê di bin lîsansên xwe de têne jêgirtin. Dane, pirtûkxane û fontên aliyê sêyem lîsansên xwe diparêzin: binêre Agahdariyên aliyê sêyem.