Re: [emergency] [OASIS Issue Tracker] (EMERGENCY-32) Make eventCode mandatory

[Art Botterell <acb@incident.com>]

Seems like this could be tricky as eventCode has no specified value-set.  Making it mandatory would seem to require CAP system operators to create or adopt eventCode schemas, which not all of them would want or need to do.


> On Nov 17, 2014, at 09:13, OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> wrote:
> 
> 
>     [ https://issues.oasis-open.org/browse/EMERGENCY-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Steve Hakusa updated EMERGENCY-32:
> ----------------------------------
> 
>    Component/s: CAP 
> 
>> Make eventCode mandatory
>> ------------------------
>> 
>>                Key: EMERGENCY-32
>>                URL: https://issues.oasis-open.org/browse/EMERGENCY-32
>>            Project: OASIS Emergency Management TC
>>         Issue Type: Bug
>>         Components: CAP 
>>           Reporter: Steve Hakusa
>> 
>> Suggestion extracted from https://www.oasis-open.org/apps/org/workgroup/emergency-cap/download.php/54116/Sep15-2014-meeting-notes.doc and https://issues.oasis-open.org/browse/EMERGENCY-1
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.2.2#6258)
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>