Registries and the resolver
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).
- 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
- Open standards
- 5
- named, never copied
- Data and feeds
- 3
- listed for reference
- Couplings
- 3
- with other areas
- स्थिती
- Proposedin the catalogue · planned · scope STD
- Last reviewed
- area profile
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.
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 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.
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-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
नोंद जीवनचक्र
7 steps·2 stages·1 gate
NXS · Process
नोंद जीवनचक्र
The catalogue allocates a UNI, the writer creates and versions the record, corrections make new versions, and the ledger archives every version.
01 Writer
- 02RecordRecord · the writer, under a scopeA record carries uni, title, scope, category, status and rights.
- 04CorrectionStep · any person, through a change proposalA correction names what was wrong and cites its evidence; the fix is a new version.
- 05VersionStep · the writerA new version leaves the previous one unchanged; both resolve.
02 Registry and ledger
- 01UNI allocatedStart · the catalogue or the record serviceThe reference command-line tool allocates the identifier; the serial has six digits.
- 03ResolvesGate · the resolverThe resolver returns a landing page or a machine-readable record; for a restricted record it returns the reason for restriction.
- 06Later record or withdrawalDecision · a later record or a withdrawal decisionThe later record refers back; the earlier record shows its status and refers forward.
- 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
| पायरी | Phase | संचालन | Who | Decision rule | नोंद | Implements |
|---|---|---|---|---|---|---|
| 01 | विनंती | Request (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 machine | the context is explicit in the request or on the record, never inferred | a request naming its context and inputs | NS16-R20 |
| 02 | विनंती | 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 | प्रमाणीकरण | Validate 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 validator | validated against the open standard’s own schema or validator where one exists | a validation run against DataCite Metadata Schema 4.5 and Schema.org | 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 | /uni/resolve by alias, DOI, ORCID, ROR or SWHID with resolution receipts | 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 | देखरेख | 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 service | monitoring records are observations with record UNIs | observations of availability, drift and RDA FAIR Data Maturity Model RDA-A1-02M | NS11-R4 |
| 08 | देखरेख | 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 · Schema.org · NS-1: The UNI and the artefact catalogue · NS-7: Resolver landing pages, page meta tags, sitemap.
लागू होणारी मानके
The area profile lists 4 Nexus Standards; the registry lists NS-1, NS-7 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-7 · Resolver landing pages, page meta tags, sitemap
Status: in progress · 0 requirements stated. Read NS-7 · Requirements for this area.
- 03
NS-3 · Risk record UNIs (grammar, legacy crosswalk, allocation authority)
Status: proposed · 0 requirements stated. Read NS-3 · 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.
Record lifecycle from allocation to archive
Each step shows the status a record holds; identifiers are neither deleted nor reused.
Process explorer · NXS · Process
नोंद जीवनचक्र
7 steps·2 stages·1 gate
NXS · Process
नोंद जीवनचक्र
मानक जीवनचक्र · NS-13 मार्ग · योगदान माध्यमे · IETF मार्ग · W3C मार्ग · OGC मार्ग · OASIS मार्ग · ISO आणि IEC टप्पे · अनुरूपता · नोंद जीवनचक्र · मार्गनिर्देशन · देखरेख.
The catalogue allocates a UNI, the writer creates and versions the record, corrections make new versions, and the ledger archives every version.
01 Writer
- 02RecordRecord · the writer, under a scopeA record carries uni, title, scope, category, status and rights.
- 04CorrectionStep · any person, through a change proposalA correction names what was wrong and cites its evidence; the fix is a new version.
- 05VersionStep · the writerA new version leaves the previous one unchanged; both resolve.
02 Registry and ledger
- 01UNI allocatedStart · the catalogue or the record serviceThe reference command-line tool allocates the identifier; the serial has six digits.
- 03ResolvesGate · the resolverThe resolver returns a landing page or a machine-readable record; for a restricted record it returns the reason for restriction.
- 06Later record or withdrawalDecision · a later record or a withdrawal decisionThe later record refers back; the earlier record shows its status and refers forward.
- 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
| पायरी | Phase | संचालन | Who | Decision rule | नोंद |
|---|---|---|---|---|---|
| 01 | Registry and ledger | UNI allocated (start). The reference command-line tool allocates the identifier; the serial has six digits. | the catalogue or the record service | serials are allocated by the tool and are not reused (NS1-R2, NS1-R3) | an allocated serial |
| 02 | Writer | Record (record). A record carries uni, title, scope, category, status and rights. | the writer, under a scope | required fields, rights and status are set at creation | the record with its required fields |
| 03 | Writer | Version (step). A new version leaves the previous one unchanged; both resolve. | the writer | semantic versioning for schemas and the registry; dated editions for documents | a new version, the previous kept |
| 04 | Registry and ledger | Resolves (gate). The resolver returns a landing page or a machine-readable record; for a restricted record it returns the reason for restriction. | the resolver | published, non-restricted records resolve (NS-7) | HTML or JSON for the UNI |
| 05 | Writer | Correction (step). A correction names what was wrong and cites its evidence; the fix is a new version. | any person, through a change proposal | corrections are submitted as change proposals (NS-13) and produce a new version with its history | a change proposal, then a new version |
| 06 | Registry and ledger | Later record or withdrawal (decision). The later record refers back; the earlier record shows its status and refers forward. | a later record or a withdrawal decision | the status displayed is the status recorded | supersededBy set; status updated |
| 07 | Registry and ledger | Archived (end). The ledger retains every version and every status change. | the ledger | retained permanently; history is append-only | the 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.
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.
प्रणाली आणि जोडण्या
- Registries and the resolver
- Identification (the UNI) Coupling
- Sovereign stack Coupling
- Indexing and discovery Coupling
नियंत्रणे
NS-1UNI आणि वस्तू सूची (व्याकरण v0.2: विषय, क्षेत्र, प्रदेश आणि पर्यावरण विभाग)NS-7निराकरणक प्रारंभ पाने, पान मेटा टॅग, साइटमॅपNS-3जोखीम नोंद UNI (व्याकरण, जुना तुलनात्मक संदर्भ, वाटप प्राधिकरण)NS-6पृष्ठभाग जोडणी (API शीर्षलेख, फलक उगम, पासपोर्ट, OpenAPI)NRS-A1कोड स्वरूपातील मानके: यंत्रवाचनीय मानके, आवश्यकता आणि चाचण्याNRS-C4जोखीम डेटा प्रारूप, ओळखचिन्हे आणि देवाणघेवाणNRS-H52Hazard family: Information-integrity attacks (NHS-1 cyber.integrity)NRS-A5अंगभूत परवाना आणि हक्क
निरीक्षण
- 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
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 steps·4 stages·1 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.
01 Data source register
- 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
02 Data service
- 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
- 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
- 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.
03 Pages
- 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
04 Nexus Standards editors
- 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
- 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
| पायरी | Phase | संचालन | Who | Decision rule | नोंद |
|---|---|---|---|---|---|
| 01 | Data source register | Source listed (decision). Data sources are listed for reference; live data is displayed once licence review is complete. | the Secretariat, after licence review | the entry records the licence terms and the permitted delivery | an entry in the data source register |
| 02 | Data service | Feed 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 service | retrieved on the source’s schedule; each response is stored unchanged | the response with digest and retrieval date |
| 03 | Data service | Change record (record). Each feed item becomes a change record appended to the transparency log with an inclusion proof. | the data service | kind: release, errata, comment period, deprecation or supersession; version, date, URL, digest | a change record with a UNI |
| 04 | Data service | Drift check (gate). Drift is a comparison of two version strings; the register entry is corrected through a change proposal. | the data service | registered version compared with the latest release; deprecation and supersession flagged | a drift flag against the registered version |
| 05 | पाने | Notice (step). The package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such. | the page build | the age of the information is stated | a notice with date and source |
| 06 | Nexus Standards editors | Disposition (decision). The editors determine what the change means for the register entry and the crosswalk; the page shows the disposition. | Nexus Standards editors | each disposition is a change proposal under NS-13, with written reasons | a change proposal with the disposition |
| 07 | Nexus Standards editors | Next retrieval (end). The loop continues on the schedule recorded in the register entry. | the data service, on schedule | the source’s schedule, subject to the body’s terms | the 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.
Routing, 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.
In progressMonitoring console
Version and source status for each standard, as published by the issuing bodies.
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.
प्रणालीगत जोडण्या
3 couplings link this area to other areas and programmes, each with the mechanism of the link.
- 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.
- 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.
- Indexing and discoveryOpen Infrastructure and DevelopersLanding pages emit Schema.org JSON-LD, sitemaps and IndexNow pings so that indexes discover records through the resolver.
Open standards referenced
5 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
Data sources
3 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.
- थेट
- 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
- Delivery
- 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.
Working group charter
A proposed charter for this area, open to institutions and experts.
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).
- Resolver conformance tests (content negotiation, states, receipts)
- Federation delegation profile
- Convergence and divergence incident rules
- DataCite liaison sought
- ROR liaison sought
- Signposting community liaison sought
- PIDs for Science (FREYA successor) community liaison sought
निर्देशक
The area profile names 2 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
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 cites records by resolver URL so that readers reach the current version and its history.
Global Risks Forum (GRF)
GRF recognition pages link to the resolver record of the recognised context rather than copying its content.
Global Risks Alliance (GRA)
GRA readiness files link every input to its resolver URL and receipt, so investors can check the state independently.
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
2 questions identified as priorities for the working group.
- Long-term persistence when a federated national resolver is decommissioned.
- Resolving identifier collisions across peers without a central authority making an unrecorded choice.
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.
Intended users
The area profile identifies 4 user communities.
- Repository and registry operators
- Developers integrating identifiers
- Librarians and indexers
- National hosts
Hazards, threats and sectors concerned
Hazards and threats 0
This area draws on the hazards of the areas it is coupled with.
क्षेत्रे 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: planned; scope STD; 1 crosswalk domain). It has five depth pages and a register crosswalk of its domains.
लागू होणारी मानके
The rules of each listed standard, read through the specification reader.
Depth · Crosswalkसंदर्भ-जुळणी
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 · Conformanceअनुरूपता
Clauses, evidence and attestations for conformance assessment.
Depth · Readinessसज्जता
The area alongside the three pathways, as a matrix.
The crosswalk as a table: 10 external standards by 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-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.
Issuing bodies and their seats (9)
| संस्था | 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.
स्रोत
3 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-reviewedORCID: a system to uniquely identify researchersLearned Publishing · 2012
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.
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.
अभ्यासक्रम
विद्याशाखा
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.
संशोधन आणि पुरावा
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
RegistryMaintains registry interoperability and record provenance.Apply to this programme Data and ComputeWorks on access to research infrastructure.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.
AI and Digital GovernanceExamines digital dependence and the governance of public infrastructure.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.
Fintech NexusExamines open finance and application interfaces in financial services.Join this programme globalriskalliance.comAll programmes of The Global Risks Allianceशिक्षण आणि प्रशिक्षण
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 pageप्रमुख संज्ञा
- UNI
- Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
- प्रस्तावित
- 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.
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
- 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 - ORCID: a system to uniquely identify researchers
Learned Publishing · 2012 · Peer-reviewed
Related standards and frameworks
- DataCite Metadata Schema 4.5
DataCite - Schema.org
Schema.org - Data Catalog Vocabulary (DCAT) Version 3
W3C - FAIR Signposting profile
Signposting community - RFC 8615 Well-Known Uniform Resource Identifiers
IETF
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.
प्रश्न आणि उत्तरे.
What is the status of the Registries and the resolver area?
How are data sources presented?
How can this brief be amended?
या पानावरून पुरावा योगदान द्या.
Reports हे कन्सोर्टियमचे त्रैमासिक प्रकाशन आहे. या विषयाबद्दल तुम्हाला जे माहीत आहे ते पुढील आवृत्तीत पुरावा, उदाहरण किंवा दुरुस्ती बनू शकते, तुम्हाला श्रेय देऊन आणि ते तुमचे स्वतःचे काम असल्यास CC BY 4.0 अंतर्गत प्रकाशित.
- ईमेलप्रवेशद्वार GW-STDया पानावरून पाठवापुरावा, दुरुस्ती, उदाहरण, पद्धत, आढावा, भाषांतर किंवा प्रोफाइलसाठी माहिती. ते या पानाच्या टॅगसह पोहोचते, त्यामुळे त्याचा जबाबदार संपादक ते प्राप्त करतो.
- 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.
वैयक्तिक डेटा, संवेदनशील पायाभूत सुविधांचा तपशील किंवा सामायिक करण्याचा तुम्हाला अधिकार नसलेले काहीही कधीही पाठवू नका. योगदानाचे वापरापूर्वी पुनरावलोकन केले जाते; ते पाठवल्याने कोणतेही लेखकत्व किंवा संपादकीय अधिकार मिळत नाहीत, आणि प्रायोजकत्वाने कधीही निष्कर्ष विकत घेता येत नाही.
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.
स्थिती आणि वापर. Nexus Standards ही NS-13 अंतर्गत खुल्या प्रक्रियेद्वारे विकसित केलेली आणि ऐच्छिक वापरासाठी प्रकाशित प्रस्तावित मानके आहेत; ती प्रमाणन, अधिस्वीकृती किंवा नियामक मंजुरी ठरत नाहीत, आणि स्वीकार हा जागतिक मानके परिषदेचा आणि प्रत्येक देशात त्याच्या राष्ट्रीय मानके परिषदेचा निर्णय राहतो. UNI (Unique Nexus Identifier) वस्तू ओळखतो; तो तिचे प्रमाणन करत नाही. मानके संस्थांची आणि त्यांच्या मानकांची नावे त्यांच्या विश्वस्तांची आहेत आणि केवळ दस्तऐवज ओळखण्यासाठी वापरली जातात; बाह्य मानकाचा कोणताही मजकूर येथे पुनरुत्पादित केलेला नाही. Nexus Standards येथे नमूद कोणत्याही मानके संस्थेशी संलग्न नाही, तिच्याकडून समर्थित किंवा प्रमाणित नाही.
परवाने: मानकांचा मजकूर, नोंदवह्या, स्कीमा आणि माहितीसाठी CC BY 4.0; संदर्भ कोडसाठी Apache-2.0. बाह्य मानके त्यांच्या स्वतःच्या परवान्याखाली नाव, क्रमांक आणि दुव्याद्वारे उद्धृत केली जातात. तृतीय-पक्ष माहिती, ग्रंथालये आणि फॉन्ट त्यांचे स्वतःचे परवाने राखतात: तृतीय-पक्ष सूचना पाहा.