Appendix A_ Requirements Analysis

ICAO Annex 15 Obligations
This section details the analysis of the metadata obligations of ICAO Annex 15. Analysis shows different concerns addressed by the obligations. These are:

Obligations concerning data collection
Obligations concerning the verification of data collected
Obligations concerning the metadata to be provided
Other obligations
Obligations on the standards to be used for describing metadata

The following tables group the obligations according to these concerns. Emphasis is added to make clear the issues to be addressed by the obligation. Note that some obligations are repeated as they apply to different concerns.
Obligations for data collection

Identifier	Text	Source
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4f4a5a49-eaca-4fde-931b-af860d1bc931"><ac:plain-text-body><![CDATA[	4.2.1	Metadata shall be collected for aeronautical data processes and exchange points.	[1]	]]></ac:plain-text-body></ac:structured-macro>
4.2.2	Metadata collection shall be applied throughout the aeronautical information data chain, from origination to distribution to the next intended user. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="30331216-8845-4431-9ce4-3953e17341fd"><ac:plain-text-body><![CDATA[Note. — Detailed specifications concerning metadata are contained in the PANS-AIM (Doc 10066).	[1]	]]></ac:plain-text-body></ac:structured-macro>
1.2.3.2	When a different temporal reference system is used for some applications, the feature catalogue, or the metadata associated with an application schema or a data set, as appropriate, shall include either a description of that system or a citation for a document that describes that temporal reference system. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1a5336d5-0a5e-40de-9166-a26c457157df"><ac:plain-text-body><![CDATA[Note.— ISO Standard 19108, Annex D, describes some aspects of calendars that may have to be considered in such a description.*	[1]	]]></ac:plain-text-body></ac:structured-macro>
4.2.1	The metadata to be collected shall include, as a minimum: a) the name of the organizations or entities performing any action of originating, transmitting or manipulating the data; b) the action performed; and c) the date and time the action was performed. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="860b3d1a-8281-400a-86a3-0525ec2b2b0f"><ac:plain-text-body><![CDATA[Note.— ISO Standard 19115 specifies requirements for geographic information metadata.	[2]	]]></ac:plain-text-body></ac:structured-macro>
2.1.1.2	A record of data originators should be maintained. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1e8b8284-397b-4080-8f6c-52d17cea3bf8"><ac:plain-text-body><![CDATA[Note.— Metadata requirements in Chapter 4 specify which information is to be recorded for each originator.	[2]	]]></ac:plain-text-body></ac:structured-macro>

Obligations for verification of data collected

Identifier	Text	Source
2.1.2.1	Collected data shall be verified and validated for compliance with completeness, format, timeliness, traceability and data quality requirements. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="99b769c2-da27-4b6e-a2ad-1fcffde789d3"><ac:plain-text-body><![CDATA[Note 1.— Appendix 1 contains aeronautical data attributes, metadata, and accuracy requirements.	[2]	]]></ac:plain-text-body></ac:structured-macro>

Obligations for data provision

Identifier	Text	Source
5.3.1.2	Each data set shall be provided to the next intended user together with a minimum set of metadata that ensures data traceability from the end-user to the originator. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="63fa17a3-baf7-417d-8505-b4a17ae0294d"><ac:plain-text-body><![CDATA[Note.— Detailed specifications concerning metadata are contained in the PANS-AIM (Doc 10066).	[1]	]]></ac:plain-text-body></ac:structured-macro>
1.2.3.2	When a different temporal reference system is used for some applications, the feature catalogue, or the metadata associated with an application schema or a data set, as appropriate, shall include either a description of that system or a citation for a document that describes that temporal reference system. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b18f3b18-4f30-4109-9959-ae857791ca1c"><ac:plain-text-body><![CDATA[Note.— ISO Standard 19108, Annex D, describes some aspects of calendars that may have to be considered in such a description.*	[1]	]]></ac:plain-text-body></ac:structured-macro>
5.3.2.1	Each data set shall include the following minimum set of metadata: a) the name of the organizations or entities providing the data set; b) the date and time when the data set was provided; c) validity of the data set; and <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="386cf4ad-1136-487d-8188-088224293d7e"><ac:plain-text-body><![CDATA[d) any limitations with regard to the use of the data set.	[2]	]]></ac:plain-text-body></ac:structured-macro>

Other obligations

Identifier	Text	Source
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="70f8760f-4f59-4ef4-a7bf-17d8304fceee"><ac:plain-text-body><![CDATA[	3.6.5	Each quality management system shall include the necessary policies, processes and procedures, including those for the use of metadata, to ensure and verify that aeronautical data is traceable throughout the aeronautical information data chain so as to allow any data anomalies or errors detected in use to be identified by root cause, corrected and communicated to affected users.	[1]	]]></ac:plain-text-body></ac:structured-macro>
5.3.1.2	A description of the available digital data sets shall be provided in the form of data product specifications on which basis air navigation users will be able to evaluate the products and determine whether they fulfil the requirements for their intended use (application). Note 1.— ISO Standard 19131 outlines the specifications of geographic data products. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0625bff1-eb0a-4d9e-a2fa-106c4f9332cb"><ac:plain-text-body><![CDATA[Note 2.— This may include an overview, specification scope, data product identification, data content and structure, reference system, data quality, data capture, data maintenance, data portrayal, data product delivery, additional information, and metadata.	[2]	]]></ac:plain-text-body></ac:structured-macro>
5.3.1.4	The aeronautical information model used should: … c) include provisions for metadata as specified in 5.3.2; and <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1300be57-ec35-4498-bf6f-7e9658c16f42"><ac:plain-text-body><![CDATA[…	[2]	]]></ac:plain-text-body></ac:structured-macro>

Obligation on the standards to use

Identifier	Text	Source
5.3.1.1	The ISO 19100 series of standards for geographic information shall be used as a reference framework. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="316d951c-1882-460b-aba9-6b884e806806"><ac:plain-text-body><![CDATA[Note.— This is intended to facilitate and support the use and exchange of digital data sets between data providers and data users.	[2]	]]></ac:plain-text-body></ac:structured-macro>

Other Metadata Requirements Analysis
This section lists a number of other requirements which were considered in addition to those found in Annex 15. They were collected from the AIM community.

Data protection – The metadata exchanged should not allow for an individual to be identified. The preference is therefore to exchange organisation and role names.
There are proposed interoperability rules:
1. [Rule] The start of validity of a data set shall be clearly indicated through metadata.
2. [Rule] An AIP Data Set that included changes under the AIRAC system shall be clearly identified through the use of the acronym "AIRAC" in the metadata.
Some further requirements (taken from the PowerPoint which introduced the need for metadata):
1. Accuracy, resolution and integrity

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.