Rules data set (XML)

File location

Until the work on the new syntax is finalised, the file that contains the work in progress version of the rules is provided here: https://drive.google.com/drive/folders/1cXsTgQcIcV-DFxNyP5lftLLNxEjeudJD?usp=sharing

Rule editor

The AIXM Business Rules are currently created and managed by Eurocontrol, using a tool called Business Rules Manager (BRM), which is currently not available to the external users. A new version of the BRM tool is in development, featuring many significant enhancements and including the possibility to offer access to external users.

One of the important capabilities of the BRM is "rule templates", which enables the creation and maintenance of rules that have a similar structure in the form of a single "abstract" rule, with a number of concrete instances. The screenshot below shows an example of such a templated rule. It is estimated that 70-80% of the current AIXM business rules are templated and that preserving this information in the output rule sets might be beneficial for the users.

Publication format

The AIXM Business Rules are provided in two formats:

as an XML file, which preserves the information about "templates" that are applied in the definition of the majority of the rules. The XML format is intended to be used for automating the development of data validation services, which could generate code directly from the SBVR structured rules and templates
as a table, in Excel format. which is created by converting the original XML file into HTML and importing in Excel.

Note

In case of discrepancies between the XML and the Excel version, the XML version should be considered as the authoritative version.

XML file

The XML export structure follows the schema defined in the AIXM-BR-SBVR.XSD file, which matches with the following structure:

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="AIXM-BR-SBVR.xsl"?>
<AIXM-BR-SBVR xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" criteriaAIXMversion="5.1.1" criteriaProfile="eEAD:Warning, eEAD:Error, DigitalNOTAM:Error, DigitalNOTAM:Warning" criteriaStatus="Rule accepted" exportedAt="2024-04-15T20:22:32.854048Z" xsi:noNamespaceSchemaLocation="AIXM-BR-SBVR.xsd">

   <rule uid="AIXM-5.1.1_RULE-1F47D0">
    <profiles>
      <profile>
        <name>DigitalNOTAM</name>
        <level>Error</level>
      </profile>
    </profiles>
    <name>(Event) version 2.0</name>
    <aixm_class>event:Event</aixm_class>
    <aixm_attributes>version</aixm_attributes>
    <aixm_association/>
    <sbvr>
      <keyword>It is prohibited that</keyword>
      <noun_concept>event:Event</noun_concept>
      <verb_concept>has-descendant</verb_concept>
      <noun_concept>event:version</noun_concept>
      <keyword>value</keyword>
      <keyword>other-than</keyword>
      <name>'2.0'</name>
    </sbvr>
    <comments>It is obligatory that the Event has version equal to '2.0'</comments>
    <diagnostics>Found Event version different from '2.0'</diagnostics>
    <timeslice/>
    <category>Standard (ICAO, industry, etc.)</category>
    <source>Digital NOTAM Event Specification</source>
    <reference/>
    <context>It is prohibited that DVT</context>
    <remarks/>
  </rule>

  <template uid="1AA450">
    <profiles>
      <profile>
        <name>eEAD</name>
        <level>Warning</level>
      </profile>
    </profiles>
    <name>Resolution (horizontal) - ${Equipment} when used at aerodrome</name>
    <aixm_class>Navaid</aixm_class>
    <aixm_attributes/>
    <aixm_association>servedAirport, composedOf</aixm_association>
    <sbvr>
      <keyword>It is prohibited that</keyword>
      <noun_concept>NavaidTimeSlice</noun_concept>
      <verb_concept>has</verb_concept>
      <noun_concept>servedAirport@xlink:href</noun_concept>
      <keyword>value</keyword>
      <keyword>and</keyword>
      <noun_concept>NavaidTimeSlice.navaidEquipment@xlink:href</noun_concept>
      <verb_concept>references-to</verb_concept>
      <noun_concept>${Equipment}</noun_concept>
      <keyword>and</keyword>
      <noun_concept>${Equipment}</noun_concept>
      <verb_concept>has-descendant</verb_concept>
      <noun_concept>gml:pos</noun_concept>
      <keyword>value</keyword>
      <keyword>coordinates-expressed-with</keyword>
      <keyword>less-than 5</keyword>
      <name>'decimals'</name>
    </sbvr>
    <comments>Latitude and Longitude of ${Equipment}, when used for aerodrome operations, shall be published with 1/10 sec resolution</comments>
    <diagnostics>Found ${Equipment} used for homing at AirportHeliport and having location.ElevatedPoint coordinates expressed with insufficient resolution (less than 5 decimals).</diagnostics>
    <timeslice>set of snapshots</timeslice>
    <category>Recommended practice (ICAO, industry, etc.)</category>
    <source>ICAO Annex 15</source>
    <reference>Table A7-1</reference>
    <context>It is prohibited that DV and RF and DVT</context>
    <remarks/>
    <instances>
      <instance uid="AIXM-5.1.1_RULE-1AA451">
        <profiles>
          <profile>
            <name>eEAD</name>
            <level>Warning</level>
          </profile>
        </profiles>
        <parameters>
          <parameter name="Equipment">VOR</parameter>
        </parameters>
      </instance>
      <instance uid="AIXM-5.1.1_RULE-1AA452">
        <profiles>
          <profile>
            <name>eEAD</name>
            <level>Warning</level>
          </profile>
        </profiles>
        <parameters>
          <parameter name="Equipment">DME</parameter>
        </parameters>
      </instance>
	...

Tabular format

First, an XSL stylesheet is used to convert the AIXM-BR-SBVR.xml export file into a single HTML table, where templates are instantiated.

Then, the HTML table was imported into Microsoft Excel. Here, the file was sorted by AIXM Class, AIXM Attribute and AIXM Associations. In addition, filters have been defined for the various 'Profile' columns.

The result in the form of an Excel table looks like this: