AIRM Derivation: Generating ATM Exchange Models

®

AIRM Derivation

© 2013 Open Geospatial Consortium

Hosted and Sponsored by

83rd OGC Technical Committee

Redlands, CA USA

Debbie Wilson Clemens Portele

Snowflake Software interactive Instruments

January 17, 2013

OGC®

Objectives

AIRM to WXXM Derivation

ATM Information Reference Model (AIRM) is used as a common reference for civil, military and civil-military information constructs relevant to ATM developed as part of SESAR.

Aim: Demonstrate how to derive ATM exchange models (**XM) and their implementation schema from the AIRM – Meteorology to WXXM

© 2013 Open Geospatial Consortium, Inc.

1. Develop tools for generating ATM Exchange Models (**XM) from AIRM

2. Develop and document mapping rules:• AIRM to ISO 19109 UML Application Schema• Additional mapping rules needed for programmatic

derivation3. Demonstrate transforming AIRM Meteorology package into

WXXM and two implementation schemas: GML/ JSON

OGC®

AIRM Derivation Architecture


Available from: http://shapechange.net

Two Stage Approach: ShapeChange

http://shapechange.net/

OGC®

AIRM

AIRM Derivation Architecture

© 2013 Open Geospatial Consortium, Inc.

MDATransform

WXXM

Stage 1: Transform relevant AIRM packages into an ATM Exchange Model (**XM ) Application Schema

Shape Change

GML

JSON

Stage 2: Transform the ATM Exchange Model into physical implementation schemas (GML, JSON) and other representations

Two Stage Approach: ShapeChange

OGC®

Mapping Rules

• Two sets of mapping rules were defined:


MDA Transformation Rules

• Add Stereotypes and Tagged Values to packages, classes and attributes

• Set AIRM default multiplicities on attributes and association roles

UML to GML/JSON Encoding Rules

• ShapeChange already supports mapping rules for ISO/OGC UML types to GML and JSON*

• Defined additional mapping rules for:

1. Simplify encoding of AIRM data types (measures and strings) to use existing types (e.g. gml:Measure, integer)

2. Mapping AIRM data types to existing **XM types (e.g. AIXM geometry types)

3. Map ISO types not instantiated in GML & JSON to relevant GML/JSON type (e.g. DirectPosition GM_Point)

* UML to JSON Rules were developed in the SSI thread

OGC®

MDA Transformation

• Transforming AIRM packages into an ATM Exchange Model involves several steps:


Set-up

1. Import the MDA Transformation Templates into Enterprise Architect

2. Create a destination package for the Exchange Models

Transformation:

3. Select then transform relevant AIRM Subject Fields, Data Types and Abstract Types

4. Set the relevant tagged values to ensure correct generation of the implementation schema using ShapeChange

Demo: Generating an Exchange Model from AIRM

http://youtu.be/kCOSr7PtZhs



OGC®

Generating the implementation schemas

ShapeChange Configuration


ShapeChange Configuration

Input

Logging

Target

• XML• JSON• Codelist Dictionary• Feature Catalogue

Specify the location and format (xmi/eap) of the source model, which application schema packages are to be converted and UML profile applied

Specify the name and destination location of the log file and the logging level

Specify the destination locations, formats, encoding rules and any additional mapping rules for each of the required outputs

OGC®

Running ShapeChange …

• Either from the command line referencing the configuration file:java -jar ShapeChange-2.0.0-SNAPSHOT.jar -Dfile.encoding=UTF-8 -c ows9_wxxm_config.xml

• Or from Enterprise Architect:


After processing, the log file, implementation schema and other targets are generated on the file system

OGC®

Outputs from ShapeChange

GML & JSON Schemas:• AIRM• WXXM – WX & AVWX


OGC®



Codelist dictionaries


OGC®



Codelist dictionaries

Feature Catalogue


OGC®

Summary

Issues:• AIRM is still in development so inconsistencies exist between model and

AIRM Foundation Rules

• Difficult to automatically transform structured data types

• Recommendation: apply <<Entity>> to features and assign no stereotype to identifiable structured data types and do not apply the suffix “Type”

• Some association roles are assigned multiplicity but no name so inconsistent with ISO 19136 Rules for GML Application Schema

• May incorrectly transform some multiplicities as EA sets multiplicity to 1 by default – not visible on model. But in the AIRM, if multiplicity is not visible the property carries the AIRM default multiplicity: 0..1

• The model uses an old version of the ISOTC211 foundation schema and has deleted several key packages (e.g. ISO 19103 and ISO 19156 (draft).

• Recommendation: import full ISOTC211 model (preferably connect to SVN repository)


OGC®

Summary

Improvements


MDA Transformation Rules• Develop an AIRM UML Profile to ensure

classes are implemented consistently according to AIRM Foundation Rules

• Evaluate use of additional tagged values to improve encoding:

• inlineOrByReference

• vocabulary, extensibility (INSPIRE)

• Voidable (INSPIRE)

UML to GML/JSON Encoding Rules• No encoding rule improvements were identified

based on WXXM

• Additional encoding rules may need to be developed to support AIXM (Temporality/ extension)

• Evaluate ability to generate schematron rules automatically from the UML

• Future Work• Identified modeling issues should be resolved to enable a consistent

conversion from AIRM to implementation schemas• Evaluate ability to generate other exchange models (FIXM, AIXM)• Test implementation schemas, particulary JSON

OGC®

Summary

• Key AccomplishmentsSuccessfully demonstrated the ability to transform AIRM and

automatically generate implementation schemasDeveloped simple, flexible transformation & mapping rules for

generating ATM **XM Application SchemaBy using a schema conversion tool such as ShapeChange ensure

schemas are generated consistently


MDA Transformation Templates

ShapeChangeConfig & Schemas

http://wiki.snowflakesoftware.com/display/LAB/OWS-9+Aviation%3A+AIRM+Derivation

http://shapechange.net/tmp/ows9/wxxm/

http://wiki.snowflakesoftware.com/display/LAB/OWS-9+Aviation:+AIRM+Derivation




http://shapechange.net/tmp/ows9/wxxm/


®


OGC Public Engineering Report

12-094: OWS-9 Aviation: AIRM Derivationhttp://www.opengeospatial.org/standards/per

Aviation Domain Working GroupEmail: [email protected]

http://external.opengis.org/twiki_public/AviationDWG/WebHome

mailto:[email protected]

AIRM Derivation: Generating ATM Exchange Models

Documents

Transcript of AIRM Derivation: Generating ATM Exchange Models