[OASIS Issue Tracker] (EMERGENCY-8) Add hierarchical data to CAP through XML extensions in schema

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

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

Steve Hakusa commented on EMERGENCY-8:
--------------------------------------

I argue for this in a presentation on this at the 2013 CAP conference in Geneva:
http://www.wmo.int/pages/prog/amp/pwsp/documents/CAP-IW-2013-p03-10-US-Google.pdf

The summary of the argument is that, based our interactions with a dozen or so alert publishers globally in the last couple years, the growth in usage of CAP is limited by the difficulty of representing data in a more structured way in the existing CAP standard.  Given that XML is built to be extensible, CAP should allow for that extensibility.

> Add hierarchical data to CAP through XML extensions in schema
> -------------------------------------------------------------
>
>                 Key: EMERGENCY-8
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-8
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
>
> Steve Hakusa: To add hierarchical data to CAP, allow XML extensions in the CAP schema through the following change to the .xsd: <any minOccurs="0" maxOccurs="unbounded" namespace="##other"    processContents="lax" />
>   a. Allow such XML extensions at the <info> level, and optionally at the <alert> level. Having extensions at the <info> level would be required in case the hierarchical data is language-specific.  Extensions at the <alert> level could cut down on redundancy in the case the data is related to all <info> blocks.
> Jacob Westfall: Add extensibility with <xs:any## other minOccurs="0"/> 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)