Start here: how this desk | Reports Nexus Standards

01What Reports is

Reports is the Consortium’s quarterly publication. Nexus Standards writes the desk that reports where open standards stand. If you adopt, assess or extend a standard, this desk records what was adopted, what conformed and what crosswalks exist.

Atlas of the Standards Progress desk: its mandate, the series it leads, the eight chapters of its edition, what to send here and its Zenodo community. The sections below give the same facts as text. — The Standards Progress desk atlas, with its facts written out below.

02This desk: Standards Progress

Nexus Standards reports the state of the standards: adoption, conformance, crosswalks and the domain and industry profiles. The Global Centre for Risk and Innovation (GCRI) is the secretariat.

Mandate: The state of the Nexus Standards parts and of the external standards they adopt: adoption, conformance attested by those who apply them, crosswalks, and domain and industry profiles. The parts are preparatory working drafts (2026); conformance is attestation, not certification.

Series this desk leads:

Methods and Technical

03The six desks

Standards Progress is one of six desks, and it deposits to its own Zenodo community under the flagship.

Diagram of the six desks and the flagship Zenodo community nexusreports. The table below lists the desks.

The six desks
Desk	Edition	Zenodo community
GCRI	Systems Evidence	`nexusreports-gcri`
GRF	Public Deliberation	`nexusreports-grf`
GRA	Capital Readiness	`nexusreports-gra`
NXS	Standards Progress	`nexusreports-nxs`
RA	Capability	`nexusreports-ra`
GRX	Measurement	`nexusreports-grx`

04The edition in eight chapters, in this desk’s terms

The chapters follow a standard’s life, from where one is needed to the crosswalks that connect it to others.

The eight chapters of the Standards Progress edition
Chapter	Title	What it covers
1	Where standards are needed	The places in the systems in scope where a shared standard is missing or contested.
2	Adoption findings	Which parts are adopted or applied, by whom, as the adopting bodies state it.
3	Domain and industry profiles	The domain and industry profiles that read the scope against the parts.
4	Conformance and assurance	Conformance attested by those who apply the parts, and how each attestation can be checked.
5	Change scenarios	How the parts would need to change under stated scenarios; conditional, never predictions.
6	Readings from the other desks	Readings from the other desks: cross-references to their editions for the same scope, not copies of them.
7	Standards work programme	The dockets, drafts and reviews the next cycle takes up, under the open development process.
8	Crosswalks	Crosswalks from the parts to the external standards they adopt or align with.

05How to contribute

Send adoption or conformance evidence, a crosswalk or a proposed clause. Cite the clause number and the version it applies to.

This desk takes:

Evidence that a body has adopted or applies a part, stated by that body
A conformance attestation, with what was checked
A crosswalk between a part and an external standard
A proposed clause or a comment on a part, for its docket

The gateway page of the Standards Progress desk gives the route.

06The editorial workflow

A proposed clause is handled like any submission: screened for scope, reviewed, decided with reasons. The review model declared at submission tells you who sees what.

Diagram of the editorial workflow in six steps: submit, screen, review, decide, accept, publish, with a revision branch and a decline or appeal branch. The list below gives every step.

The editorial workflow
Step	What happens
1. Submit	Contributor declarations and licence terms are signed first.
2. Screen	Editors check scope, completeness and licensing.
3. Review	Peer review runs under the model declared at submission. Authors may revise, then the work returns to review.
4. Decide	Named editors decide and record their reasons. Declined work can be appealed through a separate route.
5. Accept	The decision is recorded and the work moves to production.
6. Publish	A named editor publishes. The DOI is issued.

07The sixteen-gate quarterly cycle

The cycle sets when a clause can be taken into an edition. A clause that misses the submission deadline waits for the next quarter.

Diagram of the sixteen gates of a quarterly cycle, from the call opening to the corrections window closing. The list below gives every gate.

The sixteen gates of a quarterly cycle
Order	Gate	Meaning
1	call_open	The call opens.
2	call_close	The call closes.
3	submission_deadline	Last moment to submit into this cycle. Later submissions roll to the next cycle.
4	triage_close	Intake triage must be finished.
5	review_open	The review window opens.
6	reviewer_reminder	First reminder to reviewers.
7	review_close	Reviews are due. Overdue reviews escalate and are reassigned.
8	decision_date	The editorial decision is due.
9	revision_close	The revision window ends.
10	copyedit_freeze	Copyedit and data-check freeze.
11	evidence_close	Evidence close.
12	production_close	Production ends.
13	release_approval	The named approver signs the release.
14	release	Release date. It is the anchor of the cycle.
15	deposit_approval	Zenodo deposit approval. The deposit stays a draft until then.
16	corrections_close	The corrections window ends.

08Release control

Standards work depends on file rules. Release needs open or documented formats and a checksum on every file, and these are checked before approval.

Diagram of release control: seven checks must pass, the named approver signs, six artefacts are fixed with checksums, the Zenodo deposit stays a draft, then the record is published with a DOI.

09Open licensing

An edition’s text is CC BY 4.0 and its data is CC0 1.0. Code that implements a standard needs an OSI-approved licence.

Licence rules

Text, figures and maps: CC BY 4.0 (SPDX: CC-BY-4.0).
Data: CC0 1.0 (SPDX: CC0-1.0).
Code: an OSI-approved licence.
Media: CC BY 4.0 or CC0 1.0.
No NC, ND or SA licence on our own outputs. No paywall, no embargo on text, no fees.

Shared text. It is the same on every Reports site by design.

10Zenodo community and DOIs

Standards records go to the Nexus Standards desk community on Zenodo. It exists, every submission is reviewed, and it is still empty.

This desk’s community: zenodo.org/communities/nexusreports-nxs

Flagship community: nexusreports. It exists and holds records today.
Every record carries a DOI and a full version history. A correction becomes a new version and keeps the concept DOI.

Shared text. It is the same on every Reports site by design.

11The open science stack, with its honest status

Machine-readable output is the point of this stack for adopters. RO-Crate and JATS XML are built. ROR needs an id, and Crossref is an export only.

Diagram of the open science stack with the status of each integration. The table below gives every status.

The open science stack and its status
Integration	What it does	Status
Zenodo	DOIs, deposits and versions	Built
ORCID	Contributor identity and review credit	Built
ROR	Institution identifiers	Needs the id
COAR Notify	Inbox for peer review services	Built
OAI-PMH	A harvesting endpoint	Built
JATS XML	Journal article markup	Built
RO-Crate	Research object packaging	Built
Crossref	An export, not in use	Export only

Cite

Reports, Standards Progress, start here [Draft under review]. GCRI for the Nexus Consortium.

Review copy. The DOI is issued at deposit. Text under CC BY 4.0.

Name	Purpose	Duration	Party
`wordpress_*`cookie	Strictly necessaryThis site	Until you sign out	First party
`wordpress_logged_in_*`cookie	Strictly necessaryThis site	Until you sign out, or 14 days	First party
`wordpress_sec_*`cookie	Strictly necessaryThis site	Until you sign out, or 14 days	First party
`wordpress_test_cookie`cookie	Strictly necessaryThis site	Session	First party
`wp-settings-*`cookie	Strictly necessaryThis site	1 year	First party
`wp-postpass_*`cookie	Strictly necessaryThis site	10 days	First party
`comment_author_*`cookie	Strictly necessaryThis site	About 347 days	First party
`wpEmojiSettingsSupports`browser storage	Strictly necessaryThis site	Session	First party
`nexus_consent`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent_id`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent_reset`cookie	Strictly necessaryPrivacy choices	Session	First party
`wp_consent_*`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent`browser storage	Strictly necessaryPrivacy choices	180 days	First party
`nx_theme`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.theme.default`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bx-color-mode`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bx-color-mode-against`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.embed.theme`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`buddyx_dark_mode`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`buddyx_color_mode_against`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.a11y`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.dock`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bp-activity`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-groups`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-members`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-blogs`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-messages`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party

Start here: how this desk of Reports works