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-163) ETL: Modified 5.3.5

Jacob Westfall created EMERGENCY-163:

             Summary: ETL: Modified 5.3.5
                 Key: EMERGENCY-163
                 URL: https://issues.oasis-open.org/browse/EMERGENCY-163
             Project: OASIS Emergency Management TC
          Issue Type: Improvement
          Components: EDXL-CAP 
            Reporter: Jacob Westfall

Modify the content for 5.3.5


{color:#4c4635}proxy terms that are otherwise not event terms (i.e., âredâ).{color}

{color:#4c4635}Red is not an event on its own, it is a quality tied to an impact scale. âRedâ may be used by the authority in the <headline>, <description>, <parameter> or other elements as an alerting authority based preferred term but as an event these terms do not convey the idea of an event and make comparisons difficult. Multi-word terms that try to make an event out of a proxy event (i.e., âred issueâ) are also not accepted, as this assumes a scale-based term. Turning the proxy term into an event in this manner provides no context to the term event as the definition of red on its own is a color. NOTE: Communities, such as public alerting based communities, are welcome to establish a set of color based terms and codes, however, originators of CAP messages are asked to also include a reference to the OASIS event code in one instance of the multi-instanced CAP <eventCode> element based on the actual event.{color}

This message was sent by Atlassian Jira

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