[OASIS Issue Tracker] (CAPAU-4) alert.info.headline/description change from optional to required

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/CAPAU-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36865#comment-36865 ] 

Norm Paulsen commented on CAPAU-4:
----------------------------------

Optional or Required in the context of XML is based on system processing of an XML message. If <description> can be empty, and it may very well be during a <msgType>Cancel, so in that context it is "optional". The business context of <description> being required to run an effective alerting "alerting" operation is just that a "business" rule. Making it conditionally required (based on <msgType>) is not the place of CAP/OASIS to set that rule. This is where communities (like IPAWS) need to take ownership of such rules. If I want to play  in the community that makes that rule then I need to follow it. So technically, I support no change to the CAP Standard even though I support the idea of the rule. I hope communities step up and take ownership and create their profile with such rules. 

> alert.info.headline/description change from optional to required
> ----------------------------------------------------------------
>
>                 Key: CAPAU-4
>                 URL: https://tools.oasis-open.org/issues/browse/CAPAU-4
>             Project: OASIS EDXL CAP
>          Issue Type: Improvement
>            Reporter: Tony Mancuso
>
> From Norm Mueller. CAP 1.2 discussions.



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)