 |
 |
 |
 |
|
 |
 |
ITIS Phrase Tables, Draft [issued: 04-11-09]
-
10 -
This is a draft document of the SAE ATIS committee, subject to change.
Textual Use: The ERM message definition allows free text to be used at any point in the description, along
with standards-defined phrases, causes, advice and quantities. However, this text is placed in the data
element assigned to hold it and not inserted into other locations.
Language: The language of free text occurring in the ERM message is typically defined in an Interchange
Agreement - a working agreement drawn up between message exchange partners. Partners can agree to use
English, French, Spanish, or any other language of their choice for routine exchanges. If desired, the
language of the free text can also be indicated for a specific message exchange using optional TMDD Data
Element #3816 within ERM. Typically, this is used if the normally agreed upon language must be
changed in a specific message. Text occurring in the rest of the ERM message is presumed to be of table
type #0. This is a reserved type which implies that the text will be formatted in Latin_1 characters and
employ no indexing (e.g. simple free text).
Table Types: The ERM message definition presumes that the table entries are static in nature and that
entries are never reused. This is reflected in the table header values outlined further in this document.
Local Use: ERM allows the standard ITIS phrases to be varied or translated for local applications, e.g.
"traffic stopped" can be expressed as "stationary traffic" or "bouchon" if desired in Nova Scotia or Quebec.
Like all users of these phrases, makers of ERM message receiving equipment are free to express these
tables in whatever rendering, language, or media formats suit their specific needs. Within this, local
additions to the table MAY still be added as required and SHALL occupy ranges between 129 and 250 in
the various tables. This will be in accordance with the rules of J2540
5
for local list additions, as well as not
violating the specifications of TMDD.
Supporting Messages: Implementers SHOULD also implement the messages of SAE J2540 which support
the automatically downloading, updating and translations of table and table entries to users.
Like all users of these phrases, makers of ERM message receiving equipment are free to express these
tables in whatever rendering, language, or media formats suit their specific needs.
5.4
Use in the IEEE Incident Management Message Set
The IEEE has developed an ITS message set for use between the dispatch centers of agencies responding to
various incidents. This standard makes a very heavy reuse of date elements found in the rest of ITS
(including TMDD and SAE lists which were effected by the harmonization of the ITIS lists). The
standard has been forced to adopt since being issued (as 1512-2000) to reflect further changes in ITS
harmonization. Implementers must refer to the (as yet not balloted) changes document for the definitive
information regarding the use of ITIS and other code list changes made to this standard. Some
implementation insights are provided below.
In general the adoption of ITIS phrases in 1512-2000 can be classed into two types of use. The first, where
formerly free text was used for various descriptions is very must like the changes found in SAE ATIS and
other standards. The full feature set of J2540 is employed and a mixture of both free text and index values
can be found in the resulting ASN1 element. In the second case, various subsets of the event types where
used to clarify and sort the type of event being used. In this instance a subset of ITIS phrases is in general
used (while free text is prohibited).
Precedence:
The ASN1 found in the adopted IEEE 1512-2000 and its anticipated updated
recommendation standard is the definitive authority for the structure of 1512 messages.
5
SAE J2540 provides ways to do this with varying degrees of formality. One can simply pick a
new table number and add whatever is wanted in the least "registered" case, while other ranges of use
provide for national and regional registry control to occur.