NXS · Foundations
NS-2 citation and attribution: what the standard requires and who it serves
NS-2 proposes one way to cite any artefact or record that carries a UNI. This explainer covers the four citation forms, concept and version citations, DOIs, attribution to people, agents and the publisher of record, and source citation for derived works.
- As of
- 3 November 2026
- Ukufunda
- 10 minutes
- Ubungqina
- 13 sources, cited in order
- Imeko
- Proposed standard
- Ikhowudi
- NS-2 · Citation and attribution format for UNIs
Status and scope
A proposed standard. It is not adopted, approved or certified by any authority.
- Ikhowudi
- NS-2 · Citation and attribution format for UNIs
- Ubungakanani bomsebenzi
- How an artefact or record keyed by a UNI is cited by people and machines, and who receives credit.
- Applies to
- Every citation of a Nexus artefact or record, in text, captions, reference lists and machine exports.
- 1 Forms
- 2 Attribution
- 3 Imithetho
01What NS-2 citation and attribution is
What NS-2 citation and attribution is
NS-2 citation and attribution is the proposed Nexus Standard titled Citation and attribution format for UNIs. Its identifier is NXS-STD-ST-000009 and its current version is 0.1.0, catalogued on 16 October 2026 1. The text is on the NS-2 page.
NS-2 says how an artefact or record keyed by a UNI is cited by people and machines 1. It has three aims: attribution that is exact, versioned and resolvable, and credit for the publisher of record. The publisher of record is an institution, never the technology owner by default 1.
Its parent is NS-1, which defines the UNI itself 1,2. NS-2 is a preparatory working draft circulated for comment on 17 October 2026, and is not for implementation 1.
02Why exact citation matters for risk evidence
Why exact citation matters for risk evidence
Risk decisions travel through many hands. A dataset feeds a model, the model feeds a report, the report is quoted in a briefing and the briefing reaches a minister. If any link in that chain is cited loosely, by a title, a team name or a web address that later changes, the decision loses its trail.
Scholarly publishing solved part of this with persistent identifiers and structured metadata. The DOI system is documented in the DOI Handbook, which describes it at business and technical levels 3. DataCite's metadata schema, now at version 4.7, released on 3 March 2026, describes resources for citation and retrieval 4. NS-2 builds on the same idea, but for every artefact in the ecosystem, including records, figures and code that never pass through a journal 1.
03The four citation forms
The four citation forms
Clause 1 defines four forms 1. The short form is the UNI, or the UNI with a version, for inline text, captions and interfaces, for example NXS-GRX-RP-M002-000007@1.2.0 1.
The full form is for reference lists. It follows the pattern creators, year, title, version, publisher, UNI and then a DOI or URL 1. The standard's own example credits The Global Centre for Risk and Innovation (GCRI), in its Canadian form, as both creator and publisher of a 2026 report on African flood exposure at version 1.2.0, followed by the UNI and a resolver address 1.
The record form cites a record by its UNI and record version together with the source release, for example a record at version 3 drawn from a named release 1. The machine form is written urn:nexus:uni: followed by the UNI, together with CITATION.cff and DataCite exports defined in NS-1 1,2. The URN form follows the syntax of RFC 8141, which defines a URN as a persistent, location-independent identifier 5.
Fig. 01Four ways to cite under NS-2
Figure 1 in words
Column 1, short: UNI or UNI@version, for inline text, captions and interfaces. Column 2, full: creators (year), title (version), publisher, UNI, then DOI or URL, for reference lists. Column 3, record: record UNI at record version, with the source release. Column 4, machine: urn:nexus:uni: plus the UNI, with CITATION.cff and DataCite exports.
04Concept or state: what the version says
Concept or state: what the version says
NS-2 draws a sharp line between two kinds of citation 1. A citation without a version cites the concept: the report, dataset or model as a continuing thing. A citation with a version cites a state: what the artefact said at that version.
Rule NS2-R2 makes the choice explicit. Versioned claims cite a version, and concept citations must be deliberate 1. The difference matters whenever a figure is revised. A statement such as exposure rose by a given share is only checkable against the version that said it. A reading list pointing readers to the latest edition, by contrast, should cite the concept.
Versions themselves follow NS-1, where an artefact's version is a semantic version and a record's version is an integer 2.
05DOIs alongside UNIs
DOIs alongside UNIs
Where a DOI exists, NS-2 places it after the UNI, and the UNI is never omitted 1. This keeps one key across all artefacts, whether or not they have been deposited, while still giving readers the citable identifier their tools expect.
In NS-1, a DOI returned by a deposit is written back to the record as an identical identifier 2. DataCite's controlled list of relation types includes IsIdenticalTo for exactly this kind of link 6. Zenodo, one common deposit route, assigns a DOI to every upload 7.
06Attribution follows the record
Attribution follows the record
Clause 2 says creators and the publisher come from the record's own creator and publisher fields, never from whoever happens to write the citation 1. Rule NS2-R3 adds that the publisher of record is credited 1.
Agents that produced an artefact are credited as creators of the type Agent, with their mandate, while the responsible institution remains publisher of record 1. This matches NS-12, under which every artefact an agent produces credits it as an agent and names its mandate 8.
People are typically identified through persistent researcher identifiers. ORCID provides such identifiers as part of the wider digital infrastructure researchers use to share information 9. For finer detail about who did what, the CRediT Contributor Role Taxonomy offers 14 contributor roles. It was approved as an ANSI/NISO standard in 2022 and is licensed under CC BY 4.0 10. NS-2 version 0.1.0 does not mention CRediT 1.
Fig. 02Who gets credit
Figure 2 in words
Four layers from bottom to top. Record: the creator and publisher fields are the source of attribution. Creators: the people who made the artefact. Agents: credited as creators of type Agent, with their mandate. Publisher of record, highlighted: the responsible institution, never the technology owner by default.
07Derived works cite every source
Derived works cite every source
Clause 2 also sets the provenance rule. Derived works cite every IsDerivedFrom and Compiles relation in their record, following the PROV-O profile of NS-3b, and a figure cites the datasets and records it draws on, under NS-5 1.
These relation names come from the DataCite controlled list, where Compiles indicates that one resource is the result of a compile or creation event using another 6. In W3C PROV-O, a derivation is a transformation of one entity into another 11.
Rule NS2-R4 is unusually firm: omitting a source is a provenance defect, not a style choice 1. A figure without its data citations is therefore incomplete in the same way that a figure without axes would be.
08Citations must resolve
Citations must resolve
Rule NS2-R5 says every cited UNI must be answered, either by the Nexus resolver under NS-7 or by a DOI 1. A citation that leads nowhere fails the standard even if it is formatted correctly.
Under NS-1, the resolver path for a UNI returns an HTML landing page to browsers and JSON to machines 2. That gives a reader a page to read and gives software a record to parse, from the same identifier.
09The five rules in one place
The five rules in one place
Clause 3 condenses NS-2 into five rules 1. NS2-R1: every citation of a Nexus artefact or record carries its UNI, and names alone never cite. NS2-R2: versioned claims cite a version, and concept citations are explicit. NS2-R3: attribution follows the record, the publisher of record is credited and agents are credited as agents. NS2-R4: derived works cite their sources' UNIs, and omission is a provenance defect. NS2-R5: citations resolve through the resolver or a DOI.
Fig. 03From source to citation
Figure 3 in words
Four rising steps. Sources: datasets and records, each with a UNI. Derived work: a figure or report whose record lists derivation and compilation relations. Cited sources, highlighted: every source UNI is cited; omission is a provenance defect. Resolved: every cited UNI answers through the resolver or a DOI.
10Citing in practice: three places
Citing in practice: three places
The forms are easiest to see in use. The examples below reuse the illustrative identifiers that NS-2 and NS-1 themselves give, and describe no real publication 1,2.
A figure caption. A chart that draws on version 1.2.0 of a regional report carries the short form, NXS-GRX-RP-M002-000007@1.2.0, at the end of its source line. A reader can paste it into the resolver and reach the exact state the chart used. Under NS-1, figures already carry their own UNI as a caption suffix, so a caption may hold two identifiers: the figure's own and the source it draws on 2.
A reference list. The same report appears in full form: creators and year, title and version, publisher, UNI, and then a DOI if the report was deposited, or the resolver address if not 1. Readers who never use the resolver still find the work through the DOI, and readers who do can see every other version.
A data record. An observation drawn from a dataset release is cited in record form, with its record version and the release it came from 1. This lets an analyst rerun a calculation on the same inputs months later, because the record version pins the exact value that was used. If the observation is later corrected, a citation of the earlier version still says precisely which value the original calculation relied on, and a reviewer can compare the two versions side by side.
11Working with existing citation tools
Working with existing citation tools
Most readers manage references with tools that already understand DOIs and common formats. NS-2's machine form includes CITATION.cff exports 1. The Citation File Format project explains that a CITATION.cff file placed in a code repository on a major hosting service is linked from the repository page and offered as a ready-made citation, and that reference managers can use it to fill a reference entry 12.
Because NS-2 requires the UNI in every citation, a reference produced by such tools would need the UNI added to its identifier field. A DataCite export can carry it as a related identifier alongside a DOI 2,6.
12Differences and open questions
Differences and open questions
Three points are worth noting for implementers. First, NS-2 credits creators and the publisher of record, but does not yet say how individual contributions should be recorded, where CRediT offers a standard set of roles 1,10. Second, the full form gives a year, while some records will need a full date to distinguish versions issued in the same year 1. Third, NS-1 names DataCite 4.5, while DataCite now lists version 4.7 as the latest 2,4.
These are matters a later version could settle through an NS-13 proposal 13.
13Who NS-2 serves and how to take part
Who NS-2 serves and how to take part
NS-2 serves authors, editors, analysts and the tools they use. It gives each a single way to say exactly which artefact, at which version, from which publisher, and a way to check it 1.
Changes follow the open process on Develop a standard, and comments go through the contact form. The standards are published by GCRI as Secretariat. The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) take part as stakeholders like any other. Learners can study related methods in Risk Academy's Technology and Data course.
14Instruments named in or related to NS-2
Instruments named in or related to NS-2
The table lists external instruments NS-2 names or resembles, as published on 3 November 2026. Each is maintained by its own issuer and applies on its own terms.
| Isixhobo | Relation to NS-2 | Uhlelo |
|---|---|---|
| DOI Handbook | DOI given after the UNI | December 2025 3 |
| DataCite relation types | IsDerivedFrom, Compiles, IsIdenticalTo | Schema 4.5 6 |
| RFC 8141 (IETF) | Machine form as a URN | April 2017 5 |
| W3C PROV-O | Derivation of works | 30 April 2013 11 |
| Citation File Format | Machine export | cff-version 1.2.0 12 |
| CRediT | Contributor roles, not yet referenced | ANSI/NISO, 2022 10 |
What this page does not claim: NS-2 is a proposed, preparatory working draft that its own page says is not for implementation, and no Nexus Standard has been adopted by the Global Standards Council or any National Standards Council. The citation example described here is the one NS-2 gives as an illustration of the format. The International DOI Foundation, DataCite, the IETF, W3C, CRediT, the Citation File Format project, Zenodo and ORCID maintain their own instruments; Nexus Standards has no affiliation with any of them, and an export format is not an alignment claim.
Imibuzo
Imibuzo neempendulo
What is the shortest valid NS-2 citation?
The UNI on its own, or the UNI with a version, for example NXS-GRX-RP-M002-000007@1.2.0, used inline, in captions and in interfaces.
Should I cite a version or not?
Cite a version when you rely on what the artefact said at that point. Cite without a version only when you mean the continuing concept.
What if the artefact also has a DOI?
Give the DOI after the UNI. The UNI is never omitted, so every citation carries the same key.
How are agents credited?
As creators of the type Agent, with their mandate. The responsible institution remains the publisher of record.
What is NS-2's own status?
Proposed. Version 0.1.0 is a preparatory working draft circulated for review and comment, not for implementation, and changes go through NS-13 proposals.
Imiqathango
Glossary
- Publisher of record
- The institution credited as publisher of an artefact, which is not by default the owner of the technology used.
- Concept citation
- A citation without a version, naming the artefact as a continuing thing.
- State citation
- A citation with a version, naming what the artefact said at that version.
- Derived work
- An artefact made from others, such as a figure drawn from datasets or a report compiled from records.
- Resolver
- A service that turns an identifier into a landing page for people and a record for machines.
Okunxulumeneyo
Further reading across the network
- All Nexus Standards
- NS-2: Citation and attribution
- NS-1: The UNI and the artefact catalogue
- NS-3b: Dataset and product metadata profile
- NS-5: Figures, maps and visualisation
- NS-12: Software, model and AI/ML artefacts
- NS-13: Standards development process
- Develop a standard
- Governance of the Nexus Standards
- Glossary
- I-Global Risks Forum
- I-Global Risks Alliance
Imithombo
References
13 sources, numbered in the order they are first cited
- Nexus Standards (2026-10-16). NS-2: Citation and attribution format for UNIs (proposed). nexustandards.com. Accessed 2026-11-03.
- Nexus Standards (2026-10-15). NS-1: The UNI and the artefact catalogue (proposed). nexustandards.com. Accessed 2026-11-03.
- International DOI Foundation (2025-12). DOI Handbook. www.doi.org. Accessed 2026-11-03.
- DataCite e.V. (2026-03-03). DataCite Metadata Schema. schema.datacite.org. Accessed 2026-11-03.
- Internet Engineering Task Force (IETF) (2017-04). RFC 8141: Uniform Resource Names (URNs). www.rfc-editor.org. Accessed 2026-11-03.
- DataCite e.V. (2024-01-22). relationType: DataCite Metadata Schema 4.5 documentation. datacite-metadata-schema.readthedocs.io. Accessed 2026-11-03.
- CERN and OpenAIRE (2026-11-03). Zenodo. zenodo.org. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-12: Software, model and AI/ML artefacts (proposed). nexustandards.com. Accessed 2026-11-03.
- ORCID (2026-11-03). About ORCID. info.orcid.org. Accessed 2026-11-03.
- CRediT, approved as an ANSI/NISO standard (2026-11-03). CRediT: Contributor Role Taxonomy. credit.niso.org. Accessed 2026-11-03.
- World Wide Web Consortium (W3C) (2013-04-30). PROV-O: The PROV Ontology. www.w3.org. Accessed 2026-11-03.
- Citation File Format project (2026-11-03). Citation File Format (CFF). citation-file-format.github.io. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-13: Standards development process (proposed). nexustandards.com. Accessed 2026-11-03.
Irekhodi
Editorial record
Facts as of 3 November 2026. The NS-2 text, version and status were read on its page that day, and every external instrument was checked at its issuer the same day. The FORCE11 and PeerJ pages refused automated access, so the data and software citation principles are not cited. This page is reviewed at least every 180 days and whenever NS-2 changes version or status. Text, visuals and data on this page are licensed CC BY 4.0.
Published by the Standards desk, Nexus Standards. Drafted with AI assistance under the Nexus editorial constitution. To report an error, use the corrections page; corrections are dated and listed here.
Cite this article
Standards desk, Nexus Standards (2026, November 3). NS-2 citation and attribution explained. Nexus Standards. https://nexustandards.com/ns-2-citation-and-attribution/
@online{standards2026ns2citationandattrib,
author = {{Standards desk, Nexus Standards}},
title = {{NS-2 citation and attribution explained}},
publisher = {Nexus Standards},
year = {2026},
month = {11},
url = {https://nexustandards.com/ns-2-citation-and-attribution/},
language = {en}
} TY - ELEC AU - Standards desk, Nexus Standards TI - NS-2 citation and attribution explained PB - Nexus Standards PY - 2026 DA - 2026/11/03 UR - https://nexustandards.com/ns-2-citation-and-attribution/ LA - en ER -
Republish
Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Nexus Standards, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.
Attribution to paste
<p>NS-2 citation and attribution: what the standard requires and who it serves — Standards desk, Nexus Standards, Nexus Standards. First published 3 November 2026 at <a href="https://nexustandards.com/ns-2-citation-and-attribution/">https://nexustandards.com/ns-2-citation-and-attribution/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>
Comment on this draft
Comments are taken clause by clause, with the exact text you propose and your evidence, through the comment form on this site.