The UNI and the artefact catalogue
Explains the UNI (Unique Nexus Identifier, NS-1): the grammar NXS-SCOPE-CAT[-REGION]-SERIAL[@VERSION], allocation only through the catalogue command-line tool, never deleted or reused, embedded in the artefact itself and resolvable at /uni/<uni>; and how record UNIs (NS-3) and contextual UNIs (NS-9) extend it. A UNI identifies and resolves an artefact; it does not certify it or authorise its use. Each artefact of the area carries a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-1, NS-3, NS-7, NS-9.
- Open standards: DataCite Metadata Schema 4.5; RFC 8141 Uniform Resource Names (URNs); SoftWare Hash IDentifier (SWHID) specification; Schema.org vocabulary; Data Catalog Vocabulary (DCAT) Version 3; DOI Handbook (the DOI system, standardised as ISO 26324, named only).
- Data and feeds: DataCite REST API (DOI metadata for crosswalk and harvest tests); ROR data dump (organisation identifiers for publisher and creator fields); ORCID public data file.
- Couples with: Conformance programme; Licensing and intellectual property; How a standard is made; Data and evidence.
پوختە
- 01ScopeScope and boundaries
- 02Standards architectureFoundation, referenced and implementing layers
- 03پەیوەستبوونە سیستەمییەکانپەیوەستبوونە سیستەمییەکان
- 04System modelHow a shock travels through this system
- 05ستانداردستانداردە جێبەجێبووەکان
- 06Working groupWorking group charter
- 07Open standardsOpen standards referenced
- Nexus Standards
- 4
- NS-1, NS-3, NS-7
- ستانداردە کراوەکان
- 6
- named, never copied
- Data and feeds
- 3
- listed for reference
- پەیوەستبوونەکان
- 4
- with other areas
- UNI
- requested · allocation in progress
- دۆخ
- Proposednot yet in the catalogue
- Last reviewed
- area profile
Nexus Standards (2026). The UNI and the artefact catalogue: area brief, Foundations and Governance programme. Proposed. https://nexustandards.com/foundations/the-uni/. 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 Foundations and Governance programme (foundations). The area profile sets out 5 matters in scope and 3 matters addressed by other areas.
In scope 5
- UNI grammar, scopes, categories and the region segment (ISO 3166-1 alpha-3 or UN M49)
- Allocation, versioning, supersession and withdrawal rules (NS1-R1 to NS1-R7)
- Resolver behaviour, landing pages, JSON by content negotiation and the X-Nexus-UNI header (NS-7)
- Crosswalks to DOI, ORCID, ROR, SWHID, Schema.org, DataCite and CodeMeta
- Embedding rules for files, documents, datasets, figures and web pages
Out of scope 3
- Minting DOIs or acting as a DOI registration agency
- Trademark or brand use of codes; a scope code is not a product name
- Any statement that a resolved record is true, approved or fit for a purpose
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 process in operation
A producer describes an artefact; its context codes are checked against the registries; the catalogue mints the UNI (Unique Nexus Identifier) and keeps the record; the UNI is embedded in the artefact and resolves to its landing page; versions share the UNI, and a withdrawn or replaced artefact keeps its record. 8 operations in 6 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 (10).
گەڕۆکی پرۆسە · Standards · کۆدکردن و ڕاستکردنەوە
خولی ژیانی ستاندارد
17 هەنگاو·6 قۆناغ
Standards · کۆدکردن و ڕاستکردنەوە
خولی ژیانی ستاندارد
خولی ژیانی ستاندارد · ڕێڕەوی NS-13 · کەناڵەکانی بەشداری · ڕێڕەوی IETF · ڕێڕەوی W3C · ڕێڕەوی OGC · ڕێڕەوی OASIS · قۆناغەکانی ISO و IEC · گونجاندن · خولی ژیانی تۆمار · ئاڕاستەکردن · چاودێری.
دۆزینەوەکانی خول دەبنە پێشنیاری گۆڕانکاری، ئەنجومەنی جیهانیی ستانداردەکان دوای دوایین بانگەوازی گشتی پەسەندیان دەکات، و هەر وڵاتێک بڕیار لەسەر پەسەندکردنی خۆی دەدات.
01 ئاڕاستەکردنی ئەرکەکان
- 01Route missions to standards and profilesStep · Nexus StandardsNexus Standards routes each candidate mission to the standards and profiles that apply.
02 پرۆفایلەکان و گونجان
- 02پرۆفایلی ئەرکەکان پێکبهێنەهەنگاو · Nexus StandardsNexus Standards پرۆفایلی ئەرکەکان پێکدەهێنێت و هەر پەسەندکردنێکی نیشتمانی تۆمار دەکات کە ئەرکەکان پشتی پێدەبەستن.
- 03دەرچووەکانی دروستکردن بەراورد بە پڕۆفایلەکان پشتڕاست بکەرەوەهەنگاو · Nexus StandardsNexus Standards دەرچووەکانی دروستکردن بەراورد بە پڕۆفایلە پێکهێنراوەکان پشتڕاست دەکاتەوە و بەڵگەکان تۆمار دەکات.
- 04چاودێریی گونجان بکە و بەڵگەی مۆرکراو تۆمار بکەهەنگاو · Nexus Standardsلە ماوەی Action Week دا، Nexus Standards چاودێریی گونجان دەکات و لادانەکان تۆمار دەکات.
03 پێشنیار و پێداچوونەوە
- 05لادان و ڕاستکردنەوەکان دەبنە پێشنیاری گۆڕانکاریهەنگاو · Nexus Standardsلادانەکان دەبنە پێشنیاری گۆڕانکاری، و ڕاستکردنەوەکە وەک گۆڕانێک لە بەڵگەکەدا تۆمار دەکرێت.
- 06دۆزینەوەکانی خول دەبنە پێشنیاری گۆڕانکاریهەنگاو · Nexus Standardsدۆزینەوەکانی خولێک دەبنە پێشنیاری گۆڕانکاری: دۆزینەوەکانی میتۆد و ڕاستکردنەوە لە ڕاپۆرتەکان (F06) و بابەتەکانی خشتەی کار لە Nexus…
- 07بە ئاشکرا ڕەشنووس بکە و پێیدا بچۆرەوەهەنگاو · لیژنەکان و گرووپەکانی کارلیژنە تەکنیکییەکان و گرووپەکانی کار ستانداردەکان لە پرۆسەی کراوەی NS-13 دا ڕەشنووس دەکەن و پێیاندا دەچنەوە.
- 08پێداچوونەوە بەرەو بڕیاری ئەنجومەنهەنگاو · Nexus StandardsNexus Standards پێشنیارەکانی گۆڕانکاری لە ڕێگەی پێداچوونەوەوە بەرەو بڕیاری ئەنجومەن دەبات.
04 بڕیاری ئەنجومەن
- 09بانگەوازی کۆتایی گشتیهەنگاو · ئەنجومەنی جیهانیی ستانداردەکانئەنجومەنی جیهانیی ستانداردەکان دوای بانگەوازێکی کۆتایی نەوەد ڕۆژە بە زۆرینەی دوو لەسەر سێ پەسەند دەکات.
- 10پەسەندکردنی جیهانیی ستانداردێکبڕیار · ئەنجومەنی جیهانیی ستانداردەکانئەنجومەنی جیهانیی ستانداردەکان دوای دوایین بانگەوازی گشتی بڕیار لەسەر پەسەندکردنی هەر ستانداردێک دەدات.
05 بڵاوکردنەوە و ناساندن
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 12UNI دەناسێنێت و هەرگیز بڕوانامە ناداتتۆمار · Nexus Standardsهەر بابەتێکی ساڵی بەرنامە یەک ناسێنەر هەڵدەگرێت، UNI یەک لەژێر NS-1، بۆ ئەوەی ئاماژەی پێ بکرێت، وەشانبەندی بکرێت و چارەسەر بکرێت.
- 13گۆڕانکارییە پەسەندکراوەکانی ساڵەکە بڵاو بکەرەوەهەنگاو · Nexus Standardsلە کاتی نوێکردنەوەدا Nexus Standards گۆڕانکارییە پەسەندکراوەکانی ساڵەکە و دۆخی پەسەندکردنی نیشتمانی بڵاو دەکاتەوە.
06 پەسەندکردن و جێبەجێکردنی نیشتمانی
- 14پەسەندکردنی نیشتمانی لەلایەن ئەنجومەنی نیشتمانیی ستانداردەکانەوەبڕیار · ئەنجومەنی نیشتمانیی ستانداردەکانئەنجومەنی نیشتمانیی ستانداردەکانی هەر وڵاتێک بڕیار لەسەر پەسەندکردنی نیشتمانی دەدات: وەک خۆی پەسەند بکرێت، بە پڕۆفایلێک پەسەند بکرێت (NS-16)، بگونجێنرێت، یان تەنها ئاماژەی پێ بکرێت.
- 15ستانداردە پەسەندکراوەکان دەگەنە خول و وەشانەکانهەنگاو · Nexus Standardsهەر ستاندارد یان پرۆفایلێکی پەسەندکراو دەبێتە مۆدیولی خولێک لە Risk Academy (F09)، و ستانداردەکان لە وەشانەکانی Reports دا جێبەجێ دەکرێن (R1).
- 16پەسەندکردن بۆ هەر ناوچەیەکی دەسەڵات کۆتاییەستاندارد · ئەنجومەنی نیشتمانیی ستانداردەکانپەسەندکردن بۆ هەر ناوچەیەکی دەسەڵات کۆتاییە، و GSC هیچ ڤیتۆیەکی بەسەر بڕیارێکی نیشتمانیدا نییە. هیچ دەزگایەکی جیهانی ڤیتۆی نییە.
- 17تۆمارەکانی پەسەندکردنی نیشتمانیتۆمار · Nexus Standardsپڕۆفایلە پێکهێنراوەکانی ئەرک و تۆمارەکانی پەسەندکردنی نیشتمانی لە قۆناغی ئامادەکردنی ئامادەییدا دەنێردرێن بۆ Foundry (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
| هەنگاو | قۆناغ | کارکردن | کێ | Decision rule | تۆمار | Implements |
|---|---|---|---|---|---|---|
| 01 | Description | Describe artefact (start). The producer states what the artefact is, which scope publishes it, its category, and only the domain, sector, region and environment segments that are true of all of it. | the producer: a person, an institution or an agent under a recorded mandate | one UNI per artefact concept; codes classify, they never name a product | a draft entry: title, scope, category and the context segments that are true of the artefact | NS1-R1, NS1-R6, NS1-R7 |
| 02 | کۆدەکان | Check codes (gate). Scope, domain, sector and environment codes are three-letter registry codes; regions are ISO 3166-1 alpha-3 or UN M49. A missing code is proposed, never invented. | the catalogue validator | every segment is a registry code meeting CA-1 to CA-10; a new code enters through an NS-13 proposal and may be used, with its status shown, until adopted | a validation result for every segment | NS1-R8, NS1-R10 |
| 03 | تەرخانکردن | Mint the UNI (step). The catalogue returns the next serial for the scope, category and context segments. The serial is never reused. | the catalogue of the scope | UNIs are allocated only through the catalogue; never typed by hand | a UNI with a six-digit serial for the full prefix | NS1-R2 |
| 04 | تەرخانکردن | Catalogue record (record). One record per UNI says what the artefact is, who made and publishes it, what rights apply and where it lives. | the catalogue | every record carries the required metadata; the legal state defaults to review-required | the record: title, scope, category, status, creators, publisher, date, rights, legal state, locations | NS1-R4 |
| 05 | Embedding | Embed the UNI (step). Source files carry a header line, documents front matter, datasets a sidecar or metadata key, figures a caption suffix, web pages a meta tag and APIs the X-Nexus-UNI header. | the producer, on each surface | the UNI is embedded in the artefact itself so that machines and people find the record (section 6) | a header line, front matter, sidecar, caption suffix, meta tag or response header | NS1-R5 |
| 06 | ڕوونی | Resolve the UNI (record). The resolver path returns the record; the URN form urn:nexus:uni:<UNI> and the citation forms of NS-2 point to the same record. | the resolver (NS-7) | a UNI identifies and resolves; it never certifies | a landing page for people and JSON for machines at /uni/<UNI> | NS1-R5 |
| 07 | ڕوونی | New version (step). A revision keeps the identifier of the concept; citations of a state cite the version. | the producer | versions share the UNI and differ in @VERSION | the same UNI with a new @VERSION | NS1-R1 |
| 08 | Retirement | Withdraw or replace (end). A withdrawn artefact keeps its record and identifier; a replaced one points to its successor, and identifiers that use a retired code stay valid. | the publisher of record | UNIs are never deleted or reused; a retired code keeps its entry | the record kept with status WITHDRAWN, or with supersededBy | NS1-R3, NS1-R9 |
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 · RFC 8141 Uniform Resource Names (URNs) · NS-1: The UNI and the artefact catalogue · NS-3: Risk record UNIs.
پەیوەستبوونە سیستەمییەکان
4 couplings link this area to other areas and programmes, each with the mechanism of the link.
- Conformance programmeFoundations and GovernanceEvery Implementation Conformance Statement and attestation is an AT record with its own UNI, so the conformance register is a query over the catalogue rather than a separate list.
- Licensing and intellectual propertyFoundations and GovernanceCatalogue records are released as CC0 1.0 metadata so that DataCite, Schema.org and STAC exports can be harvested without attribution friction, while the artefacts keep their own licences.
- How a standard is madeFoundations and GovernanceDrafts, proposals, last-call comments and authority decisions each carry a UNI, which gives the standards track a permanent, citable audit trail.
- Data and EvidenceData and EvidenceThe Data and Evidence programme profiles the record kinds (observation, source release, indicator, boundary) whose UNIs are minted under NS-3 by the governed data service.
How a shock travels through this system
A system model of this area built from the registry: 5 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.
سیستەم و بەستنەوەکان
- The UNI and the artefact catalogue
- بەرنامەی گونجان هاوبەستی
- مۆڵەتدان و موڵکی هزری هاوبەستی
- ستانداردێک چۆن دروست دەکرێت هاوبەستی
- داتا و بەڵگە هاوبەستی
کۆنترۆڵەکان
NS-1UNI و کەتەلۆگی بەرهەمەکان (ڕێزمانی v0.2: بەشەکانی بوار، کەرت، هەرێم و ژینگە)NS-3UNIەکانی تۆماری مەترسی (ڕێزمان، خشتەی گواستنەوەی کۆن، دەسەڵاتی تەرخانکردن)NS-7پەڕەکانی گەیشتنی چارەسەرکەر، تاگە مێتای پەڕە، نەخشەی ماڵپەڕNS-9UNIی ناوەڕۆکی (دامەزراندنەکان، نموونەکان، نموونەکانی پڕۆگرام)NRS-A5مۆڵەتدان و مافەکان لە ناوەوەNRS-C4مۆدێلی داتای مەترسی، ناسێنەرەکان و ئاڵوگۆڕNRS-A3ڕووکاری بریکار بۆ ستانداردەکانNRS-U16Universe platform profile: Institutional Funds Nexus
چاودێری
- DataCite REST API (DOI metadata for crosswalk and harvest tests) (listed for reference)
- ROR data dump (organisation identifiers for publisher and creator fields) (listed for reference)
- ORCID public data file (listed for reference)
- Metadata is identified by a persistent identifier
- Metadata is accessed through standardised protocol
ستانداردە جێبەجێبووەکان
The area profile lists 4 Nexus Standards. 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.
- 02
NS-3 · Risk record UNIs (grammar, legacy crosswalk, allocation authority)
Status: proposed · 0 requirements stated. Read NS-3.
- 03
NS-7 · Resolver landing pages, page meta tags, sitemap
Status: in progress · 0 requirements stated. Read NS-7.
- 04
NS-9 · Contextual UNIs (deployments, instances, programme instances)
Status: proposed · 5 requirements stated. Read NS-9.
Working group charter
A proposed charter for this area, open to institutions and experts.
Maintain NS-1, NS-3 and NS-9, the resolver behaviour (NS-7) and the crosswalks to other persistent identifier systems.
Institutions and experts are invited to charter this working group under NS-13 by filing a public change record. National Working Groups (NWGs) contribute national inputs and field exercises through their National Nexus Consortium (NNC).
- NS-1 edition with a conformance class per embedding surface
- Crosswalk tables UNI to DataCite, Schema.org, CodeMeta and STAC with validator runs
- Resolver test suite (HTML, JSON, headers, sitemap) under Apache-2.0
- DataCite (information exchange on metadata crosswalks sought) liaison sought
- Research Organization Registry (ROR) community (information exchange sought) liaison sought
- Software Heritage (SWHID crosswalk consultation sought) liaison sought
Open standards referenced
6 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
profile2
RFC 8141 Uniform Resource Names (URNs)IETF (RFC Editor)proposed for the registerData Catalog Vocabulary (DCAT) Version 3W3Clisted in the register · w3c-dcat-3crosswalk3
DataCite Metadata Schema 4.5DataCitelisted in the register · datacite-metadata-schema-4-5SoftWare Hash IDentifier (SWHID) specificationSWHID working group (Software Heritage)listed in the register · swhid-iso-iec-18670DOI Handbook (the DOI system, standardised as ISO 26324, named only)DOI Foundationproposed for the registerRouting, monitoring and verification tools
Routing console
Select a sector, hazard family, capability and artefact type; the registry identifies the applicable standards and states the reasons.
Available · from the registryVerification console
Test suites, conformance statements and attestations for each standard, as recorded in the registry.
پلانی بۆ دانراوەDeployment
Reference deployments and a sandbox with worked examples.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
Open research questions
3 questions identified as priorities for the working group.
- How a regional segment should behave when a boundary changes or a country code is retired, without breaking the never-reuse rule.
- Whether contextual UNIs for deployments disclose sensitive infrastructure detail when published, and which fields require restricted handling.
- How to deduplicate concepts that already hold a DOI or SWHID so that one artefact does not acquire competing primary identifiers.
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 decides under its own rules which identified records it accepts as evidence; a resolvable UNI makes a record traceable but is not an acceptance.
Global Risks Forum (GRF)
The Global Risks Forum (GRF) may use UNIs to reference contributions in its own processes and decides recognition independently of whether a record carries one.
Global Risks Alliance (GRA)
The Global Risks Alliance (GRA) decides capital readiness under its own criteria; UNIs only let its reviewers trace an evidence chain to source records.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Intended users
The area profile identifies 4 user communities.
- developers and integrators
- data stewards
- librarians and repository managers
- editors of documents and reports
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.
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
- جێبەجێکردن
- 0 governed service · 0 plugin · 1 browser · 2 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 (DOI metadata for crosswalk and harvest tests)for reference.
DataCite · continuous
CC0 1.0 (metadata)
direct browser readproposed for the data register.
ORCID public data filefor reference
ORCID · annual
CC0 1.0
build-time snapshotproposed for the data register
ROR data dump (organisation identifiers for publisher and creator fields)for reference.
Research Organization Registry · monthly
CC0 1.0
build-time snapshotproposed for the data register
نیشاندەرەکان
The area profile names 2 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
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.
سەرچاوەکان
4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedThe FAIR Guiding Principles for scientific data management and stewardshipScientific Data · 2016- officialFAIR Data Maturity Model: specification and guidelinesResearch Data Alliance · 2020
- standardDataCite Metadata Schema 4.5DataCite · 2024
- standardRFC 8141: Uniform Resource Names (URNs)IETF / RFC Editor · 2017
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; PID infrastructure; DataCite Metadata Schema; RFC 8141 Uniform Resource NamesDerived 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 record provenance, versioning and correction histories, the practice that a persistent identifier makes citable.Apply to this programme Data and ComputeEngineers public-interest data infrastructure and reproducible pipelines, on which resolvable identifiers depend.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, policy and convening
Global Risks Forum (GRF)
Tracks that convene public authorities, researchers and institutions on the governance of shared risks.
Governance NexusCompares authority, oversight and anti-capture arrangements in institutions, the questions that the standards process answers for its own decisions.Join this track Research NexusConvenes research on research integrity and the science-policy interface, the basis of evidence over assertion.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.
Financial Regulation NexusCompares regulatory and supervisory frameworks, the context in which supervised institutions read voluntary standards.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.
- 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.
- 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
- RFC 8141: Uniform Resource Names (URNs)
IETF / RFC Editor · 2017 · Standard - FAIR Data Maturity Model: specification and guidelines
Research Data Alliance · 2020 · Official publication - The FAIR Guiding Principles for scientific data management and stewardship
Scientific Data · 2016 · Peer-reviewed - DataCite Metadata Schema 4.5
DataCite · 2024 · Standard
Related standards and frameworks
- DataCite Metadata Schema 4.5
DataCite - RFC 8141 Uniform Resource Names (URNs)
IETF (RFC Editor) - SoftWare Hash IDentifier (SWHID) specification
SWHID working group (Software Heritage) - Schema.org vocabulary
Schema.org community - Data Catalog Vocabulary (DCAT) Version 3
W3C - DOI Handbook (the DOI system, standardised as ISO 26324, named only)
DOI Foundation
Search terms, derived from the title and scope of the area: persistent identifier; persistent identifiers; digital object identifier; PID infrastructure. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.
پرسیار و وەڵام.
What is the status of the UNI and the artefact catalogue 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 The UNI and the artefact catalogue
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 بۆ کۆدی سەرچاوە. ستانداردە دەرەکییەکان بە ناو، ژمارە و بەستەر لە ژێر مۆڵەتەکانی خۆیاندا ئاماژەیان پێدەدرێت. داتا، کتێبخانە و فۆنتەکانی لایەنی سێیەم مۆڵەتەکانی خۆیان دەپارێزن: بڕوانە ئاگادارییەکانی لایەنی سێیەم.