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=48547#comment-48547 ] 

Steve Hakusa commented on EMERGENCY-21:

From https://www.oasis-open.org/apps/org/workgroup/emergency-cap/download.php/53696/July28-2014-meeting-notes.doc

The motion to mark this issue as “no action needed” was put forward. Art moved and it was seconded by Eliot. Art and Rex discussed how best to resolve the identifiers issue at the TC level for all standards. A comment should be added to this issue to state that global identifiers could be addressed by the TC if needed later. All agreed with the motion and it passed.

> 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]