ARINC 814-1 PDF

Scope of Document

This document defines an open binary encoding format for XML content. This format, when designed and implemented, will enable quick, economic, and efficient use of XML in avionics for uses ranging from loadable databases to data messaging between systems. The standard serves as a support document for applicationspecific data standards.

Specific XML schemas are not addressed in this standard. Application-specific schemas, formats, and content requirements are described elsewhere. ARINC Specification 814 is designed to be used for any XML content, but was primarily driven by the following uses:

• XML based database formats, for example:

o ARINC Specification 813: Embedded Interchange Format for Terrain Databases

o ARINC Specification 815: Embedded Interchange Format for Obstacle Databases

o ARINC Specification 816: Embedded Interchange Format for Airport Mapping Database

• XML based protocols (air-ground), for example:

o ARINC Specification 830: Aircraft/Ground Information Exchange (AGIE) Using Internet Protocols

o ARINC Specification 834: Aircraft Data Interface Function (ADIF)

• XML based messaging between Aircraft Systems, for example, Aeronautical Operational Control (AOC) messages

o ARINC Specification 633: AOC Air-Ground Data and Message Exchange Format

Since industry does not require applications using the above specifications to be standardized, data interpretation is not addressed in this document (e.g., how one uses ARINC 816 data for an airport map application is left to implementation details).

This specification does not require the use of a centralized database server; however, the concept of such a server and/or System Wide Information Management (SWIM) architectures weighed heavily in the development of this standard. When applicable, provisions have been made to enable use of XML Encoding and Compression with an aeronautical database server for both future and existing databases (e.g., Terrain, Airport, Performance, Navigation, Obstacle, and Configuration databases of any kind).

The foundation of the XML Encoding format is the OGC BXML Encoding Specification. The OGC BXML design has been optimized and extended to support the use cases identified above.

In addition, this specification has been designed to be extensible for new data types, metadata, and indexing approaches. For example, geospatial indexing is necessary for efficient use of terrain and obstacle data sets. In addition to BXML encoding, this standard covers the use of compression on BMXL encoded data. While compression is not required for ARINC 814 data, it is the only compression technique supported for ARINC 814 compliant data. It is assumed that any content compressed must be decompressed before being processed as BXML data.

In some cases, the ARINC 814 format chose simplicity and compactness over flexibility. Therefore, the ability to preserve XML formatting like whitespace and comments is not available. However, in cases directly related to data content, flexibility and robustness were major considerations, as manifested in the capabilities provided by string tables, indexing, and binary large object (blob) support.

This document does not address packaging (e.g., ARINC 665 for data load content) or integrity methods such as digital signatures or Cyclic Redundancy Checks (CRCs). Rather, it is assumed that other standards which define the specific XML content and schema address these topics. ARINC Specification 814 was designed to support various methods loading or distribution methods, such as delta or short loading.

Appendix B defines an approach for providing optional ARINC 814 encoding instructions and guidance within an XML schema definition (XSD).