Search Results

This SAE Standard provides a table of textual messages meeting the requirements for expressing the names of street and roads and some basic building blocks for phrases commonly used in the ITS industry. The tables provided herein are taken from SAE J2369, and follow the rules of SAE J2540 and therefore allow a local representation in various different languages, media expressions, etc. to allow true international use of these phrases. The phrases are predominantly intended to provide a means to express street names including pre and post fixes ( North Oak Street is an example name with a prefix “North” and main portion “Oak” and a suffix “Street”). Other phrases exist for other specific specialty areas of ITS, and all such phrases follow a set of encoding and decoding rules outlined in SAE J2540 to ensure that the use of these phrases in messages remain interoperable between disparate types of user equipment.

This SAE Standard provides a table of textual messages meeting the requirements for expressing the names of street and roads and some basic building blocks for phrases commonly used in the ITS industry. The tables provided herein are taken from SAE J2369, and follow the rules of SAE J2540 and therefore allow a local representation in various different languages, media expressions, etc. to allow true international use of these phrases. The phrases are predominantly intended to provide a means to express street names including pre and post fixes ( North Oak Street is an example name with a prefix “North” and main portion “Oak” and a suffix “Street”). Other phrases exist for other specific specialty areas of ITS, and all such phrases follow a set of encoding and decoding rules outlined in SAE J2540 to ensure that the use of these phrases in messages remain interoperable between disparate types of user equipment.

This SAE Standard presents a set of rules for transforming an Abstract Syntax Notation (ASN.1) message set definition into an eXtensible Markup Language (XML) schema. The result is intended to be a stand-alone XML Schema that is fully consistent with an existing ASN.1 information model. This is a different goal from other related work by other standards bodies developing a set of XML encoding rules for ASN.1 or ASN.1 encodings for XML Schema. These rules were initially developed in order to produce an XML schema for the SAE ATIS standard. While other standards may also choose to use these rules, the rules may not be applicable for all environments. The goal for these transformation rules is twofold. The first goal is to provide a uniform set of such rules that all interested parties can use. The second goal is to use such rules to define an adopted schema for traveler information that reflects the preferred translation of ASN.1 message sets to XML for use by ITS system implementers.