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

Art Botterell commented on EMERGENCY-21:
----------------------------------------

Based on conversation within the CAP subcommittee today I'm persuaded that this is not a necessary change, and that it wouldn't necessarily be that much of an improvement over the current scheme.  Possibly we got it right the first time!

> 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
(v6.2.2#6258)


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