Re: [emergency] Mandatory fields when msgType=Cancel ?

Interesting situation. One of a few recently which certainly deserve to be 
carefully thought through.

Ciao,
Rex

At 09:16 AM 1/31/2005, Art Botterell wrote:
>The U/S/C triad is mandatory whenever the optional <info> block is 
>present.  In most cases you're right, a Cancel won't have an <info> block 
>at all.  However, some senders have expressed a desire to be able to 
>annotate their Cancel messages with new <headline>, <description> etc. 
>elements... e.g., in the case of an all-clear from a hazmat incident.  In 
>that case, the U/S/C values should reflect the new, post-crisis 
>situation.  (I've never been entirely satisfied with that arrangement 
>myself, but nobody's come up with a simpler one.)
>
>- Art
>
>
>At 11:57 AM -0500 1/31/05, Bob Wyman wrote:
>>In CAP V1.0 and draft V1.1, it appears that <urgency/>, <severity/>, and 
>><certainty/> are always required fields. However, it doesn't seem to make 
>>sense that these fields would be required when the msgType is "Cancel." 
>>Why is it useful to require that these fields be present when a message 
>>is being cancelled? If they are present, what should the value of these 
>>fields be when the msgType is "Cancel"?
>>Typically, when one is canceling a message, one wants to say as little as 
>>possible about the original - you just want it to go away.
>>
>>                         bob wyman
>
>
>To unsubscribe from this mailing list (and be removed from the roster of 
>the OASIS TC), go to 
>http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php.
>
>

Rex Brooks
President, CEO, Starbourne Communications Design
Executive Director, Humanmarkup.org, Inc.
1361-A Addison
Berkeley, CA 94702
510-849-2309