Static view: the interactive graph runs where this page’s scripts and WebGL can; every node is also linked on this page.
Reports · Nexus Standards · Capability
capability
Data and evidence in Reports
Every claim in the ecosystem is only as good as the record behind it. This page shows the series it feeds, the evidence behind it and how to contribute.
- Series
- 3
- Systems
- 4
- Areas
- 8
What this area brings to the editions.
Every claim in the ecosystem is only as good as the record behind it. This subsite holds the identifier, data, provenance, statistics, publication, decision-record, privacy and streaming standards, with PROV-O as its worked package.
From Foundry evidence to the series.
The evidence, step by step, from the systems this area reads to the series it feeds.
How Data and evidence reaches Reports: what it reads, how it reads it, the sealed cut and the series it feeds.
| Step | What happens | Source |
|---|---|---|
| 01 What it reads | Data and evidence reads The Global Risks Index (NXS-GRX) and NXS-NSF (trust, authorisation and assurance): governed sources with their releases, never a value without its source. | |
| 02 The cut is sealed | Each quarter the evidence is sealed in one cut, so OBSERVED, REPORTED and ESTIMATED values stay apart and every edition can be rebuilt. | |
| 03 The series it feeds | The cut feeds Methods and Technical and Global Sector Risk and Resilience, from the Baseline Edition 2026 into the quarterly series. | |
| 04 Who decides | Decisions stay with the authorities that hold them, under their own rules; an edition informs a decision and never makes it. |
A teaching model of the evidence path, not a forecast and not a record of any run; the systems, methods and series named come from the registries. Sources: Data and evidence in Reports (2026); Data and evidence home (2026).
The series it feeds, and what backs each.
| Series | Foundry systems it draws on | Academy disciplines | Series home |
|---|---|---|---|
| Methods and Technical | NXS-GRX the methods, indicators and validation studies behind each product NXS-LAB (research, experiments and simulations) method comparisons under transparent test conditions NXS-NXQ (software, models and capability lifecycle) the fitness record of models and tools the methods use | Quantitative risk analysis and statistics Model risk and validation Risk indicators and composite indices | Methods and Technical series home |
| Global Sector Risk and Resilience | NXS-GRX one sector’s structure, dependencies and concentration measures NXS-EOP (earth observation and digital twins) observed change in the sector’s assets and their surroundings | Trade, supply chains and geoeconomics Critical infrastructure and lifelines | Global Sector Risk and Resilience series home |
| Evidence Brief | NXS-GRX the evidence behind one question, with its strength and gaps NXS-POR (public, client and partner delivery) the public-safe release of a brief and its corrections NXS-DSS (decision cases and deliberation) what the evidence settles for the decision in hand | Research, evidence and the science-policy interface Risk communication and risk literacy Uncertainty and decision making | Evidence Brief series home |
The 8 areas inside Data and evidence.
Each area is a section of this Nexus Standards subsite. Its parts, indicators and working group feed the standards progress reported each quarter.
- capabilitiesNS-1 · NS-3 · NS-9 · NS-6 · NS-7Identification (the UNI)Specifies how every artefact, NXS-GRX record and deployment context receives one permanent Unique Nexus Identifier (UNI) through catalogue or fabric allocation, how…
- capabilitiesNS-3 · NS-3b · NS-11 · NS-1Data and datasetsDefines the NXS-GRX record model for observations, source releases, corrections and data cuts, the NS-3b dataset and product metadata profile over STAC, DCAT 3 and…
- capabilitiesNS-2 · NS-4 · NS-7 · NS-8Documentation and publicationGoverns document templates with uni front matter, citation of artefacts by UNI, resolver landing pages, and the Zenodo and DataCite publication pipeline that deposits…
- capabilitiesNS-3b · NS-11 · NS-3Provenance and evidenceDefines receipts, digests, PROV-O lineage graphs, correction history and supported claim levels so that every risk statement can be traced to referenced (never embedded)…
- capabilitiesNS-3 · NS-3b · NS-11Indicators and statisticsDefines indicator and measure records, series metadata and release practice for risk statistics, adopting SDMX and DDI, aligned with the UN Fundamental Principles of…
- capabilitiesNS-10 · NS-11 · NS-9 · NS-13Decision records and accountabilitySpecifies decision records and dockets: who decided, under which mandate, on what evidence, with what dissent and review date, kept append-only and time-stamped, so…
- capabilitiesNS-10 · NS-11 · NS-3Privacy and data protectionSets privacy and data-protection requirements for risk records: purpose limitation, minimisation, public-safe projections, statistical disclosure control and…
- capabilitiesNS-3 · NS-6 · NS-11Real-time and streaming dataSpecifies event and notification semantics for real-time risk data: MQTT 5 topics modelled on the WIS2 hierarchy, notification messages that point to governed records…
Parts and open standards applied here.
Nexus Standards parts are preparatory working drafts (2026); external standards are cited, never reproduced.
The systems, methods and teaching behind it.
Where the same subject is reported elsewhere.
- Coupled areaNexus StandardsRegistries and the resolverEvery UNI minted under NS-1 and NS-3 must resolve at /uni/{uni} with content negotiation; an identifier that does not resolve is treated as unallocated by the resolver section.
- Coupled areaNexus StandardsData and datasetsEvery notification carries the recordUni@recordVersion it announces, so subscribers fetch through the governed read service.
- Coupled areaNexus StandardsDocumentation and publicationThe UNI is embedded in front matter, captions and DataCite exports; a DOI is written back as an external binding only after the legal gate, never minted in place of the UNI.
- Coupled areaNexus StandardsNaming, marks and intellectual propertyDeposit is refused unless legalState is APPROVED and a publication decision record exists.
- Coupled areaNexus StandardsProvenance and evidenceA decision record cites evidence bundles and attestations by UNI@version so its basis survives later corrections.
- Coupled areaNexus StandardsIndicators and statisticsIndicator and measure definitions (IN, ME record kinds) bind series to SDMX structures, so statistics are released as governed records with their own UNIs.
- Coupled areaNexus StandardsGeospatial and Earth observationSpatial datasets inherit NS-3b plus the STAC and COG profile; boundary versions (BD records) carry the boundary licence gate.
- Coupled areaNexus StandardsIdentification (the UNI)Front matter and DataCite exports are generated from the UNI record, so a document and its catalogue record cannot disagree on title or version.
Contribute on Data and evidence.
Evidence, a case, a correction, a method or profile input on this subject. The composer tags it with this area and its series.
Write a contribution the editor can act on.
Say what it is, where its record is kept and on which licence. It arrives tagged with this page, its area and its gateway, so it reaches the editor who owns it.
Your email opens with the subject and a template already filled in for GW-STD.
- Evidence
- Correction
- Case study
- Analysis or method
- Peer review
- Translation
- Profile input
Never send personal data or sensitive infrastructure detail. A contribution is reviewed before use; sending it confers no authorship or editorial rights.
Open science for Data and evidence.
How a contribution on this subject is deposited, identified, credited, licensed and found, and the metadata for it prefilled from this page.
Data and evidence’s open record
- Area
- Data and evidence
- Feeds
- Methods and Technical, Global Sector Risk and Resilience, Evidence Brief
- Record
- A UNI for every accepted contribution; cited with its DOI in the edition that uses it
- Links
- isSupplementTo the edition it informs; isNewVersionOf its earlier version
- Licence
- CC BY 4.0 (SPDX CC-BY-4.0) for original material; metadata CC0 1.0
Credit and identity
- ORCID
- Your iD in the deposit and the contribution record; DataCite can then add the work to your ORCID record
- ROR
- Your organisation by its ROR identifier, never by a typed name alone
- CRediT
- Conceptualization, Data curation, Formal analysis, Investigation, Methodology, Software, Validation, Visualisation, Writing, review and editing
- Account
- None needed to contribute; never a password
Find and follow
Search the open indexes for Data and evidence; software is cited by its SWHID from Software Heritage. Annotation is your choice: Hypothesis opens this page in its own viewer.
Mirrors and harvest
The DOI is canonical. At release each signed bundle is also given an IPFS content identifier and a bloxberg anchor as mirrors; both are listed in the record once they exist. Zenodo exposes every record over OAI-PMH, and reviews and endorsements can arrive through COAR Notify where the repository supports it.
{
"metadata": {
"resource_type": {
"id": "dataset"
},
"title": "Evidence on Data and evidence for Nexus Reports",
"publication_date": "YYYY-MM-DD",
"creators": [
{
"person_or_org": {
"type": "personal",
"family_name": "Your family name",
"given_name": "Your given name",
"identifiers": [
{
"scheme": "orcid",
"identifier": "0000-0000-0000-0000"
}
]
},
"affiliations": [
{
"id": "ROR identifier of your organisation"
}
]
}
],
"description": "What it is, where its record is kept and how it bears on Data and evidence in Nexus Reports.",
"rights": [
{
"id": "cc-by-4.0"
}
],
"subjects": [
{
"subject": "Nexus Reports"
},
{
"subject": "Data and evidence"
},
{
"subject": "capability"
}
],
"related_identifiers": [
{
"identifier": "https://nexustandards.com/nexus-reports/areas/data-identifiers-and-evidence/",
"scheme": "url",
"relation_type": {
"id": "issupplementto"
},
"resource_type": {
"id": "other"
}
}
],
"version": "1.0.0"
},
"custom_fields": {},
"access": {
"record": "public",
"files": "public"
},
"files": {
"enabled": true
},
"parent": {
"communities": {
"default": "nexusreports"
}
}
}Releases for this area.
Releases tagged to this area appear here once released.
Send evidence on Data and evidence.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-STDSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- 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.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Around the reports at Nexus Standards.
Bring what you know to the next edition.
Every quarter closes on a sealed evidence cut. Contributions received before the cut are reviewed for that edition; later ones wait for the next.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.