[OASIS Issue Tracker] (EMERGENCY-36) add a profile element

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

     [ https://issues.oasis-open.org/browse/EMERGENCY-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomer Petel updated EMERGENCY-36:
---------------------------------

    Proposal: 
Add an element called
<profile>
Which will indicate to the consumer of the CAP message, which profile this CAP message is, thereby allowing consumer to select the right parser/processor. 

  was:
add an element called
<profile>

that tells the consumer of the CAP message what profile this CAP message is and thereby allow it to select the right parser/processor. 


> add a profile element 
> ----------------------
>
>                 Key: EMERGENCY-36
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-36
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tomer Petel
>
> Currently every major user of CAP has their own "profile". A well known example is, for example, IPAWS.
> A consuming system would like formal knowledge of the profile of CAP it is processing so that it can apply the proper processing module to it. Otherwise it would have to look for unofficial hints that may or may not be supported long term. 



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