OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (EMERGENCY-21) UIDs for alert identifier and references

    [ https://issues.oasis-open.org/browse/EMERGENCY-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41840#comment-41840 ] 

Eliot Christian commented on EMERGENCY-21:

This proposal singled out the Universally Unique Identifier (UUID) for the value of a CAP alert identifier. It should be noted that the UUID specification is one among multiple information technology mechanisms in common use to provide globally unique identifiers. Particular mechanisms were discussed in a CAP Workshop in Geneva in 2009 ( http://www.wmo.int/pages/prog/www/ISS/Meetings/WIS-CAP_Geneva2009/DocPlan.html ) that was convened to address the need for a CAP alert identifier that is globally unique. 

Discussion during the 2009 CAP Implementation Workshop on Identifiers included: general requirements such as simplicity, usability, flexibility, extensibility, scalability, and deployability; considerations about distributed versus centralized management approaches of various identifier schemes; considerations about long-term reliability of identifier registrars, and the availability of high-performance tools for discovering information associated with any given identifier. The recommendation from that Workshop was to use Object Identifiers (OIDs). OIDs (Object Identifiers) are explained at http://www.oid-info.com

Following that recommendation, ISO and ITU established an arc of the OID tree specifically for alerting: {joint-iso-itu-t(2) alerting(49)} (see http://oid-info.com/get/2.49 ). In 2010, WMO in association with ITU published the "Administrative Procedure for Registering WMO Alerting Identifiers" (see http://www.wmo.int/pages/prog/amp/pwsp/documents/AIR_PWS-20.pdf ) This document established the rules for registration of all OIDs subordinate to the alerting OID arc administered by WMO: {joint-iso-itu-t(2) alerting(49) wmo(0)} (see http://oid-info.com/get/2.49.0 ). These OIDs are allocated to alerting authorities as registered in the international Register of Alerting Authorities (see http://www.wmo.int/alertingorg ).

There are four arcs of alerting OIDs administered by WMO (see http://oid-info.com/cgi-bin/display?tree=2.49.0&see=all ). These distinguish between OIDs used for identifying alerting authorities and OIDs used for identifying alert messages from those alerting authorities. The arcs are also distinguished between alerting authorities that are organized within countries and alerting authorities that are other organizations. The four arcs are: Alerting authorities of countries; Alerting messages of countries; Alerting authorities of other organizations; Alerting messages of other organizations. 

> UIDs for alert identifier and references
> ----------------------------------------
>                 Key: EMERGENCY-21
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-21
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
> Art Botterell;  alert.identifier and alert.references: I'd like to propose for future versions of CAP the TC consider the specification of a Universally Unique Identifier (UUID) as the value of alert.identifier and of entries in alert.references. While this would make the identifiers longer, it would reduce the risk of non-unique identifiers and simplify the construction of references. UUIDs are spec'd in ITU X.667 and IETF RFC 4122.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]