Update Definitions page to include the different types of data sets. This can be a note in the ICAO data set entry.
|The obstacle data set has different requirements from the others so needs to be defined on its own.||Implemented|
The different metadata requirements can be found at Basic properties for obstacles.
Discussed 16 July and no objections raised.
|2||Change wording of DS-META-007 - Geographical extent of the data set on Metadata Requirements|
Reword the requirement into two clauses:
The new wording will be reflected on DS-META-007 - Geographical extent of the data set.
The obstacle data set makes "Area of coverage" mandatory.
The tidy up of the table will ensure it is inline with the requirement/recommendation.
|Implemented||Discussed 16 July and no objections raised.|
|3||Change the list of geographical elements to include.|
The introduction on DS-META-007 - Geographical extent of the data set should become:
The Obligation / Condition row in tables should become:
|Reflects decision to concentrate on the provision of GeographicalDescription but allow the provision of other elements if available.||Implemented||Discussed 16 July. Proposal updated to reflect the outcomes.|
New requirement for obstacle data sets covering integrity.
Add definition to Definitions:
Add new requirement to Minimal Metadata Requirements:
Add dedicated page with guidance. The table will use lineage. Of note:
When adding the lineage statement state whether critical, essential or routine data integrity level is assured.
Update Appendix B_ Complete Informative Example to reflect the guidance.
|See Basic properties for obstacles.|
Discussed 16 July. Proposal updated to reflect the outcomes.
See notes below. Decision was to use lineage and the levels (critical, essential, routine) to fulfill the requirement. Obstacle data is routine so that is used in the guidance.
|5||Rename DS-META-007 - Geographical extent of the data set, etc.|
The page name should be updated to e.g. DS-META-007 - Geographical extent of the data set.
This change should be applied to all the individual requirements pages.
|The word "requirement" can be misleading. It is better simply to use the identifier.||Implemented||Discussed 16 July and no objections raised.|
|6||Update Appendix A_ Requirements Analysis to reflect final version of Annex 15 and PANS-AIM||Check the paragraph numbers used. Add the obstacle data set metadata requirements. Updated numbers should be reflected on Minimal Metadata Requirements as well.||Mostly tidy up.||Implemented||Discussed 16 July and no objections raised.|
|7||Update trace for DS-META-007 - Geographical extent of the data set on the Metadata Requirements page.||The requirement is traceable to PANS-AIM Table A6-2. Obstacle attributes for the obstacle data sets||The obstacle data set makes "Area of coverage" mandatory.||Implemented||Discussed 16 July and no objections raised.|
|8||Update guidance on|
Add guidance to clarify what is meant by validity in this case.
|Implemented||Discussed 16 July. Proposal updated to reflect the outcomes.|
|9||Change the order of the two examples on DS-META-003 - Validity of the data set||Change the order of the examples as the "End date unknown" is the more usual case.||Implemented||Implemented without discussion as has no impact on anything else.|
|10||Add DS-META-000 - How to Provide Metadata to Metadata Requirements list||Add DS-META-000 - How to Provide Metadata to the Metadata Requirements page as it is currently not listed there.||We should not have a requirement that is not listed on the Metadata Requirements page.||Implemented|
|11||Add link to the obstacle requirements on the main page.||Implemented|
|12||Integrate the obstacle data set requirements|
The following pages were added:
changes were made to integrate the obstacle metadata to
content came from [for deletion] Obstacle metadata requirements
|Bringing all of the metadata requirements into one place to make easier to manage and understand||Implemented||Implementation will be explained on 13 April 2021|