Representation of Tactical Situation Objects
Contact e-mail: Sean.Barker # baesystems.com
General purpose and services to the end user
The application provides lightweight protocol for situation awareness in emergency response.
The protocol shall present table-driven attribute values, including types of action, types of resource, relationships between items, etc.
n/a - this is a data exchange mechanism between multiple applications or multiple instances of the same application
See TSO either at CEN (European Committee for Standardization, WS/ISD "information System for Disaster and Emergency Management") or Afnor
General characteristics (size, coverage) of the vocabulary
Currently as tabular document, with some tens of tables. Some tables have tens of entries.
Language(s) in which the vocabulary is provided
Base definitions are in English.
2.5 URGENCY element This is a proposal, consistent with OASIS description of the civil protection domain. It is consistent with the CAP protocol v1.0 (cap.alertinfo.urgency.code). The code denotes the urgency of the subject event of the alert message. Acronym Level Definition IMMEDI Immediate Responsive action should be taken immediately EXPECT Expected Responsive action should be taken soon (within next hour) FUTURE Future Responsive action should be taken in the near future PAST Past Responsive action is no longer required UNKNWN Unknown Urgency not known
Machine-readable representation of the vocabulary
See on afnor site
Software applications used to create and/or maintain the vocabulary, features lacking for the case
Word has been used to edit the tables that describe the vocabulary.
Management of changes
The vocabulary is at an early stage of development, so there is no formal process.
Standards and guidelines considered during the design and construction of the vocabulary
The vocabulary inherits from the MIP initiative.
See also the vocabularies for C2IEDM at the NATO MIP site (http://www.mip-site.org/)