SAE J2630_200312

1 Scope
2 References
3 Definitions
4 Rules for Converting an ASN.1 Message Set Definition to
  an XML Schema
  4.1 Defining a Simple Type in Terms of a Basic Type
  4.2 Defining Basic INTEGER Types
  4.3 Defining INTEGER Types with Minimum and Maximum Values
  4.4 Defining String Types of Minimum and Maximum Length
  4.5 Defining String Types of Fixed Length
  4.6 Defining ENUMERATED Types
  4.7 Defining a Type Definition Embedded in an Element
       Definition
  4.8 Defining a Complex Type as a SEQUENCE of Elements
  4.9 Defining a Complex Type as a CHOICE of Elements
  4.10 Defining a Complex Type as a SEQUENCE of Named Types
  4.11 Defining a Complex Type as a SEQUENCE of a Named Type
       with Minimum and Maximum Number of Elements
  4.12 Defining a Complex Type as a SEQUENCE of an Unnamed Type
  4.13 Defining Elements as Instances of Existing Basic Types
  4.14 Defining Elements as Instances of User-Defined Types
  4.15 Defining Elements as Instances of In-Line Defined Types
  4.16 Defining BIT STRING Elements
  4.17 Defining OCTET STRING Elements
  4.18 NULL Elements
  4.19 Object Identifier (OID) Elements
  4.20 General Elements
  4.21 Handling Comments
  4.22 Commonly Repeated Element
  4.23 Defining an Element of a Type Defined in a Different Schema
  4.24 Defining Top-Level Elements
  4.25 Beginning and Ending the Schema
5 Discussion of Selected Conversion Rules
  5.1 Methods of Defining ENUMERATED Elements
  5.2 Alternate Methods of Defining Mixtures of Text Strings and
       ENUMERATED Elements
  5.3 Alternate Method of Defining BIT STRINGs
  5.4 Treatment of IA5String Contents
  5.5 Treatment of OCTET STRINGs
  5.6 Treatment of Manual ASN.1 Tag
  5.7 Treatment of Long ASN.1 Names
  5.8 Treatment of ASN.1 Comments
  5.9 Use of XML Names spaces to Point to Types Defined in
       Other Standards
  5.10 Expressing the Resulting Schema in a Standard
6 New Types Defined for the SAE ATIS J2353/2354 Schema
  6.1 Binary Type
  6.2 OctetString Type
  6.3 NumericString Type
  6.4 BoundedString Type
  6.5 UndefinedElement Type
7 A Complete Example of the Rules in Use
8 BIBLIOGRAPHY
TABLES

Specifies set of rules for transforming an Abstract Syntax Notation (ASN.1) message set definition into an extensible Markup Language (XML) schema. Intended to be a stand-alone XML Schema that is fully consistent with an existing ASN.1 information model.

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. The first goal is met by this document. The second goal is met by employing this document to produce XML information as part of the periodic re-balloting of the SAE ATIS standard. This is a parallel standards effort with this document.2xThese rules were developed as part of the process to draft an XML version of the ATIS data element and message set standards. The original effort focused upon the needs found in the currently adopted October 2000 SAE J2354 standard for ATIS message sets. SAE J2354 makes extensive use of elements from the ITETMDD work and from ITE-TCIP work. In addition, the draft “Event Report Message” (ERM) portion of the Message Sets for External Traffic Management Center Communication (MS/ETMCC) standard was also examined and translated. Message and data elements from the IEEE Incident Management standard (IEEE 1512-2000) were also examined. By this effort, every major message set of ITS was considered to some degree to ensure that the resulting translations could be successfully employed by others toward a common result. It is intended that the resulting ATIS schema will be voted on as an SAE ATIS standard. Other standards-developing organizations may also choose to use these rules; however, it is recognized that translations may not be necessary in some environments and that these rules may not be applicable to all environments within ITS. It is left to each standards-development organization to make such determinations for their specific environments.Section 4 is the complete set of conversion rules. An example of use for each rule is given, showing an original ASN.1 definition, the resulting XML schema definition, and a sample XML document element where applicable.Section 5 of this document discusses the background of some non-obvious conversion rules presented in Section 4.2x These include methods of handling the XML representation of enumerations, octet strings, and bit strings. Section 5 also describes how XML namespaces can be used to point to types defined in the Traffic Management Data Dictionary (TMDD), the Transit Communications Interface Profiles (TCIP) standard, the Location Reference Message Set (LRMS), or the International Traveler Information Systems (ITIS) phrase lists. It also discusses additional translation refinements proposed for the conversion of the ATIS message standard.Some omissions in the SAE standards required new types to be defined in order to have a valid XML schema. In addition, some new types must be defined to implement the representation of octet strings and bit strings. These changes are documented in Section 6. In the currently adopted revision of the standard the use of inline definitions rather than the more proper use of formal Type Definitions is also a challenge for conversion.Section 6 also documents a number of common types that were defined globally at the start of the schema rather than being redefined identically, in-line multiple times in the schema.Section 7 presents a sizable sample ASN.1 definition and the corresponding XML schema. The sample illustrates a large number of the conversion rules.