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).
- 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.
Summary
- Version1.2 (OASIS Standard 1 July 2010; announced 12 August 2010)
- वर्ष2010
- प्रवेशखुले
- Relationadopt
- Verifiedyes: name, body, version and year confirmed at the source
- DomainEarly warning and anticipatory action
- Updateslisted for reference
The relation is shown as recorded in the registry.
- Operations
- 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
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 steps·3 stages·2 gates
NXS · Process
OASIS standards track
मानक जीवनचक्र · NS-13 मार्ग · योगदान माध्यमे · IETF मार्ग · W3C मार्ग · OGC मार्ग · OASIS मार्ग · ISO आणि IEC टप्पे · अनुरूपता · नोंद जीवनचक्र · मार्गनिर्देशन · देखरेख.
A technical committee drafts, public review gates the Committee Specification, statements of use make a candidate, and a membership ballot approves the OASIS Standard.
01 Technical Committee
- 01Technical CommitteeStart · OASIS members, under a charterThe committee’s charter and IPR mode are public; membership is through OASIS.
- 03Committee Specification DraftRecord · the technical committeeDrafts are numbered and public; working drafts precede them.
- 04Committee SpecificationDecision · the technical committeeThe specification is stable at this stage; implementers may build on it.
02 Public review
- 02Public reviewGate · anyone, through the comment listComments arrive on the comment list and are dispositioned by the committee.
- 05Statements of useGate · implementersOrganisations state that they have used the specification; the statements are public.
03 OASIS membership
- 06Candidate OASIS StandardRecord · the technical committeeA sixty-day public review of the candidate precedes the ballot.
- 07Membership ballotDecision · OASIS organisational membersThe ballot is a formal vote of the OASIS membership.
- 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
| पायरी | Phase | संचालन | Who | Decision rule | नोंद |
|---|---|---|---|---|---|
| 01 | Technical Committee | Technical Committee (start). The committee’s charter and IPR mode are public; membership is through OASIS. | OASIS members, under a charter | formed under the TC Process with a declared IPR mode | a technical committee with its IPR mode |
| 02 | Technical Committee | Committee Specification Draft (record). Drafts are numbered and public; working drafts precede them. | the technical committee | approved by a committee vote | a numbered draft |
| 03 | Public review | Public review (gate). Comments arrive on the comment list and are dispositioned by the committee. | anyone, through the comment list | a first review of thirty days; later reviews fifteen days on changes | comments and their dispositions |
| 04 | Technical Committee | Committee Specification (decision). The specification is stable at this stage; implementers may build on it. | the technical committee | a Special Majority vote after public review | the Committee Specification |
| 05 | Public review | Statements of use (gate). Organisations state that they have used the specification; the statements are public. | implementers | three statements of use for a Candidate OASIS Standard | three statements of use |
| 06 | OASIS membership | Candidate OASIS Standard (record). A sixty-day public review of the candidate precedes the ballot. | the technical committee | entry when statements of use are collected | the candidate with its statements of use |
| 07 | OASIS membership | Membership ballot (decision). The ballot is a formal vote of the OASIS membership. | OASIS organisational members | approval by the membership as the TC Process states | the ballot result |
| 08 | OASIS membership | OASIS 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). | OASIS | published after the ballot; may be submitted to de jure bodies | the 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.
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.
- Parts5
- Named sub-parts21
- Machine artefactCAP 1.2 XML Schema (CAP-v1.2.xsd)
- 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).
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.
The crosswalk as a table: 30 external standards by domain
| कार्यक्षेत्र | External standard | Issuing body | Relation |
|---|---|---|---|
| हवामान | GHG Protocol Corporate Accounting and Reporting Standard | World Resources Institute and WBCSD (GHG Protocol) | cite |
| हवामान | GHG Protocol Corporate Value Chain (Scope 3) Accounting… | GHG Protocol | cite |
| हवामान | GHG Protocol Scope 2 Guidance | GHG Protocol | cite |
| हवामान | GOOS Essential Ocean Variables | IOC-UNESCO Global Ocean Observing System | adopt |
| हवामान | IFRS S2 Climate-related Disclosures | International Sustainability Standards Board (IFRS Foundation) | crosswalk |
| हवामान | INFORM Climate Change Risk Index – Concept and Methodology | European Commission Joint Research Centre | cite |
| हवामान | IPCC AR6 Working Group II – risk framing (hazard… | Intergovernmental Panel on Climate Change | adopt |
| हवामान | ISO 14090:2019 Adaptation to climate change – Principles… | ISO/TC 207/SC 7 | crosswalk |
| हवामान | ISO 14091:2021 Adaptation to climate change – Guidelines… | ISO/TC 207/SC 7 | crosswalk |
| हवामान | NGFS long-term climate macro-financial scenarios | Network for Greening the Financial System | cite |
| हवामान | SBTi Corporate Net-Zero Standard | Science Based Targets initiative | cite |
| हवामान | UAE Framework for Global Climate Resilience (Global Goal… | UNFCCC | cite |
| Disaster risk reduction | Comprehensive School Safety Framework 2022–2030 | Global Alliance for Disaster Risk Reduction and Resilience in the Education Sector | crosswalk |
| आपत्ती जोखीम न्यूनीकरण | DELTA Resilience (Disaster and Hazardous Events, Losses… | UNDRR, UNDP and WMO | crosswalk |
| आपत्ती जोखीम न्यूनीकरण | INFORM Risk Index – Concept and Methodology | European Commission Joint Research Centre with the Inter-Agency Standing Committee | profile |
| आपत्ती जोखीम न्यूनीकरण | Risk Data Library Standard (RDLS) | Global Facility for Disaster Reduction and Recovery | profile |
| आपत्ती जोखीम न्यूनीकरण | Sendai Framework for Disaster Risk Reduction 2015–2030 | UN Member States (Third UN World Conference on DRR); UNDRR custodian | crosswalk |
| आपत्ती जोखीम न्यूनीकरण | Sendai Framework Monitor (38 indicators) | UNDRR | crosswalk |
| आपत्ती जोखीम न्यूनीकरण | UNDRR-ISC Hazard Information Profiles (HIPs) | UNDRR and International Science Council | adopt |
| आपत्ती जोखीम न्यूनीकरण | WMO Cataloguing of Hazardous Events (WMO-CHE) | WMO (adopted by Congress 2019) | crosswalk |
| Early warning and anticipatory action | Early Action Protocols under the DREF anticipatory pillar | IFRC | cite |
| पूर्वसूचना आणि पूर्वकृती | Early Warnings for All initiative and Executive Action… | WMO, UNDRR, ITU, IFRC (co-leads) | crosswalk |
| पूर्वसूचना आणि पूर्वकृती | ISO 22322:2022 Security and resilience – Emergency… | ISO/TC 292 | crosswalk |
| पूर्वसूचना आणि पूर्वकृती | ITU-T Recommendation X.1303 bis Common alerting protocol… | ITU-T | cite |
| पूर्वसूचना आणि पूर्वकृती | Multi-hazard Early Warning Systems: A Checklist | WMO and UNDRR | crosswalk |
| पूर्वसूचना आणि पूर्वकृती | OASIS Common Alerting Protocol Version 1.2 | OASIS Emergency Management TC | adopt |
| पूर्वसूचना आणि पूर्वकृती | OASIS EDXL Situation Reporting (EDXL-SitRep) Version 1.0 | OASIS Emergency Management TC | cite |
| पूर्वसूचना आणि पूर्वकृती | OASIS Emergency Data Exchange Language (EDXL) Distribution… | OASIS Emergency Management TC | cite |
| पूर्वसूचना आणि पूर्वकृती | WMO Global Multi-hazard Alert System (GMAS) | WMO | cite |
| पूर्वसूचना आणि पूर्वकृती | WMO Register of Alerting Authorities and CAP alert… | WMO | adopt |
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.
- NS-0 Constitution and principlesStatusPROPOSED12RulesClause-level crosswalkin preparation under NS-14
- NS-3 Risk record UNIs (grammar, legacy crosswalk, allocation authority)StatusPROPOSED0RulesClause-level crosswalkin preparation under NS-14
- NS-3b Dataset and product metadata profile (STAC, DCAT, PROV-O)StatusPROPOSED0RulesClause-level crosswalkin preparation under NS-14
- NS-11 Verification and monitoring (evidence, attestations, zero-trust conformance observation)StatusPROPOSED6RulesClause-level crosswalkin preparation under NS-14
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.
| अंमलबजावणी | By | हे काय आहे |
|---|---|---|
| ITU-T Recommendation X.1303 bis | ITU-T | the CAP 1.2 text published as an ITU-T Recommendation (registry entry itu-t-x-1303bis) |
| WMO Register of Alerting Authorities | World Meteorological Organization | the register of authorities that issue CAP alerts and their feed locations |
| Test suite or validator | What it checks |
|---|---|
| CAP 1.2 XML Schema | validate 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.
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 | हे काय आहे | What it requires | दुवा |
|---|---|---|---|
| Technical committee | OASIS Emergency Management TC, the committee that maintains CAP | OASIS membership to join; the committee’s pages and minutes are publicly available | Open the technical committee page |
| Public comment list | emergency-comment list archive: the channel for comments from non-members | subscription and acceptance of the OASIS feedback licence | Open the public comment list page |
| Process document | OASIS Technical Committee Process (registry entry oasis-tc-process) | to be read before participating | Open the process document page |
| IPR policy | OASIS IPR Policy: the committee’s IPR mode applies to contributions | membership agreement for committee members | Open the ipr policy page |
Process explorer · NXS · Process
Contributing through a standards body
11 steps·3 stages·1 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.
01 Contributor
- 01Identify the bodyStart · the contributorEach standard package links to the issuing body, its working group or technical committee and its process document.
- 02Read IPR and participation rulesStep · the contributorParticipation rules differ by body, from no membership at the IETF to membership at OASIS.
- 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.
- 07Implement and testExercise · the contributorThe contributor runs the body’s test suite or validator, where the body publishes one.
02 The standards body
- 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.
- 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.
- 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.
- 08Implementation reportRecord · the body or the working groupImplementations are listed as submitted, in alphabetical order.
03 Nexus Standards
- 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.
- 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.
- 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
| पायरी | Phase | संचालन | Who | Decision rule | नोंद |
|---|---|---|---|---|---|
| 01 | Contributor | Identify the body (start). Each standard package links to the issuing body, its working group or technical committee and its process document. | the contributor | the register names the body and links to its own page | the body’s page, linked from the package |
| 02 | Contributor | Read 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 contributor | membership, patent policy and contributor agreements are set by the body and read at the source | the requirements of the channel |
| 03 | The standards body | Join 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 committee | the channel belongs to the body and follows its process document | a list subscription, an issue account, a membership |
| 04 | The standards body | File 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 tracker | an issue is the body’s record, cited by URL | an issue with a stable link |
| 05 | The standards body | Public 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 process | the body decides under its own rules; the Nexus Standards record the public outcome | comment dispositions by the body |
| 06 | Contributor | Propose 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 channel | text is proposed through the body’s own channel; the body’s text remains with the body | a change request, an Internet-Draft or a comment with wording |
| 07 | Contributor | Implement and test (exercise). The contributor runs the body’s test suite or validator, where the body publishes one. | the contributor | a passing run is evidence of implementation | a test run with the suite version and time |
| 08 | The standards body | Implementation report (record). Implementations are listed as submitted, in alphabetical order. | the body or the working group | listed as the body publishes it, without ranking | the report, linked |
| 09 | Nexus Standards | Cite 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 editors | cited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalence | a crosswalk entry or a clause citing the source |
| 10 | Nexus Standards | Change 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 recorded | every change is submitted as a change proposal under NS-13 | a change proposal with a UNI |
| 11 | Nexus Standards | Register change (end). The register entry is amended and the package page is regenerated from it. | editors, with reasons on record | accepted, rejected or withdrawn in writing; the history is retained | the 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.
Tools and their availability
Run the test suite in the browser
A browser-based test run on worked examples is in progress. In the meantime, CAP 1.2 XML Schema, published by the body, can be run at the source.
AvailableOpen the schema
CAP 1.2 XML Schema (CAP-v1.2.xsd), at the body’s own address.
Available · composed in the browserDownload the profile
The composer opens with this standard and the area’s Nexus Standards selected, and produces YAML or JSON with citations and the licence line.
PlannedOpen in an integrated application
An integration point on this page is reserved for compatible applications and is not yet active.
A passing test run constitutes implementation evidence.
Latest releases from the body
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 source | नोंदवही | स्वरूप | Browser read | Delivery | Cadence |
|---|---|---|---|---|---|
oasis.news.feed | data-sources | rss | unknown | governed data service, build-time snapshot | daily |
oasis.tc.emergency.list | data-sources | html | unknown | governed data service, build-time snapshot | daily |
oasis.tc.emergency.comment-list | data-sources | html | unknown | governed data service, build-time snapshot | daily |
oasis.docs.cap-1-2.artifacts | data-sources | html | unknown | build-time snapshot | weekly |
wmo.register-alerting-authorities | data-sources | html | unknown | governed data service, build-time snapshot | weekly |
5 data sources listed.
प्रश्न आणि उत्तरे.
Do the standards reproduce CAP 1.2?
Where do the updates come from?
Is the relation a conformance statement?
Around hydrometeorological hazard.
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.
स्थिती आणि वापर. Nexus Standards ही NS-13 अंतर्गत खुल्या प्रक्रियेद्वारे विकसित केलेली आणि ऐच्छिक वापरासाठी प्रकाशित प्रस्तावित मानके आहेत; ती प्रमाणन, अधिस्वीकृती किंवा नियामक मंजुरी ठरत नाहीत, आणि स्वीकार हा जागतिक मानके परिषदेचा आणि प्रत्येक देशात त्याच्या राष्ट्रीय मानके परिषदेचा निर्णय राहतो. UNI (Unique Nexus Identifier) वस्तू ओळखतो; तो तिचे प्रमाणन करत नाही. मानके संस्थांची आणि त्यांच्या मानकांची नावे त्यांच्या विश्वस्तांची आहेत आणि केवळ दस्तऐवज ओळखण्यासाठी वापरली जातात; बाह्य मानकाचा कोणताही मजकूर येथे पुनरुत्पादित केलेला नाही. Nexus Standards येथे नमूद कोणत्याही मानके संस्थेशी संलग्न नाही, तिच्याकडून समर्थित किंवा प्रमाणित नाही.
परवाने: मानकांचा मजकूर, नोंदवह्या, स्कीमा आणि माहितीसाठी CC BY 4.0; संदर्भ कोडसाठी Apache-2.0. बाह्य मानके त्यांच्या स्वतःच्या परवान्याखाली नाव, क्रमांक आणि दुव्याद्वारे उद्धृत केली जातात. तृतीय-पक्ष माहिती, ग्रंथालये आणि फॉन्ट त्यांचे स्वतःचे परवाने राखतात: तृतीय-पक्ष सूचना पाहा.