Nexus StandardsEarly Warning and Anticipatory ActionCross-cutting capabilities
Area · proposed

Alerting and messaging

Profiles OASIS CAP 1.2 for warning and trigger candidates produced by risk engines, requiring UNI identifiers, contextual senders and epistemic-state parameters, and defines the lawful handoff by which only competent alerting authorities issue official warnings. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.

Area recordEarly Warning and Anticipatory Action
  1. TierCross-cutting capabilities
  2. Registryproposed area · no registry row yet
  3. Nexus StandardsNS-10, NS-11, NS-3, NS-9
  4. Open standards5
  5. Feeds3 · 0 admitted
  6. Couplings3
  7. Last reviewed2026-10-17

Context entry PROPOSED for the Nexus Standards registry.

UNI
requested · not yet allocated
Status
PROPOSEDproposed area · no registry row yet
Last reviewed
area context bank
Cite this page

Nexus Standards (2026). Alerting and messaging: area brief, Early Warning and Anticipatory Action (PROPOSED). https://nexustandards.com/early-warning/alerting-and-messaging/. Last reviewed 2026-10-17.

Download the profile

Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.

01Scope

Alerting and messaging: what the area covers, and what it leaves to others.

The cross-cutting capabilities section of Early Warning and Anticipatory Action. Scope as the area context entry states it (PROPOSED).

In scope 4

  • Nexus CAP 1.2 profile and validation
  • Sender identity and register of alerting authorities
  • Candidate versus official warning semantics
  • Multi-language and accessible alert content

Out of scope 2

  • Issuing official public warnings (OFFICIAL_WARNING is not permitted)
  • Operating cell broadcast or sirens

Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.

02Nexus Standards that apply

4 Nexus Standards for this area.

The Nexus Standards the area context entry lists. Every one is proposed or specified; none is adopted by an authority.

  1. 01

    NS-10 · Policies and clauses (machine-readable obligations, enforcement in commons and command rooms)

    Status proposed · 7 rules stated. Read NS-10

  2. 02

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status proposed · 6 rules stated. Read NS-11

  3. 03

    NS-3 · GRIx record UNIs (grammar, legacy crosswalk, allocation authority)

    Status proposed · 0 rules stated. Read NS-3

  4. 04

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status proposed · 5 rules stated. Read NS-9

03Open standards

5 open standards, each with its relation.

Relations are register entries (NS-14), never conformance or equivalence statements; hover or focus a relation for its meaning. 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.

05Systemic couplings

3 couplings to other areas and subsites.

Each coupling names the mechanism that links this area to another; select a card on the canvas to trace it. Mechanisms are stated in the context bank (PROPOSED).

Canvas · the area and its couplingsDesign, not a record
Alerting and messaging: systemic couplingsThe couplings the area context bank records for Alerting and messaging: 1 area in Early Warning and Anticipatory Action, 2 areas in other subsites and 2 subsites reached. Each coupling carries a mechanism stated in the context bank (PROPOSED); a reading aid, not a dependency proof.

Fig.RUNNING marks the area you are reading; DONE an area in the same subsite, QUEUED an area elsewhere and GATE a subsite reached. Tags give reading order only, never a status. Design, not a record.

  1. Real-time and streaming dataData and EvidenceCAP candidates travel as notifications on the WIS2-style topic hierarchy pointing at the resolver, never as the full record.
  2. Early warning and anticipatory actionEarly Warning and Anticipatory ActionAnticipatory-action triggers in that area consume CAP candidates and record their own trigger evaluations.
  3. Translation and localisationCommunities, Learning and ContributionCAP info blocks per language follow the translation rules; translations are informative and carry translator and date.
06Data and feeds

3 sources, with provider, licence and delivery path.

Sources the area reads or proposes. Delivery follows GRIx first; a source is shown live only after an owner decision admits it for public pages.

Every feed · pending admission

No legal register row admits any of these sources for live display on public pages yet, so nothing is read from them here. A register row that exists records the source for the governed GRIx path; admission for public pages is a separate owner decision.

Admitted
0
none yet
Register row exists
3
recorded for the GRIx path
Proposed row
0
terms to be recorded
Delivery
3 GRIx · 0 plugin · 0 browser · 0 snapshot
GRIx first, then plugin, browser-direct, snapshot
  • GDACS events feedpending admission

    European Commission JRC and UN OCHA · continuous

    GDACS terms of use

    GRIx governed readregister row exists

  • NOAA NWS alerts APIpending admission

    NOAA National Weather Service · continuous

    U.S. Government work (public domain)

    GRIx governed readregister row exists

  • WMO Register of Alerting Authorities CAP feedspending admission

    WMO · continuous

    WMO Unified Data Policy plus each alerting authority's terms

    GRIx governed readregister row exists

07Indicators

2 indicators the area tracks.

Indicator names and codes as their stewards publish them; values appear only from a governed GRIx source, never typed into a page.

08Restricted compatibility profiles

No closed standard is named for this area.

Closed or paywalled standards appear by name and link only; any compatibility profile of one is built on simulated data and kept on protected pages until an institutional arrangement with the issuing body is recorded. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

The working group may name closed standards later; they would be listed here by name and link only.

09Working group

The working-group charter, proposed.

Scope

CAP profile, alert integrity clauses and authority handoff.

No working group is chartered yet; a community may charter this one under NS-13 through a docket.

Deliverables · 3
  1. Nexus CAP 1.2 profile with XSD and Schematron tests
  2. Alert integrity clause pack
  3. Handoff protocol for warning candidates
Liaison targets · 4
  • OASIS Emergency Management Technical Committee liaison sought
  • WMO liaison sought
  • ITU-D liaison sought
  • IFRC liaison sought
10Readiness

What each pathway can read from this area.

GCRI Canada evidence pathway

GCRI Canada

GCRI Canada analyses warning performance only from CAP records whose sender, identifier and status can be verified.

Open the GCRI Canada evidence pathway

Recognition pathway

The Global Risks Forum (GRF)

GRF recognises early-warning contributions that hand candidates to the competent authority, not those that issue warnings themselves.

Open the Recognition pathway

Capital pathway

The Global Risks Alliance (GRA)

GRA links parametric triggers to official alert records only through the authority's published messages.

Open the Capital pathway

Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.

11Open problems

2 open problems an expert would start with.

  1. Impact-based warning content that CAP fields represent only loosely.
  2. De-duplicating overlapping alerts from several authorities for the same event.
12Audiences

Who works with this area: 4 audiences.

  1. National meteorological and hydrological services
  2. Civil protection agencies
  3. Humanitarian anticipatory-action teams
  4. Alert software developers
13Hazards and sectors

What acts on this area, and who carries it.

Hazards and threats 0

No hazard or threat is listed for this area; it reads the hazards of the areas it couples with.

Sectors 0

No sector is listed for this area; it serves every sector through the areas it couples with.

14References

3 sourced references.

Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them.

  1. peer-reviewedCommunication of emergency public warnings: A social science perspective and state-of-the-art assessmentOak Ridge National Laboratory (OSTI) · 1990
  2. published statisticsEarly Warnings for AllWMO · 2022
  3. standardCommon Alerting Protocol Version 1.2OASIS · 2010
15Learning

Risk Academy faculties for this area.

Plain links to the faculty pages of Risk Academy; no course, credential, recognition or endorsement is implied.

16Key terms

Terms used on this page.

UNI
Unique Nexus Identifier: identifies and resolves an artifact and its record; it never certifies truth, readiness or approval.
PROPOSED
Drafted content that no authority has adopted. Every area entry here is a proposal to the Nexus Standards registry.
profile
Relation: a Nexus profile narrows or extends the external standard for the nexus, validated with the body's own tools where they exist.
cite
Relation: the external standard is cited by identifier and URL as a reference.
crosswalk
Relation: Nexus clauses are mapped to parts of the external standard by number, never by text.
adopt
Relation: the external standard is used as published, values validated against it.
pending admission
No legal register row admits this source for display on public pages yet, so nothing is read from it.
GRIx
The governed data layer of Nexus Foundry: external data is read through it with its licence and source release.
docket
A public change record under NS-13, decided by editors with written reasons.
attestation
An evaluator's recorded result for one clause and one subject under NS-11; never a certification.
liaison sought
A liaison the working group would ask the body for; none is held unless the body confirms it in writing.
18Learn and apply

Where Alerting and messaging is taught, worked on and run.

Risk Academy disciplines that teach Alerting and messaging, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.

Risk Academy

Disciplines and courses

19Questions

Questions and answers.

Is the Alerting and messaging area adopted?
No. The area entry is PROPOSED content for the Nexus Standards registry; there is no registry row yet. Adoption of any standard is a recorded authority decision and none is recorded today.
Are the feeds on this page live?
No. Every feed is pending admission: no legal register row admits it for public pages yet, so nothing is read from it here.
How do I change this brief?
Through a docket under NS-13: a pull request against the area context bank or the registry, decided by editors with written reasons.
Nexus Standards

Shape this brief: Alerting and messaging.

Propose a change, join the working group or name a source. Area entries are PROPOSED content for the Nexus Standards registry; a UNI identifies and never certifies, and nothing on this site is a certification, an approval or a readiness statement.

Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.

Skip to toolbar