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-8) Add hierarchical data to CAP through XML extensions in schema


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

Art Botterell commented on EMERGENCY-8:
---------------------------------------

Steve,  your slides seem to have overlooked the Resource block, which provides precisely this sort of extension point.

> 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)


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