1. The European Organisation for the Safety of Air Navigation Open session AIXM XML Developers' Seminar

2. AIXM 5.1 – Business rules 2 Content UUID XML Schema structure order of elements order of features annotations in XML Schema use of global elements with global types schema profile bi-directional associations platform-neutral treatments of AIXM extension mechanism GML encoding “Donlon” data set mapping AIXM / Arinc424A-XML Mapping/Connection with other data formats (eg. ARINC 424) AICM generic DB

3. AIXM 5.1 – Business rules 3 Universal Unique Identifiers (UUID) Two aspects Feature identification Feature reference (association) TimeSlice validTime = … interpretation = BASELINE sequenceNumber = 1 property 1 property 2 property 3 (xlink:href to AirportHeliport) property 4 property 5 Runway gml:identifier = UUID

4. AIXM 5.1 – Business rules 4 Universal Unique Identifiers (UUID) Feature identification dd062d88-3e64-4a5d-bebd-89476db9ebea alternative: include a Snapshot TimeSlice TimeSlice validTime = … interpretation = SNAPSHOT sequenceNumber = 1 property 3 (xlink:href to AirportHeliport) designator = 08L/26R Runway TimeSlice validTime = … interpretation = TEMPDELTA sequenceNumber = 1 property 5 = temporary value…

5. AIXM 5.1 – Business rules 5 Universal Unique Identifiers (UUID) Feature reference Xlink:href By UUID SUPERVISE

6. AIXM 5.1 – Business rules 6 Universal Unique Identifiers (UUID) Idea – also provide the natural key as “xlink:title” thanks to Iain Hammond, MacDonald, Dettwiler & Associates Ltd, AIXM User Conference 2008, Washington DC, USAIain Hammond, MacDonald, Dettwiler & Associates Ltd, AIXM User Conference 2008, Washington DC, USA SUPERVISE http://www.aixm.aero/example#xpointer(//aixm:OrganisationA uthority[gml:identifier='74efb6ba-a52a-46c0-a16b-03860d356882'])

7. AIXM 5.1 – Business rules 7 Universal Unique Identifiers (UUID) xlink:title = ' ' The title attribute shall be used to describe the meaning of a link or resource in a human-readable fashion, along the same lines as the role or arcrole attribute. A value is optional; if a value is supplied, it shall contain a string that describes the resource. In general it is preferable to use a 'title' child element rather than a 'title' attribute. The use of this information is highly dependent on the type of processing being done. It may be used, for example, to make titles available to applications used by visually impaired users, or to create a table of links, or to present help text that appears when a user lets a mouse pointer hover over a starting resource.

8. AIXM 5.1 – Business rules 8 Order of elements as is? alphabetical for easier generation of AIXM files? imposed by a sequence number, based on some kind of 'importance'?

9. AIXM 5.1 – Business rules 9 Order of features No rules? Imposed (as in AIXM 4.5 – for SAX parser) specified in a document? imposed by schema? supported by a XSLT script generic (any referenced feature brought up)? specific (always order as in the specified order)?

10. AIXM 5.1 – Business rules 10 Annotations in XML Schema Conclusion from day 1: Yes, include in the schema definitions for class, attribute, role, data type and enumerated values. Also provide a copy of the schema without all these annotations, to facilitate usage of the schema for pure validation Use the version without annotations on www.aixm.aero/schema/5.1 www.aixm.aero/schema/5.1

11. AIXM 5.1 – Business rules 11 Need for an expanded model?

12. AIXM 5.1 – Business rules 12 Show nilReason in the UML model?

13. AIXM 5.1 – Business rules 13 Use of global elements with global types Where to do that In the XML schema only? In the UML model also?

14. AIXM 5.1 – Business rules 14 Use of global elements with global types Raised by Luciad: “For the ValDistanceType only, there are already around 130 of these identical anonymous types defined in the schema. The result of all these anonymous types is a huge amount of Java classes which are all identical and make our domain model too large to manage. <xsd:attribute name="nilReason" type="gml:NilReasonEnumeration" /> Instead of introducing all these anonymous types in the XML Schema, I would suggest to define one global named type for each type for which a variant with a nilReason is required (e.g. a ValDistanceOrNullType or something similar for the example above). This allows reusing of types, which not only makes our Java domain model much more manageable, but also makes the XML Schema more readable and smaller in size.”

15. AIXM 5.1 – Business rules 15 Use of global elements with global types The measured angle between the runway direction and True North at a given position. Note : The True North is the north point at which the meridian lines meet. ………………….

16. AIXM 5.1 – Business rules 16 Use of global elements with global types Used as unique key for the identification of the Time Slice concerned. See the AIXM Temporality model for details.

17. AIXM 5.1 – Business rules 17 Schema profile Need sub-set of AIXM features Would like to work with just a sub-schema? What is the advantage code generation Solution: Provide a script that allows to select the desired features and then extracts from the AIXM-Features.xsd and AIXM- DataTypes.xsd just the needed elements Also GML profile! Metadata profile!

18. AIXM 5.1 – Business rules 18 Bi-directional associations

19. AIXM 5.1 – Business rules 19 Bi-directional associations +airplaneLandingArea

20. AIXM 5.1 – Business rules 20 Bi-directional associations Provided as a separate version of the AIXM Schema? Provided as an “extension”?

21. AIXM 5.1 – Business rules 21 AIXM Extensions platform-neutral treatments of AIXM extension mechanism? Answered yesterday? Migration to EA and use of XMI as start of the schema generation process?

22. AIXM 5.1 – Business rules 22 GML encoding recommended GML constructs for point, line, polygon geometries

23. AIXM 5.1 – Business rules 23 GML encoding Significant Point reference from airspace vertex Where the Point with the gml:id “myPointID” is defined in the same file as position for a Navaid or DesignatedPoint …. 5.97166667 50.97611111

24. AIXM 5.1 – Business rules 24 GML encoding geo-border reference from airspace vertex FAA solution mentioned yesterday Other ideas? Extent the gml:PointProperty? By reference to a local copy of the exact extraction from the GeoBorder

25. AIXM 5.1 – Business rules 25 GML encoding Future for procedure definition and GML geometries

26. AIXM 5.1 – Business rules 26 Donlon Data Set Current status – see www.aixm.aero (Downloads page)www.aixm.aero How to improve it? What do you need?

27. AIXM 5.1 – Business rules 27 2010: A424 v19 will become A424-A v1 ARINC424-19 NDBX (former Arinc829) (Embedded format Requirements) Input for the definition of 424A content ARINC424-A formats Script 1 Visual Basic “Bijection” between original A414-19 and Arinc424-A ASCII ARINC 424A ASCII ARINC424A BXML (embedded XML) Full ARINC424A XML Script 2 TBD ARINC424-A Model UML Adapted ARINC424 XML ARINC 424A

28. AIXM 5.1 – Business rules 28 Mapping AIXM / Arinc424A-XML In 2011, EUROCONTROL will Define a set of mapping rules for conversion of ground sources (AIPs published in AIXM 5.1 format) into Arinc424A- XML Develop, as a proof of concept, some code that implements these rules Primary focus will be on data used by the FMS (former NDBX scope) Objective: validate the concept of a full digital data chain from AIPs up to the embedded system ARINC 424A XML/BXML FMS Simulation