Electronic AIP Specification(9)

曝光台 注意防骗 网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者

Amendments attributes Elements, whose Updated attribute has a value different than "No", must have an id and an Updated-ref attributes
Nested amendments Amendments may not be nested. This means that any element whose Updated attribute is different than "No" may not have a descendant whose Updated attribute is different than "No".
NIL If a NIL element has following sibling(s), it must have its Updated attribute set to Inserted or Deleted and they must have it set to the opposite.
3.3.2.2.2. Data Consistency Rules
ToC and id An element whose Toc attribute is set to "Yes" must have an id attribute.
MIME types The Type attribute of Graphic-file elements must contain a "known" MIME type. The list of known MIME types is given in XML format in the file mime-types.xml (in directory tools/Validator in the eAIP package). All eAIP software implementation must be able to handle these MIME types.
Graphics and paper AIP If the xlink:show attribute on e:Graphic-file is set to "replace" or "new", then attribute Page-name must not be empty.
Internal links Internal links (x:a elements with a href attribute value beginning with "#") must point to an existing element. That is, the value after the "#" character must be the id of an element in the same eAIP document.
Internal References Internal references must refer to an existing element, depending on the referrer:
.
An Abbreviation must refer to an Abbreviation-description;

.
A Location must refer to a Location-definition

.
A Significant-point-reference must refer to a Navaid or a Designated-point

.
A Significant-point-remark-reference must refer to a Significant-point-remark

.
A Route-segment-usage-reference must refer to a Route-segment-usage

.
A Route-segment-remark-reference must refer to a Route-segment-remark

.
An Aerodrome must refer to a Location-definition

.
A Heliport must refer to a Location-definition

.
The Updated-ref attribute must refer to an Amendment

Significant-point-ATC Legal values are: "Request", "Compulsory" and "No-report" and they must be expressed inside a single text node. These values can be inside child elements (typically e:Deleted and e:Inserted), but no other text is allowed. Text inside e:Deleted elements is not con-sidered for this rule (as it must have been valid before the amendment).
Route-segment-usage-direction Legal values are: "Forwards" and "Backwards". These values can be inside child elements (typically e:Deleted and e:Inserted), but no other text is allowed. Text inside e:Deleted elements is not considered for this rule (as it must have been valid before the amendment).
Route-segment-usage-level-type Legal values are: "Odd" and "Even". These values can be inside child elements (typically e:Deleted and e:Inserted), but no other text is allowed. Text inside e:Deleted elements is not considered for this rule (as it must have been valid before the amendment).
Location-name
Location-name must not be empty.

Location-ident Location-ident must exist and not be empty if its parent Location-definition's Type attribute is set to "ICAO".
3.3.2.2.3. Data types Rules
Column width
The width attribute of x:col element must be a positive integer.

Dates Effective-date and Publication-date attributes' value must be an ISO-8601 date without time zone information.
3.3.2.3. Optional Rules
Route segment usage and track If a route segment has at least one child Route-segment-usage-reference of value "For-wards" (respectively, "Backwards"), then the route segment should have a Route-segment-true-track (resp. Route-segment-reverse-true-track) or a Route-segment-mag-track (resp. Route-segment-reverse-mag-track) element.
　
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：Electronic AIP Specification(9)