Light
Dark
System
Log In
Loading...
Compare / EASA/
Incorporated Amendments
/
Compare & Highlight Differences
AMC1 AIS.TR.210 Exchange of aeronautical data and aeronautical information
Available versions for ERULES-1963177438-17501
ED Decision 2020/008/R
found in: ATM/ANS Provision of Services (2017/373) (Mar 2025)
From
ATM/ANS Provision ... (Mar 2025)
ATM/ANS Provision ... (Feb 2023)
From section
To
ATM/ANS Provision ... (Mar 2025)
ATM/ANS Provision ... (Feb 2023)
To section
No visible text changes
0 removals
0 additions
View
Rich
Plain
Sync scrolling
Share
From
Show details
Hide details
To
Show details
Hide details
Version
Show side by side
AMC1 AIS.TR.210 Exchange of aeronautical data and aeronautical information ED Decision 2020/008/R EXCHANGE MODELS (a) The exchange model used should encompass the aeronautical data and aeronautical information to be exchanged. (b) The exchange model used should: (1) use the unified modelling language (UML) to describe the aeronautical information features and their properties, associations and data types; (2) include data value constraints and data verification rules; (3) include provisions for metadata; (4) include a temporality model to enable capturing the evolution of the properties of an aeronautical information feature during its life cycle; (5) apply a commonly used data encoding format; (6) cover all the features, attributes, data types and associations of the aeronautical information model; and (7) provide an extension mechanism by which groups of users can extend the properties of existing features and add new features which do not adversely affect global standardisation.
AMC1 AIS.TR.210 Exchange of aeronautical data and aeronautical information ED Decision 2020/008/R EXCHANGE MODELS (a) The exchange model used should encompass the aeronautical data and aeronautical information to be exchanged. (b) The exchange model used should: (1) use the unified modelling language (UML) to describe the aeronautical information features and their properties, associations and data types; (2) include data value constraints and data verification rules; (3) include provisions for metadata; (4) include a temporality model to enable capturing the evolution of the properties of an aeronautical information feature during its life cycle; (5) apply a commonly used data encoding format; (6) cover all the features, attributes, data types and associations of the aeronautical information model; and (7) provide an extension mechanism by which groups of users can extend the properties of existing features and add new features which do not adversely affect global standardisation.