Page Comparison

In order to ensure data protection, the metadata exchanged should not allow for an individual to be identified. The preference is therefore to exchange organisation and role names.

Note: This was reflected in the implementing instructions for Requirement 1.

(Rule)The start of validity of a data set shall be clearly indicated through metadata.

Note: This was captured in Requirement 3.

(Rule) An AIP Data Set that included includes changes under the AIRAC system shall be clearly identified through the use of the acronym "AIRAC" in the metadata.

Note: This was captured in Requirement 4.

Note: Justification for this requirement comes from various parts of ICAO Annex 15:

• 5.3.2.1 Recommendation.— An AIP data set should be provided covering the extent of information as provided in the AIP.
• 6.2.1 Information concerning the following circumstances shall be distributed under the regulated system (AIRAC) <...>
• 6.3.1.1 AIP shall be amended or reissued at such regular intervals as may be necessary to keep them up to date.
• 6.3.3.1 Data sets shall be amended or reissued at such regular intervals as may be necessary to keep them up to date.
• 6.3.3.5 Updates to AIP, AIP data sets and Instrument Flight Procedures data sets shall be synchronised.

1. Accuracy, resolution and integrity

Note: After analysis it was decided not to include requirements for the provision of the metadata with regards to the accuracy, resolution and integrity of the data. The measurement of these is part of the "verification of data collected" and is not metadata to be included at the dataset level.