曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
5.2. Embedded versus not embedded graphics
The eAIP Specification supports three different ways of referencing a graphic file in an AIP: fully embedded, embedded in paper only or external. In this context, an embedded graphic is a graphic file whose image is directly visible on the page, between two paragraphs, for in-stance. A graphic file which is not embedded is not visible until the user performs some action, such as clicking on a link in HTML.
Fully embedded graphic Such a graphic file is directly visible both in HTML format and on paper. It is part of the text flow. Typical examples are small diagrams included in the GEN part.
Paper embedded graphic The image is not embedded in HTML and other on-screen presentation formats; a link to the image is presented instead. The image is embedded in XSL-FO format and deriv-atives (PDF, PostScript, etc.) so that the image still appears on paper, but it is embedded in a separate page, after the last page of the current section (or the current aerodrome or heliport). Typical examples are ENR and AD 2.
External graphic Rarely used, it is presented as a Web link to the graphic in HTML (the user must follow the link in order to access the image). On paper, the link is visible (i.e. the graphic address on the Web is printed), but of course not click-able. In PDF format, the link may be click-able, just like in HTML. Typical examples are addresses of the Web pages of an organ-isation/authority.
Chapter 6. eAIP Amendments
6.1. Introduction
The ICAO Annex 15 requirements for AIP amendments are fully suported by the eAIP Spe-cification. When the eAIP is presented on-screen, in HTML format, every individual change can be clearly highlighted. Further more, it is possible to compare the current (modified) content with the previous content. When an eAIP is printed, in PDF format, change bars are inserted on all affected lines within the document.
Paper AIPs are kept up-to-date by removing/inserting pages at every amendment date (AIRAC and non-AIRAC). These pages are issued in the form of an AIP Amendment (AMDT) docu-ment. The concept of 'replacement pages' does not apply to an Electronic AIP, which is re-issued in full at every amendment date. However, in order to facilitate the maintenance of a paper AIP, it is also possible to identify the pages that have been affected by the changes between two consecutive issues of the AIP in PDF format.
6.2. Document Type Definition aspects
In order to support amendments, a dedicated set of XML elements and attributes have been included into the eAIP Document Type Definition (DTD). For example, new text is marked using an Inserted element, while deleted text is marked using a Deleted element. There is no special element for modified text. Instead, modified text is marked as a sequence of Insertedand Deletedelements.
There are also DTD elements, which do not have in-line text content, such as a references, graphics, etc.. An Updated attribute, which may take the values Insertedor Deleted is used in this case. The old element will get the value Deleted in its Updated attribute and a new element of the same type will be inserted, with the new content.
Details about how the content of each individual DTD element may be amended have been included into the DTD Documentation.
6.3. Procedures
6.3.1. Old changes
Each eAIP issue contains markup (Insertedand Deleted XML elements and attributes) only for the changes made in that issue. Eventually, if that eAIP issue corresponds to an AIRAC amendment, the changes of the previous non-AIRAC amendment can be kept (and vice-versa).
There are a few reasons behind the decision to remove the old changes in XML. If old inserted and deleted elements were kept, then:
.
the XML eAIP files might soon become very complex and even invalid, due to clashes between current and previous Insertedand Deletedelements; at one moment, some of the old amendment markup would need anyhow to be deleted for the content to become again understandable;
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
Electronic AIP Specification(13)
