Re: [emergency-cap-profiles] IPAWS eventCode note

[Rex Brooks <rexb@starbourne.com>]

We should bring this up in the TC meeting and decide whether to 
address it or wait and add it to the Public Review comments.

Cheers,
Rex

At 12:44 PM -0500 2/16/09, Jacob Westfall wrote:
>  > Seems to me that if all info blocks in an alert must relate to a
>>  single incident or update with the same category and eventCode, that
>>  limits it to one eventCode per alert.
>
>Both category and eventCode are multiple value elements.  The info 
>block requirement doesn't limit them to a single value only, just 
>that all info blocks must use matching values.  So this example 
>would be valid under the current language,
>
>...<info>
>   <eventCode>SAME=abc</eventCode>
>   <eventCode>SAME=def</eventCode>
></info>
><info>
>   <eventCode>SAME=abc</eventCode>
>   <eventCode>SAME=def</eventCode>
></info>
>
>However you don't want to limit it to one eventCode entirely since 
>other code lists might be in use by an issuer for other system needs,
>
>...<info>
>   <eventCode>SAME=abc</eventCode>
>   <eventCode>CustomStateCode=123</eventCode>
>
>So whats needed is a restriction of only one eventCode of valueName 
>"SAME" per info block.  This of course contrasting with the geocode 
>where multiple geocodes of valueName "SAME" are allowed.
>
>--
>jake@jpw.biz
>--
>
>---------------------------------------------------------------------
>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


-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670