1 This document establishes the requirement that ASN.1 shall be the normal syntax notation to be used in Standards in the TICS Sector, and to provide a common message form for such ASN.1 based data elements, such that reference to the relevant TICS ISO Standard may be achieved. This Standard provides guidance as to the usage of ASN.1 within the TICS Sector, and makes provision for other extant Standardised syntax notations (such as EDIFACT).
2 This document is designed to provide an 'enabling' structure for use in the TICS/RTTT sector. It enables users of ASN.1 structures to reference specific Standards wherein specific data messages (and their syntax notation) are determined. The use of a Standard form of notation is designed to allow interoperability between different commercial systems, and to allow migration of data to other systems, and to later generations of systems.
3 This standard notation provides methods of identification of the relevant Standard in which a TICS message, expressed in ASN.1 notation, is described, and thereby enables understanding and interpretation of the message.
4 Vision statement. This document envisions a low overhead and minimum maintenance means of identifying the Standard of all ASN.1 message structures in an interoperable environment within the TfCS Sector.
5 Mission statement. This document is to provide guidance to identify the relevant Standard wherein a particular ASN.1 message may be understood and used.
6 This document is procedural in nature affecting data presentation in ASN.1. As such it is concerned only with data architecture, and the whole content of the document falls into this category. Consideration of other architectural aspects as such, are therefore not appropriate in this document.
7 Specific implementation requirements, other than those determined in the syntax notations identified above, are beyond the scope of this document.
This document also provides a means where particular sector requirements, or existent Standards, that require particular message forms that have traditionally been expressed in other notations (e.g. EDIFACT), may be referenced, with the purpose of actual usage from a TICS Sector application. Thus it presents an unambiguous system for identifying all the different data types that, in such a way that it may easily be interpreted to/from other notations where appropriate.