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: Form submission from: Request a template / starter document


Submitted on Friday, June 7, 2019 - 18:48
Submitted by user:
Submitted values are:

Your name: Rex Brooks
TC name: Emergency Management
TC email address: emergency@lists.oasis-open.org
Work product title and version number: Common Alerting Protocol Event Terms
List
Version 1.0
Work product abbreviation: cap-etl-v1.0-cn.docx
Track: Non-Standards Track Work Product
Abstract:
The variety of practices employed regarding âeventâ types in CAP messages
makes it difficult to compare messages from different sources. The problem
has
been presented as an interoperability issue where some consumers of CAP
struggle
to compare differences in language and meaning of the terms used in the
element
in CAP.

The  element is the focus for this effort as it is the only required element
in
CAP directly associated with the subject event for a CAP message. Aligning
practices surrounding this element, as opposed to other possible candidate
elements, is the choice adopted in this work product for addressing this
interoperability concern.

However, the  element is a free form text element meant to communicate with
the
final audience and not necessarily for the automated systems that process
CAP.
The only constraint on  is that it be in the same language as indicated by
the
element in the  block the  element is found in. Therefore, for consumers, the
ability to rely on this element for uses other than just display is not
possible.

With this in mind, the concept of a mapping table where CAP originators and
CAP
consumers can contribute âeventâ lists has been conceived. With this
table,
language terms can be mapped to each other as a reference for client
consumers
thus allowing some measure of interoperability to be possible.
Template type: Basic (for most prose documents)
Format: Microsoft Word
Chair(s):
Elysa Jones, Individual Member, Emergency Management Technical Committee,
Jacob Westfall, Individual Member, Emergency Management Common Alerting
Protocol
Subcommittee
Editor(s):
Rex Brooks, rexb@starbourne.com, Individual
Norm Paulsen, norm.paulsen@canada.ca, Environment Canada
Scott Robertson, Scott.M.Robertson@kp.org, Kaiser Permanente
Namespace(s):
Notes:


The results of this submission may be viewed at:
http://tools.oasis-open.org/issues/browse/TCADMIN


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