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-4) Require alert.info.headline and alert.info.description

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

David Askov commented on EMERGENCY-4:

My input is that whatever path is chosen, the XSD should validate to these rules. We want to require a tag /alert/info/headline (and description), but only if another tag /alert/msgType does not have content of "Cancel". I'm no XSD wizard, but I don't know how you would validate this in the XSD. Someone on the call said that it could be done. I'd appreciate the chance to learn how, but mostly I just wanted to make sure it is possible, since I don't know any way to require an element based on the content of another element. 

I'm really pretty neutral on this issue, but I would oppose it if it could not be validated with XSD. It is too hard for our programmers to have extra rules outside the XSD to keep track of. 

Other notes: 
-- The parent tag /alert/info is optional, so we agreed that this issue is moot when info is not present. 
-- One caller mentioned that there are other parts of CAP that do not validate with the XSD. Do we have a list of those, or does anyone know what they are? I'd like to get that so I can pass it on to our programmers. 

> Require alert.info.headline and alert.info.description
> ------------------------------------------------------
>                 Key: EMERGENCY-4
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-4
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP

This message was sent by Atlassian JIRA

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