Skip to content
StandardsHydrometeorological hazardOpen standard package
CAP 1.2 · adopt

OASIS Common Alerting Protocol Version 1.2

The registry entry for CAP 1.2, with the body’s development process, the clause map, the crosswalk, adoption, participation channels, tools and updates. Artefacts that apply it carry a UNI (Unique Nexus Identifier).

Standardên metirsiyên hîdrometeorolojîk
What this area is built from, with the open standards it names marked: they are cited or crosswalked, never copied.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-0, NS-3, NS-3b, NS-11.
  • Open standards: WMO Cataloguing of Hazardous Events (WMO-CHE); Common Alerting Protocol Version 1.2; WMO Information System 2.0 (WIS 2.0); CF Metadata Conventions; UNDRR-ISC Hazard Information Profiles; WMO Register of Alerting Authorities and CAP guidance.
  • Data and feeds: ECMWF open data (IFS and AIFS real-time forecasts); ERA5 reanalysis (Copernicus Climate Data Store); GloFAS global flood forecasts and reanalysis; NWS API active alerts (CAP 1.2 as GeoJSON); CHIRPS quasi-global gridded precipitation.
  • Couples with: Water; Early warning and anticipatory action; Energy; Climate.
01Dîmenek giştî

Kurte

Registry entrythe external standards register · oasis-cap-1-2
  1. Version1.2 (OASIS Standard 1 July 2010; announced 12 August 2010)
  2. Sal2010
  3. Gihîştinvekirî
  4. Relationadopt
  5. Verifiedyes: name, body, version and year confirmed at the source
  6. Updateslisted for reference

The relation is shown as recorded in the registry.

Xebitandin
8
in the OASIS track
Clause map
5
parts, numbers and titles
Siblings
9
entries in early warning and anticipatory action
Data sources
5
listed for reference
02Pêvajo

How OASIS develops a standard such as CAP 1.2

The stages of the body’s own process document, step by step: the actor, the decision rule and the record each operation leaves. OASIS Technical Committee Process and IPR Policy.

Process explorer · NXS · Process

OASIS standards track

8 steps3 stages2 gates

NXS · Process

OASIS standards track

Çerxa jiyanê ya standardê · Rêça NS-13 · Kanalên beşdariyê · Rêça IETF · Rêça W3C · Rêça OGC · Rêça OASIS · Qonaxên ISO û IEC · Lihevbûn · Çerxa jiyanê ya tomarê · Rêkirin · Çavdêrî.

A technical committee drafts, public review gates the Committee Specification, statements of use make a candidate, and a membership ballot approves the OASIS Standard.

  1. 01 Technical Committee

    1. 01Technical CommitteeStart · OASIS members, under a charterThe committee’s charter and IPR mode are public; membership is through OASIS.
    2. 03Committee Specification DraftRecord · the technical committeeDrafts are numbered and public; working drafts precede them.
    3. 04Committee SpecificationDecision · the technical committeeThe specification is stable at this stage; implementers may build on it.
  2. 02 Public review

    1. 02Public reviewGate · anyone, through the comment listComments arrive on the comment list and are dispositioned by the committee.
    2. 05Statements of useGate · implementersOrganisations state that they have used the specification; the statements are public.
  3. 03 OASIS membership

    1. 06Candidate OASIS StandardRecord · the technical committeeA sixty-day public review of the candidate precedes the ballot.
    2. 07Membership ballotDecision · OASIS organisational membersThe ballot is a formal vote of the OASIS membership.
    3. 08OASIS StandardOutcome · OASISThe OASIS Standard is published; CAP 1.2 followed this path and was later published as an ITU-T Recommendation (X.1303 bis).

OASIS Technical Committee Process · OASIS IPR PolicyAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · OASIS track8 operations
GavQonaxXebitandinKîDecision ruleTomar
01Technical CommitteeTechnical Committee (start). The committee’s charter and IPR mode are public; membership is through OASIS.OASIS members, under a charterformed under the TC Process with a declared IPR modea technical committee with its IPR mode
02Technical CommitteeCommittee Specification Draft (record). Drafts are numbered and public; working drafts precede them.the technical committeeapproved by a committee votea numbered draft
03Public reviewPublic review (gate). Comments arrive on the comment list and are dispositioned by the committee.anyone, through the comment lista first review of thirty days; later reviews fifteen days on changescomments and their dispositions
04Technical CommitteeCommittee Specification (decision). The specification is stable at this stage; implementers may build on it.the technical committeea Special Majority vote after public reviewthe Committee Specification
05Public reviewStatements of use (gate). Organisations state that they have used the specification; the statements are public.implementersthree statements of use for a Candidate OASIS Standardthree statements of use
06OASIS membershipCandidate OASIS Standard (record). A sixty-day public review of the candidate precedes the ballot.the technical committeeentry when statements of use are collectedthe candidate with its statements of use
07OASIS membershipMembership ballot (decision). The ballot is a formal vote of the OASIS membership.OASIS organisational membersapproval by the membership as the TC Process statesthe ballot result
08OASIS membershipOASIS Standard (end). The OASIS Standard is published; CAP 1.2 followed this path and was later published as an ITU-T Recommendation (X.1303 bis).OASISpublished after the ballot; may be submitted to de jure bodiesthe OASIS Standard

Table.A technical committee produces a Committee Specification Draft; a public review gates the Committee Specification; with statements of use the specification becomes a Candidate OASIS Standard; a membership ballot approves it as an OASIS Standard, which may then be submitted to other bodies. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OASIS Technical Committee Process · OASIS IPR Policy.

Compare with the Nexus track and other standards bodies.

03Clause map

Public structure of the document

Part numbers and titles, linked to the body’s own document; the machine-readable artefact published by the body is linked at the source.

Clause map · the document’s public structure, navigableFrom the registry
Clause map5 parts
  1. Beş5
  2. Named sub-parts21
  3. Text reproducednone

Numbers and titles only; every part opens the body’s own document.

Obligations that a Nexus Standard adopts or profiles are written as Nexus clauses (NS-10) citing the source by identifier and clause number (NS-14).

04Tabloya beramberiyê

CAP 1.2 among the standards of early warning and anticipatory action

The registry relation is adopt: The Nexus Standards use the external standard as it is for a function. Evidence: Validation of values against the external scheme.

Crosswalk graph · hydrometeorological hazard, around this standardNexus Standards registry
OASIS Common Alerting Protocol Version 1.2: crosswalk62 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 72 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 30 external standards by domain
QadExternal standardIssuing bodyTêkilî
AvhewaGHG Protocol Corporate Accounting and Reporting StandardWorld Resources Institute and WBCSD (GHG Protocol)cite
AvhewaGHG Protocol Corporate Value Chain (Scope 3) Accounting…GHG Protocolcite
AvhewaGHG Protocol Scope 2 GuidanceGHG Protocolcite
AvhewaGOOS Essential Ocean VariablesIOC-UNESCO Global Ocean Observing Systemadopt
AvhewaIFRS S2 Climate-related DisclosuresInternational Sustainability Standards Board (IFRS Foundation)crosswalk
AvhewaINFORM Climate Change Risk Index – Concept and MethodologyEuropean Commission Joint Research Centrecite
AvhewaIPCC AR6 Working Group II – risk framing (hazard…Panela Navdewletî ya Guherîna Avhewayêadopt
AvhewaISO 14090:2019 Adaptation to climate change – Principles…ISO/TC 207/SC 7crosswalk
AvhewaISO 14091:2021 Adaptation to climate change – Guidelines…ISO/TC 207/SC 7crosswalk
AvhewaNGFS long-term climate macro-financial scenariosNetwork for Greening the Financial Systemcite
AvhewaSBTi Corporate Net-Zero StandardScience Based Targets initiativecite
AvhewaUAE Framework for Global Climate Resilience (Global Goal…UNFCCCcite
Disaster risk reductionComprehensive School Safety Framework 2022–2030Global Alliance for Disaster Risk Reduction and Resilience in the Education Sectorcrosswalk
Kêmkirina xetera karesatanDELTA Resilience (Disaster and Hazardous Events, Losses…UNDRR, UNDP and WMOcrosswalk
Kêmkirina xetera karesatanINFORM Risk Index – Concept and MethodologyEuropean Commission Joint Research Centre with the Inter-Agency Standing Committeeprofile
Kêmkirina xetera karesatanRisk Data Library Standard (RDLS)Global Facility for Disaster Reduction and Recoveryprofile
Kêmkirina xetera karesatanSendai Framework for Disaster Risk Reduction 2015–2030UN Member States (Third UN World Conference on DRR); UNDRR custodiancrosswalk
Kêmkirina xetera karesatanSendai Framework Monitor (38 indicators)UNDRRcrosswalk
Kêmkirina xetera karesatanUNDRR-ISC Hazard Information Profiles (HIPs)UNDRR and International Science Counciladopt
Kêmkirina xetera karesatanWMO Cataloguing of Hazardous Events (WMO-CHE)WMO (adopted by Congress 2019)crosswalk
Hişyariya zû û çalakiya pêşdestîEarly Action Protocols under the DREF anticipatory pillarIFRCcite
Hişyariya zû û çalakiya pêşdestîEarly Warnings for All initiative and Executive Action…WMO, UNDRR, ITU, IFRC (co-leads)crosswalk
Hişyariya zû û çalakiya pêşdestîISO 22322:2022 Security and resilience – Emergency…ISO/TC 292crosswalk
Hişyariya zû û çalakiya pêşdestîITU-T Recommendation X.1303 bis Common alerting protocol…ITU-Tcite
Hişyariya zû û çalakiya pêşdestîMulti-hazard Early Warning Systems: A ChecklistWMO and UNDRRcrosswalk
Hişyariya zû û çalakiya pêşdestîOASIS Common Alerting Protocol Version 1.2OASIS Emergency Management TCadopt
Hişyariya zû û çalakiya pêşdestîOASIS EDXL Situation Reporting (EDXL-SitRep) Version 1.0OASIS Emergency Management TCcite
Hişyariya zû û çalakiya pêşdestîOASIS Emergency Data Exchange Language (EDXL) Distribution…OASIS Emergency Management TCcite
Hişyariya zû û çalakiya pêşdestîWMO Global Multi-hazard Alert System (GMAS)WMOcite
Hişyariya zû û çalakiya pêşdestîWMO Register of Alerting Authorities and CAP alert…WMOadopt

Nexus Standards in the graph: NS-0, NS-3, NS-3b, NS-11. A relation is a register entry, never a compliance claim.

4 Nexus Standards · 3 domains · 30 external standards · 25 issuing bodies · 0 implementing repositories. Relations (adopt, profile, crosswalk, cite) are as recorded in the register; names and standards remain with their stewards.

Crosswalk graph62 nodes and 72 links: this standard, the entries in the area’s principal domains, their bodies, the Nexus Standards the area lists and their implementers. Relations are shown as recorded in the registry.

05Pejirandin

Implementations, listed as submitted

Implementations and validators in alphabetical order; the implementers of the area’s Nexus Standards with their implementation status; and the entries of the open-standards stack that name this standard. Listings are not a ranking.

Adoption · CAP 1.2Compiled from public sources
BicihanînByÇi ye
ITU-T Recommendation X.1303 bisITU-Tthe CAP 1.2 text published as an ITU-T Recommendation (registry entry itu-t-x-1303bis)
WMO Register of Alerting AuthoritiesRêxistina Meteorolojiyê ya Cîhanêthe register of authorities that issue CAP alerts and their feed locations
Test suite or validatorWhat it checks
CAP 1.2 XML Schemavalidate a message against the schema the body publishes

NoteThe outline, participation channels, implementations, test suites, schema and data feeds on this page were compiled from the body’s public pages on 16 October 2026; all other information is taken from the registry entry.

06Beşdar bibe

Participation in CAP 1.2

The participation channels of the body and the requirements of each, followed by the general path from a comment at the body to a registry change in the Nexus Standards.

ChannelÇi yeWhat it requiresGirêdan
Technical committeeOASIS Emergency Management TC, the committee that maintains CAPOASIS membership to join; the committee’s pages and minutes are publicly availableOpen the technical committee page
Public comment listemergency-comment list archive: the channel for comments from non-memberssubscription and acceptance of the OASIS feedback licenceOpen the public comment list page
Process documentOASIS Technical Committee Process (registry entry oasis-tc-process)to be read before participatingOpen the process document page
IPR policyOASIS IPR Policy: the committee’s IPR mode applies to contributionsmembership agreement for committee membersOpen the ipr policy page

Process explorer · NXS · Process

Contributing through a standards body

11 steps3 stages1 gate

NXS · Process

Contributing through a standards body

A contributor joins a body’s channel under its rules, files issues, reviews, proposes and tests, and Nexus Standards cites the outcome through a change proposal.

  1. 01 Contributor

    1. 01Identify the bodyStart · the contributorEach standard package links to the issuing body, its working group or technical committee and its process document.
    2. 02Read IPR and participation rulesStep · the contributorParticipation rules differ by body, from no membership at the IETF to membership at OASIS.
    3. 06Propose textStep · the contributor, in the body’s channelWording goes to the body’s own channel. In Nexus Standards, the obligation becomes a clause (NS-10) citing the source clause.
    4. 07Implement and testExercise · the contributorThe contributor runs the body’s test suite or validator, where the body publishes one.
  2. 02 The standards body

    1. 03Join a channelStep · the body’s working group or committeeMailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires.
    2. 04File an issueRecord · the contributor, in the body’s trackerAn erratum, a question or a proposal becomes an issue in the body’s tracker; the Nexus Standards cite it by link.
    3. 05Public reviewGate · the body, under its processPublic reviews and last calls are the body’s own stages. The monitoring console shows their dates once the body’s feed exists.
    4. 08Implementation reportRecord · the body or the working groupImplementations are listed as submitted, in alphabetical order.
  3. 03 Nexus Standards

    1. 09Cite the outcomeStep · Nexus Standards editorsThe outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source.
    2. 10Change proposalRecord · any person, with identity recordedA change proposal is a change request to the canonical repository, with a public proposal record. Editors decide with reasons.
    3. 11Register changeOutcome · editors, with reasons on recordThe register entry is amended and the package page is regenerated from it.

OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claimsAn outline of how the work is designed to run; it does not report the status of any decision or record.

The operations, as a table
Process · from a comment at the body to a register change11 operations
GavQonaxXebitandinKîDecision ruleTomar
01ContributorIdentify the body (start). Each standard package links to the issuing body, its working group or technical committee and its process document.the contributorthe register names the body and links to its own pagethe body’s page, linked from the package
02ContributorRead IPR and participation rules (step). Participation rules differ: an IETF working group requires no membership; an OASIS technical committee requires membership; W3C groups have community and member forms.the contributormembership, patent policy and contributor agreements are set by the body and read at the sourcethe requirements of the channel
03The standards bodyJoin a channel (step). Mailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires.the body’s working group or committeethe channel belongs to the body and follows its process documenta list subscription, an issue account, a membership
04The standards bodyFile an issue (record). An erratum, a question or a proposal becomes an issue in the body’s tracker; the Nexus Standards cite it by link.the contributor, in the body’s trackeran issue is the body’s record, cited by URLan issue with a stable link
05The standards bodyPublic review (gate). Public reviews and last calls are the body’s own stages. The monitoring console shows their opening and closing dates once the body’s feed is available.the body, under its processthe body decides under its own rules; the Nexus Standards record the public outcomecomment dispositions by the body
06ContributorPropose text (step). Wording is submitted to the body’s own channel. In the Nexus Standards, the same obligation is expressed as a clause (NS-10) that cites the source by clause number.the contributor, in the body’s channeltext is proposed through the body’s own channel; the body’s text remains with the bodya change request, an Internet-Draft or a comment with wording
07ContributorImplement and test (exercise). The contributor runs the body’s test suite or validator, where the body publishes one.the contributora passing run is evidence of implementationa test run with the suite version and time
08The standards bodyImplementation report (record). Implementations are listed as submitted, in alphabetical order.the body or the working grouplisted as the body publishes it, without rankingthe report, linked
09Nexus StandardsCite the outcome (step). The outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source.Nexus Standards editorscited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalencea crosswalk entry or a clause citing the source
10Nexus StandardsChange proposal (record). A change proposal is a change request to the canonical repository, with a proposal record in the public change record. Editors decide with written reasons.any person, with identity recordedevery change is submitted as a change proposal under NS-13a change proposal with a UNI
11Nexus StandardsRegister change (end). The register entry is amended and the package page is regenerated from it.editors, with reasons on recordaccepted, rejected or withdrawn in writing; the history is retainedthe amended register entry and its history

Table.A contributor identifies the standards body, reads its participation and intellectual property rules, joins a channel, files an issue, takes part in the public review, proposes text, and implements and tests; the body publishes the implementation report. The Nexus Standards cite the outcome through a change proposal that becomes a register correction, a crosswalk entry or a clause. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claims.

08Nûkirin

Latest releases from the body

Updates · listed for reference

Data sources are listed for reference; live data is displayed once licence review is complete. The latest version of the standard recorded in the registry is 1.2 (OASIS Standard 1 July 2010; announced 12 August 2010) (2010). Latest at OASIS Emergency Management TC.

After licence review, data are delivered, in order of preference, through the governed data service, the site integration, a direct browser read of an open endpoint, or a build-time snapshot with its timestamp; the age of the data is always shown. Monitoring console: worked example.

Data sourceRegistryFormatBrowser readRadestkirinCadence
oasis.news.feeddata-sourcesrssnenasgoverned data service, build-time snapshotdaily
oasis.tc.emergency.listdata-sourceshtmlnenasgoverned data service, build-time snapshotdaily
oasis.tc.emergency.comment-listdata-sourceshtmlnenasgoverned data service, build-time snapshotdaily
oasis.docs.cap-1-2.artifactsdata-sourceshtmlnenasbuild-time snapshotweekly
wmo.register-alerting-authoritiesdata-sourceshtmlnenasgoverned data service, build-time snapshotweekly

5 data sources listed.

09Pirs

Pirs û bersiv.

Do the standards reproduce CAP 1.2?
No. The page names and links the document, lists its part numbers and titles, and cites it by identifier and clause number; the text remains with the body.
Where do the updates come from?
From the body’s own channels, once licence review of the data source is complete; until then, the page shows the latest version recorded in the registry.
Is the relation a conformance statement?
No. A relation is a registry entry. Conformance is shown clause by clause through attestations under NS-11.
Standards

Building on CAP 1.2

Relations to this standard are recorded in the registry. Changes are submitted as proposals under NS-13 and may be prepared through the working groups and the National Working Groups of participating countries.

Rewş û bikaranîn. Nexus Standards standardên pêşniyarkirî ne ku bi pêvajoyeke vekirî di bin NS-13 de hatine pêşxistin û ji bo bikaranîna dilxwazî hatine weşandin; ew ne belgename, ne akreditasyon û ne pejirandina rêkxistinê ne, û pejirandin biryara Encûmena Standardên Cîhanî û, li her welatî, ya Encûmena Standardên Neteweyî ya wê dimîne. UNI (Unique Nexus Identifier) berhemekê nas dike; wê belgename nake. Navên desteyên standardan û standardên wan aîdî parêzvanên wan in û tenê ji bo naskirina belgeyan têne bikaranîn; tu nivîsa standardeke derve li vir nayê dubarekirin. Nexus Standards bi tu desteya standardan a li vir hatiye binavkirin ve ne girêdayî ye, ji aliyê wê ve nayê piştgirîkirin û belgename nekiriye.

Lîsans: CC BY 4.0 ji bo nivîsa standardan, tomargeh, şema û daneyan; Apache-2.0 ji bo koda referansê. Standardên derve bi nav, hejmar û girêdanê di bin lîsansên xwe de têne jêgirtin. Dane, pirtûkxane û fontên aliyê sêyem lîsansên xwe diparêzin: binêre Agahdariyên aliyê sêyem.