AIXM 5 Metadata

Requirements for AIXM Metadata AIXM Metadata Model Examples Requirements for AIXM Metadata AIXM Metadata Model Examples

Metadata Metadata is structured information about data It provides information about a particular dataset, which can be a message or a single feature –the origin of the data, the citation for the resources, an abstract, the purposes, credits, the status and points of contact Metadata is structured information about data It provides information about a particular dataset, which can be a message or a single feature –the origin of the data, the citation for the resources, an abstract, the purposes, credits, the status and points of contact

AIXM Requirements AIXM has two high-level requirements: –Compliance with the ISO series –Coverage for AIXM specific needs CRC Integrity AIXM has two high-level requirements: –Compliance with the ISO series –Coverage for AIXM specific needs CRC Integrity

Main Sources International Standardization Organization (ISO) –19115 (Geographic information – Metadata) and Corrigendum –19139 (Geographic information – Metadata – XML Schema Implementation) ISO = XML Schema based encoding for ISO metadata Defines geographic metadata XML encoding (gmdXML) International Standardization Organization (ISO) –19115 (Geographic information – Metadata) and Corrigendum –19139 (Geographic information – Metadata – XML Schema Implementation) ISO = XML Schema based encoding for ISO metadata Defines geographic metadata XML encoding (gmdXML)

Main Sources ISO UML model online: ISO schema available at: ISO UML model online: ISO schema available at:

Suitability of ISO ISO defines over 400 metadata elements Answers: –Does a dataset on a specific topic exist (‘what’)? –For a specific location (‘where’)? –For a specific date or period (‘when’)? –A point of contact to learn more about or order the dataset (‘who’)? Describes metadata for catalogue services, rather than for recurrent messages (e.g. AIXM messages) ISO defines over 400 metadata elements Answers: –Does a dataset on a specific topic exist (‘what’)? –For a specific location (‘where’)? –For a specific date or period (‘when’)? –A point of contact to learn more about or order the dataset (‘who’)? Describes metadata for catalogue services, rather than for recurrent messages (e.g. AIXM messages)

Requirements for AIXM Metadata AIXM Metadata Model Examples Requirements for AIXM Metadata AIXM Metadata Model Examples

AIXM Metadata Model AIXM metadata model is based on ISO19115 However, it is not intended to be a substitution for ISO It does not completely conform to ISO19115 AIXM metadata model is based on ISO19115 However, it is not intended to be a substitution for ISO It does not completely conform to ISO19115

Differences The AIXM metadata model: –Does not include topic category as mandatory –Includes extended metadata elements required to describe aeronautical information exchange data The AIXM metadata model: –Does not include topic category as mandatory –Includes extended metadata elements required to describe aeronautical information exchange data

Metadata Layers The AIXM Metadata model provides Metadata at three levels: –For the entire dataset or package, i.e. AIXM message –For each feature within a message –For each timeslice within a feature The AIXM Metadata model provides Metadata at three levels: –For the entire dataset or package, i.e. AIXM message –For each feature within a message –For each timeslice within a feature

Metadata Layers

AIXM Metadata Profile The profile has 6 models: –1. Metadata for the AIXM message –2. Metadata for an AIXM feature –3. Metadata for an AIXM feature timeslice –4. Constraint information –5. Citation and Responsible Party information –6. Data Quality information The profile has 6 models: –1. Metadata for the AIXM message –2. Metadata for an AIXM feature –3. Metadata for an AIXM feature timeslice –4. Constraint information –5. Citation and Responsible Party information –6. Data Quality information

Metadata to Include with AIXM Message The classes named using prefix MD or CI or DQ indicate inclusion of, or association with, ISO19115 classes

New Metadata Elements cyclicRedundancyCheckMessage is the value or string of alphanumeric characters usually generated by a cyclic redundancy check (CRC) algorithm. –Best practice recommends that the algorithm consider all tags and data elements within the feature data –When the data receiver applies the CRC algorithm to the feature data, a different CRC indicates that a tag or data element within the feature data has been changed since the sender generated the original CRC noteCRCMessage provides the ability to relay information to the data receiver if necessary about the CRC calculation –Using this data element, the sender can document the tags and data elements considered in the cyclic redundancy check cyclicRedundancyCheckMessage is the value or string of alphanumeric characters usually generated by a cyclic redundancy check (CRC) algorithm. –Best practice recommends that the algorithm consider all tags and data elements within the feature data –When the data receiver applies the CRC algorithm to the feature data, a different CRC indicates that a tag or data element within the feature data has been changed since the sender generated the original CRC noteCRCMessage provides the ability to relay information to the data receiver if necessary about the CRC calculation –Using this data element, the sender can document the tags and data elements considered in the cyclic redundancy check

Modified Metadata Elements The IdentificationMessage outlines the elements to include as it pertains to the data in the AIXM message The relationships with MD_Identification is labelled restriction since the AIXM class is a subset of and/or includes varied attributes IdentificationMessage and MessageMetadata are related to MD_Constraints The IdentificationMessage outlines the elements to include as it pertains to the data in the AIXM message The relationships with MD_Identification is labelled restriction since the AIXM class is a subset of and/or includes varied attributes IdentificationMessage and MessageMetadata are related to MD_Constraints

Constraint Information Metadata

New Constraint Roles Constraints manage the rights to information including restrictions on access and use. messageConstraintInfo describes the constraints –If any of the features within the message have attributes with classification codes such as restricted, confidential, top secret, etc., the classification code for the feature captures the highest classification code among the attributes –messageConstraintInfo captures the highest classification code among the features metadataConstraintInfo describes any restrictions on the access and use of the metadata for the AIXM message –Classification code for this role is determined by the sender or data producer Both are similar to the role metadataConstraints relating MD_Metadata to MD_Constraints in ISO19115 Constraints manage the rights to information including restrictions on access and use. messageConstraintInfo describes the constraints –If any of the features within the message have attributes with classification codes such as restricted, confidential, top secret, etc., the classification code for the feature captures the highest classification code among the attributes –messageConstraintInfo captures the highest classification code among the features metadataConstraintInfo describes any restrictions on the access and use of the metadata for the AIXM message –Classification code for this role is determined by the sender or data producer Both are similar to the role metadataConstraints relating MD_Metadata to MD_Constraints in ISO19115

Metadata to Include About an AIXM Feature Similar to metadata on a Message: –cyclicRedundancyCheckFeature –noteCRCFeature Similar to metadata on a Message: –cyclicRedundancyCheckFeature –noteCRCFeature

Metadata to Include About an AIXM Feature Timeslice

Metadata Elements The FeatureTimeSliceMetadata class includes elements: –to reference the party responsible for the metadata information –the date on which the metadata was compiled. FeatureTimeSliceMetadata contains five new metadata elements not defined in ISO19115: –measureClass –measEquipClass –dataIntegrity –horizontalResolution –verticalResolution The FeatureTimeSliceMetadata class includes elements: –to reference the party responsible for the metadata information –the date on which the metadata was compiled. FeatureTimeSliceMetadata contains five new metadata elements not defined in ISO19115: –measureClass –measEquipClass –dataIntegrity –horizontalResolution –verticalResolution

Citation and Responsible Party Information Metadata

Similar to ISO19115 Describes authoritative reference information ResponsibleParty is essentially the same as ISO19115 CI_ResponsibleParty –except two new data elements: systemName as a place to describe the responsible system, i.e., database or repository digitalCertificate, a field to capture an electronic signature authentication information –contactInfo is associated with Contact not CI_Contact The Contact class differs from ISO19115 CI_Contact class. –address is the same as in ISO19115 which maps to the CI_Address class –phone maps to the class Telephone not to CI_Telephone Describes authoritative reference information ResponsibleParty is essentially the same as ISO19115 CI_ResponsibleParty –except two new data elements: systemName as a place to describe the responsible system, i.e., database or repository digitalCertificate, a field to capture an electronic signature authentication information –contactInfo is associated with Contact not CI_Contact The Contact class differs from ISO19115 CI_Contact class. –address is the same as in ISO19115 which maps to the CI_Address class –phone maps to the class Telephone not to CI_Telephone

Data Quality Information Metadata

Description Describes the quality of data within a feature timeslice. The quality of data may vary by attribute or set of attributes. –ISO19115 data element attributes is used to list the attributes to which the report applies. report maps to class DataQualityElement associated with DQ_Element which contains –ISO19115 elements evaluationMethodDescription and pass. –a new metadata element evaluationMethodName giving the name of the evaluation method used on the given attributes (AirMAT-AICM metadata harmonization) Describes the quality of data within a feature timeslice. The quality of data may vary by attribute or set of attributes. –ISO19115 data element attributes is used to list the attributes to which the report applies. report maps to class DataQualityElement associated with DQ_Element which contains –ISO19115 elements evaluationMethodDescription and pass. –a new metadata element evaluationMethodName giving the name of the evaluation method used on the given attributes (AirMAT-AICM metadata harmonization)

Requirements for AIXM Metadata AIXM Metadata Model Examples Requirements for AIXM Metadata AIXM Metadata Model Examples

Optional It is optional to include metadata within an AIXM message or feature timeslice If it is included, it should conform to the profile Metadata can be easily captured and it is highly recommended that it be sent with an AIXM message It is optional to include metadata within an AIXM message or feature timeslice If it is included, it should conform to the profile Metadata can be easily captured and it is highly recommended that it be sent with an AIXM message

Mandatory Message Metadata T16:00:00Z Scott Wilson AIXM Development Support distributor “baseline” timeslice valid 01 Jan 2008 en T16:00:00Z Scott Wilson AIXM Development Support distributor “baseline” timeslice valid 01 Jan 2008 en

Feature Timeslice Metadata T16:00:00Z EUROCONTROL AIXM Development originator Donlon antenna Metadata study T17:00:00Z revision T16:00:00Z EUROCONTROL AIXM Development originator Donlon antenna Metadata study T17:00:00Z revision

Current Status The AIXM Metadata Model has not been applied to the XML Schema in Release Candidate 2 RC2 uses the ISO Schemas Release Candidate 3 will consider the adoption of the profile The AIXM Metadata Model has not been applied to the XML Schema in Release Candidate 2 RC2 uses the ISO Schemas Release Candidate 3 will consider the adoption of the profile

Next Steps The final AIXM 5 release will provide guidelines on how certain metadata fields shall be used This will lead to harmonised encodings of certain information, such as –accountable source, –date when the information was issued, –contact details, etc. The final AIXM 5 release will provide guidelines on how certain metadata fields shall be used This will lead to harmonised encodings of certain information, such as –accountable source, –date when the information was issued, –contact details, etc.

Metadata Forms

Thank you