 |
 |
 |
 |
|
 |
 |
ITIS Phrase Tables, Draft [issued: 04-11-09]
-
14 -
This is a draft document of the SAE ATIS committee, subject to change.
49
Small Numbers
50
States And Territories
51
Structures
52
Street Suffixes
53
MUTCD Locations
* Allowed to be an event type
SAE Editor: a 2-colum layout when done!
Table 1 – (Revised) Suggested Table Organization and Ordering
5.6
Formats of tables
The tables are presented as a non-nested set of tables. Common American English textual expressions are
used throughout. All strings are made up of "simple text" formatting.
Observe that the type of table entries has been preserved in a grouping which matches that used by portions
of TMDD and other ITS message sets. For example, those message phrases dealing with types of disasters
are all arranged to be within the range [0x0C01 to 0x0CFF]. These range encodings will be preserved and
implementers MAY use them for sorting purposes. If local phrases are to be added, they SHOULD
preserve these ranges insofar as possible.
Table nesting has not been used for simplicity. Some saving in memory space can be obtained at the
expense of more complex table expansion processing which can be obtained by this method. If
implementers wish to create such a nested table for textual reasons, they MAY wish to build it in two
stages to preserve the ability to perform range sorting.
5.7
Supported vocabularies and alphabets
The tables are expressed in the ASCII character set. As no diacritical marks are used, there was no need to
use the Latin_1 character sets or Unicode.
Example software algorithms to convert into and out of the modified ASCII character set can be found in
SAE J2369 Sections 10 & 11.
5.8
Registering a table within ITS
The presented tables are registered as per J2540 as tables for national use, when required.
Implementers wishing to further modify these entries (for example adding a new entry they feel is needed)
SHALL follow the procedures outlined in J2540 Section 5.7 & 5.8 and create such a table in the
registration range appropriate for their use. It is recommended that such tables nest to the tables presented
here rather than duplicate the information in a flat table of their own creation.
Most deployments will have no need to register unique tables of their own creation and can use the method
of local codes to add any additional table entries needed.