Skip to content

Enforce correct CAP identifier OID format (WMO / ITU specification) #142

@marta-baraibar

Description

@marta-baraibar

Summary

Ensure all CAP alert identifier values conform to the ITU OID specification and the WMO guidelines for CAP identifiers. Currently, some alerts incorrectly start with urn:oid:2.49.0.0… instead of urn:oid:2.49.0.1….

Background / Problem

The CAP identifier element must be globally unique, persistent, and standards-compliant. When based on an ITU OID, the format must adhere to both ITU and WMO specifications.

  • Observed issue: Some alerts are being published with identifiers beginning with 2.49.0.0 (incorrect).
  • Correct format: Identifiers must begin with 2.49.0.1 for published alerts.

Reference (WMO guideline):

First value 2 → OID namespace registered by ISO/ITU.

Second value 49 → Emergency alert system.

Third value 0 → Alert publisher registered in the WMO International Register of Alerting Authorities.

Fourth value 1 → Published alert (instead of 0, which would denote information about the publisher).

Example of valid identifier (Ethiopia):

urn:oid:2.49.0.1.231.0.2024.9.1.10.0.0

Acceptance Criteria

  • Publish blocked if identifier starts with 2.49.0.0.
  • Publish allowed only if identifier starts with 2.49.0.1.
  • Error clearly explains the required format.
  • Draft save allowed with warning.
  • Auto-generation of valid identifiers available in UI.
  • Unit tests for valid vs invalid identifiers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    checkRequires check to ensure all is well

    Type

    Projects

    Status

    CAP Backlog

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions