3.2. Compliance
3.2.1. Definition
Compliance with the EUROCONTROL eAIP Specification 1.0.3 may be claimed for eAIP instances that:
.
are valid against the eAIP DTD 1.0.3 and
.
it follows the additional rules;
A software product may be declared compliant with the EUROCONTROL eAIP 1.0.3 Spe-cification if it can handle/produce/edit/etc. compliant eAIP documents.
3.2.2. How to check compliance
3.2.2.1. Formal validation
To formally validate an eAIP means to validate it against the official DTD published on EUROCONTROL's Web site, at the address defined in the Location section and then to check the eAIP for additional rules compliance.
3.2.2.2. Using MakeAIP
MakeAIP is a batch script provided within the eAIP package. It allows to check compliance to both the eAIP DTD and the additional rules. Please refer to the MakeAIP Documentation for more details. If MakeAIP is properly configured, typing MakeAIP validator will check compliance to the DTD and report any error; then it will automatically run MakeAIP schematron, which is described below. The Validator will not explicitly report compliance.
Note that MakeAIP validates an eAIP against the DTD declared in the eAIP itself, which is generally a local copy of the DTD.
3.2.2.3. Interactive validation
Most XML editing software are able to validate an eAIP against its DTD, but not against the additional rules. Therefore, the eAIP package includes an interactive tool, based on Schematron, which is able to list additional rules validation errors. To use it, follow these 2 steps:
1.
Run MakeAIP schematron
2.
Open or reload the file ../../tools/Validator/schematron-frame.html
This tool shows the list of errors in the upper part of the browser window and the whole XML source of your eAIP in the bottom part. When you click on an error, the bottom part is scrolled to the place where the error occurs. Each error is presented with a link to the eAIP Specifica-tion, precisely to the rule related to the error.
To see how such a report looks like, please see the eAIP Specimen's additional rules validation report [../../tools/Validator/schematron-frame.html]. When downloading the eAIP package, it is necessary to generate that report for the first time: open a command-prompt window, change directory to where the eAIP package is installed and type MakeAIP schematron. The eAIP Specimen contains a lot of errors with respect to the additional rules; most of them are there to check the validation process.
3.2.3. File formats
As the baseline, the eAIP should be published in three formats: XML, HTML (for browsing) and PDF (for printing). The compliance can be formally checked only for the XML format.
Through the use of the Extensible Markup Language (XML), the eAIP data content is com-pletely separated from presentation, which, in turn, may be tailored to every target media. While the capability to fine-tune the eAIP presentation for every media (paper, CD-ROM, Web, etc.) is an advantage for the users, it is also a challenge for the producers. They must ensure the consistency between the different formats. Most likely, the reference format is XML. However, depending on the legislation in force in the issuing State and/or the user's State, it might be that another format (for example PDF or the paper document) is declared as the reference format. This is important in case of discrepancies between the different formats. The producer shall clearly state which of the different formats should be con-sidered as prevailing in case of discrepancies.
3.3. eAIP Specification
The eAIP Specification is composed of a DTD and "additional rules".
The stylesheets used for converting XML into HTML, which complement the specification, are not imposed. However, the eAIP user community expects uniformity in the layout and navigation structure of all eAIP implementations. This can be achieved through a consistent application of the EUROCONTROL eAIP stylesheets.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：Electronic AIP Specification(6)
