Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »





AIXM 5.1 - Business Rules (data verification)
Using SBVR and Schematron












Document Status: Draft
Publication date: 08 November 2016
version: 0.7
Aeronautical Information Exchange Model
(AIXM)
Copyright: 2016 - EUROCONTROL and Federal Aviation Administration
All rights reserved.
This document and/or its content can be downloaded, printed and copied in whole or in part, provided that the above copyright notice and this condition is retained for each such copy.
For all inquiries, please contact:
Eduard POROSNICU - eduard.porosnicu@eurocontrol.int
Deborah COWELL - deborah.cowell@faa.gov

Edition

Status

Issue Date

Reason for Change

0.1

Working Draft

25 July 2013

Initial working draft. Derived from previous work by Pulsar Consulting (under contract for Eurocontrol) and from the "Guidance on Writing AIRM Constraints" - SESAR Project 08.01.03 deliverable, which is itself based on the previous Eurocontrol worl

0.2

Working Draft

05 August 2013

Updated after initial attempts to use the instructions and after discussion with group members, in particular issues raised by Michal Kadlec

0.3

Draft

09 June 2014

First public release, intended for a wider review. Also including an introductory part explaining the need for business rules, the experience of the previous AIXM model version and the approach proposed for AIXM 5

0.4

Draft

15 June 2015

Second public release. Minor editorial changes. Some new keywords added. Further details about how to write paths to target NounConcepts. First examples of profiles.

0.5

Draft

15 September 2015

Updated public release. No significant changes to the document, just small editorial corrections. Issued together with version 0.5 of the rules.

0.6

Draft

July 2016

Updated version. Editorial adjustments, such as grouping together all explanations related to the use of "has" in fact types. Additional explanations about the use of the SBVR standard to the AIXM Business Rules project. Inclusion of the "different instances" notation for NounConcepts. Removal of the special notation for <<choice>> classes.

0.7

Draft

08 November 2016

Public release, in relation with the publication of the Business Rules set 0.7. Additional explanation about the use of specialised classes as NounConcept.


Contributors
This document reflects the contribution of technical and operational aeronautical information specialists, in particular from industry. Their contribution is hereby acknowledged.

Name

Organisation

CLAY Michael

Frequentis

CHUMAKOV Marina

CNA (under contract for US FAA)

DIELS-GRABSCH Volker

m-click.aero

DRUARD Sophie

Pulsar Consulting

ECHTERHOFF Johannes

Interactive Instruments

FABBRI Davide

IDS

GERMAIN Francois

Thales

GHENCEA Andrei

Eurocontrol (trainee)

HAAS Markus

Comsoft

d'HULST Jean-Christophe

Pulsar Consulting

KADLEC Michal

Avitech

POROSNICU Eduard (editor)

Eurocontrol

RAZOV Aleksandr

Monitor Soft

SANCHEZ Antonio

GroupEAD

SCHNEIDER Markus

m-click.aero

SCHEUCHER Wolfgang

Solitec

SUZIC Robert

Eurocontrol

TANG Yauwu

MITRE Corporation

WALTL Michael

Frequentis

WILSON Scott

Eurocontrol



Table of contents
Executive Summary
Introduction
The need for Business Rules
How to read this document
Rules definition using SBVR
Introduction
SBVR Profile for AIXM
SBVR concepts
NounConcept - special situations
Additional Fact-types
Verb concept - special situations
Logical Operations
Quantification
Modality
Additional SBVR keywords
Methodology
Schematron test implementation
Introduction
Schematron code - technical aspects
XPath version
XPath compatibility
Use of Java extensions
Feature references in the Schematron code
Content of the Excel file
Practical verification of AIXM data sets
Testing
AIXM Business Rules data set
Excel file
Profiles
EAD Data Provider
Event profile
Event_FAA profile
Minimum air navigation data set profile
Full air navigation data set profile
References
Annex A - License and Disclaimer
Annex B - Examples

  • No labels