Documentation and publication: standards that apply
The 4 standards listed for documentation and publication in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-2, NS-4, NS-7, NS-8.
- Open standards: DataCite Metadata Schema 4.5; Citation File Format (CITATION.cff); CodeMeta; Schema.org CreativeWork; FAIR Signposting profile.
- Data and feeds: Zenodo REST API; Crossref REST API (works); DataCite REST API (DOIs).
- Couples with: Identification (the UNI); Naming, marks and intellectual property; Indexing and discovery.
- Nexus Standards
- 4
- NS-2, NS-4, NS-7
- Open standards
- 5
- named, never copied
- Data and feeds
- 3
- listed for reference
- Couplings
- 3
- with other areas
Citation and attribution format for UNIs
Status proposed · trust, authorisation and assurance; knowledge, records and learning · NXS-STD-ST-000009.
| Rule | Text |
|---|---|
NS2-R1 | Every citation of an artefact or record identified by a UNI shall carry its UNI; a name alone does not cite. |
NS2-R2 | A claim about one version shall cite that version; a citation of the concept shall be explicit. |
NS2-R3 | Attribution shall follow the record: the publisher of record is credited, and agents are credited as agents. |
NS2-R4 | A derived work shall cite the UNIs of its sources; the omission of a source is a provenance defect, not a matter of style. |
NS2-R5 | Citations shall resolve: the resolver (NS-7) or a DOI shall answer for every cited UNI. |
Structure and drafting of Nexus Standards and documents (v0.2: clause structure, verbal forms, registered requirements; document front matter)
Status proposed · knowledge, records and learning · NXS-STD-ST-000010.
NS-4 states its requirements in sections rather than in a table of rules.
Resolver landing pages, page meta tags, sitemap
Status specified · public, client and partner delivery · UNI not yet allocated.
NS-7 is specified elsewhere: SPECIFIED in NS-1 section 1 and NS-16 section 6; implementation status per implementation in the consumers register.
Zenodo publishing workflow with legal gate, DOI write-back, Software Heritage archival
Status open · trust, authorisation and assurance · UNI not yet allocated.
NS-8 is specified elsewhere: OPEN.
Questions and answers.
Are these all the rules for documentation and publication?
What does a rule identifier such as NS1-R5 denote?
Around documentation and publication.
Shape the standards for documentation and publication.
Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.
Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artefact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.