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-36) add a profile element

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

Nuwan Waidyanatha commented on EMERGENCY-36:

There are suggestions to replace the word Profile with Policies and Procedures. If that is so, then would we need to provide both. For example, a policy may state that when rendering a CAP message for Sri Lanka it should carry the human readable summary in Sinhala, Tamil, and English. Then procedure would indicate that the summary should be constructed using the XSL provided at the certain URL and no other. Can we be a little more specific as to what a Profile should carry; i.e. is there a validator for a profile?

> 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 some users of CAP have their own "profile". A well known example is, for example, IPAWS.
> A consuming system may like to have a 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

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