Overview

Context

The AIXM model was initially developed by the European Organisation for the Safety of Air Navigation (EUROCONTROL) for the needs of the European AIS Database (EAD). The latest versions AIXM 5.1/5.1.1 have been developed in cooperation between the US Federal Aviation Administration (FAA) and EUROCONTROL with support from the international community. The further evolution of the AIXM is managed in the interest of the largest number of AIXM stakeholders by a Change Control Board (“CCB”) with international participation (industry, ANSP, etc.).

At the global level, the AIS-AIMSG of the International Civil Aviation Organisation (ICAO) has finalised the development of a completely revisited Annex 15 to the ICAO Convention. Complemented by a new PANS-AIM document, this will enable the global transition towards the provision of digital data sets, which will gradually replace the provision of paper documents. One of the key elements of the new PANS-AIM document is the definition of an “AIP Data Set”, which comprises a minimal list of features (such as Navaids, Points, Airports, Airspace, Routes, etc.) and their properties that all states worldwide should be able to provide to effectively make the transition towards digital AIS data.

The AIXM 5 Coding Guidelines are documenting the minimal coding rules for the provision of the AIP Data Set in AIXM 5.1(.1) format, to ensure that such data sets can be effectively used by the downstream AIS data chain actors, particularly by Data Provider (DAT) organisations.

Scope

The AIXM 5 Coding Guidelines comprises the following elements:

• Mapping of the ICAO PANS-AIM AIP Data Set to AIXM 5.1(.1)
• AIXM 5.1(.1) coding rules for the AIP Data Set
• AIXM 5.1(.1) verification rules for the AIP Data Set
• Sample AIXM 5.1(.1) AIP Data Set

How to use

Structure

The present Confluence Space named “AIXM 5 Coding Guidelines (ACGAIP)" is a collection of several grouped content pages.

Besides this Overview page, the Space is structured according the defined scope, mainly consisting of two parts: the pages for the Mapping and the pages for the for the Coding guidelines. The latter is including the rules and coding examples.

Additionally, you will find several File lists that contain all kind of files used in the scope of these guidelines (e.g. documents, excel spreadsheets, etc.) which can be downloaded or viewed directly in Confluence.

A dedicated page contains a summary of all the References used on the individual guidelines pages.

Finally, you will find a Contacts page with some email address in case you want to send information or ask a question.

In the sidebar on the left-hand side you have also some Space Shortcuts, which are external links (e.g. to AIXM.aero) and internal links (e.g. to a List of comments).

Types of Users

There are 2 main types of users. Based on the type of the user, different access permissions are granted.

Named user (log-in is required)

• A named user has Read & Write access.
• A named user can create content (i.e. write/update content, upload images and files, etc.) and also review and comment all the content pages (i.e. draft versions and published versions).
• The content creation is workflow dependent. First a content page is in the draft status, then it should be assigned for review and finally it will be published.

Anonymous user (no log–in required)

• The anonymous user has only read access to “published” pages.
• He can review and comment on all published pages.
• In case of accessing a page that is not yet published a corresponding error message will be shown to the user.

Commenting

There are 2 main way of providing comments to the content.

• Inline commenting: Just highlight a text or part of a text on a page. Click on the little icon that appears, enter your comment and save it.
• Write a comment field: In case you have a general comment relevant for the whole content of a page enter your comment in corresponding field displayed at the bottom of each page and save it. This way of commenting allows some additional formatting (e.g. text colouring, bold etc.) and for named users also some additional functions (e.g. upload of images).

You can also edit your already saved comments.

Mark-ups

There are 3 main types of Mark-ups used.

Content Formatting (SBVR style)

For the AIXM elements on the confluence pages, i.e. features, attributes, values, etc. SBVR style formatting is used as defined in the document AIXM 5.1 - Business Rules - Using SBVR and Schematron (version 0.7) .

The main formats used are:

• SBVR NounConcept
  Represented by AIXM UML Classes and Properties, meaning that AIXM Class Name, Role Name or Attribute Name may appear as NounConcept.
  Style: Bold, underlined and UpperCamelCase or lowerCamelCase (depending on how the noun concept appears in the UML model). If several nouns are concatenated, then they should be separated by a dot (“.”) symbol.

• SBVR Verb-concept
  Represented by Name of an AIXM UML association.
  Style: italic

• SBVR 'Name'
  Represents UML Instances, Slots, Enumeration literals, and their assigned Properties and CodeList values
  Style: surrounded by ‘simple quotes’

• SBVR keyword
  are used to construct statements – the words that can be combined with other designations to form statements and definitions, see sections on Logical Operations, Quantification, Modality and Additional SBVR keywords, all these being part of the keyword concept
  Style: Usual text format

Contributors (i.e. named users) when providing content can format text according the SBVR style. Therefor dedicated text formatting styles have been created which can be selected in the edit mode from the tool bar.

Shortcuts:

SBVR NounConcept : CTRL+SHIFT+1

SBVR Verb-concept : CTRL+SHIFT+2

SBVR 'Name' : CTRL+SHIFT+3

SBVR keyword : CTRL+SHIFT+4

References