Page Comparison

Info

title	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.

Image AddedImage Added

Publication format

The AIXM Business Rules are provided in two formats:

as an XML file, which preserves the information about "templates", which that are used 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 HTML Excel format. which is created by converting the original XML file into HTML . This can also be imported in Excel, in order to facilitate the transition to the new syntax, as the previous versions have been published only in Excel format. Also, the Excel format is more convenient for human used, as it allows sorting and filtering of the rules.and importing in Excel.

Info

title	Note

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

XML file

Warning
This is not the latest version. A new "context" element is exported, containing the mapping of the rule to the new grammar. Also, the <sbvr> element does no longer allow complex content in order to facilitate the detection of missing SBVR tags. A new <text> element will be used for free text in SBVR.

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

Code Block

language	xml
theme	Confluence
firstline	1
linenumbers	true

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="AIXM-BR-SBVR.xsl"?><AIXM>
<AIXM-BR-SBVR xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 	criteriaUIDcriteriaAIXMversion="5.1..1" 	criteriaText="..."
	criteriaCategory="..."
	criteriaProfile="eEAD:Warning, eEAD:Error, DigitalNOTAM:Error, DigitalNOTAM:Warning" criteriaStatus="Rule accepted" 	criteriaSource="..."
	criteriaAssignee="..."
    criteriaAIXMversion="..."
	criteriaProfile="Event:Warning"
	criteriaRights="..."
	exportedAt="20192024-0104-04T1215T20:22:32:47.111Z854048Z"
    xsi:noNamespaceSchemaLocation="AIXM-BR-SBVR.xsd">
    <!-- all criteria used to select the rules are included as attributes of the root element.
        Criteria not used are left out. A time stamp for the export is added.  -->

   <rule uid="AIXM-5.1.1_RULE-1A5E001F47D0">
       
<!-- example for a simple rule -->
        <profiles>
      <profile>
     <!-- for each applicable<name>DigitalNOTAM</name>
profile, include a profile element here. -->
            <profile> 				<name>EAD</name> 				<level>Error</level>
			</profile>
          
 <profile> 				<name>etc. if applicable</name> 				<level>...</level> 			</profile>
   
    </profiles>
    <name>(Event)    <!-- attention, the order of the fields is slightly different from the Excel export. References are at the end, as they are less important. -->
        <name>GML Profile - Geographic Reference Systems supported</name>
   version 2.0</name>
    <aixm_class>*<class>event:Event</aixm_class>
   
    <aixm_attributes>*<attributes>version</aixm_attributes>
   
    <aixm_association/>
    <sbvr>
   <!-- empty fields should<keyword>It beis includedprohibited asthat</keyword>
they will make simpler the script for generating a HTML table at the end --> 
        <sbvr>
      <noun_concept>event:Event</noun_concept>
      <verb_concept>has-descendant</verb_concept>
      <!-- export here rule tagged description --> 
            <keyword>It is prohibited that assigned</keyword> <noun_concept>srsName<<noun_concept>event:version</noun_concept>
<keyword>value</keyword> <keyword>not</keyword> <keyword>equal-to</keyword> <name>('urn:ogc:def:crs:EPSG::4326', 'urn:ogc:def:crs:EPSG::4258', 'urn:ogc:def:crs:EPSG::4322', 'urn:ogc:def:crs:EPSG::4230', 'urn:ogc:def:crs:EPSG::4668', 'urn:ogc:def:crs:EPSG::4312', 'urn:ogc:def:crs:EPSG::4215', 'urn:ogc:def:crs:EPSG::4801', 'urn:ogc:def:crs:EPSG::4149', 'urn:ogc:def:crs:EPSG::4275', 'urn:ogc:def:crs:EPSG::4746', 'urn:ogc:def:crs:EPSG::4121', 'urn:ogc:def:crs:EPSG::4658', 'urn:ogc:def:crs:EPSG::4299', 'urn:ogc:def:crs:EPSG::4806', 'urn:ogc:def:crs:EPSG::4277', 'urn:ogc:def:crs:EPSG::4207', 'urn:ogc:def:crs:EPSG::4274', 'urn:ogc:def:crs:EPSG::4740', 'urn:ogc:def:crs:EPSG::4313', 'urn:ogc:def:crs:EPSG::4124', 'urn:ogc:def:crs:EPSG::4267', 'urn:ogc:def:crs:EPSG::4269', 'urn:ogc:def:crs:OGC:1.3:CRS84')</name>
    <keyword>value</keyword>
      <keyword>other-than</keyword>
      <name>'2.0'</name>
    </sbvr>
    <comments>It is obligatory  <comments>Onlythat the coordinateEvent referencehas systemversion listedequal in Appendix 1 of the GML Guidelines for Aviation Data shall be used.to '2.0'</comments>
    <diagnostics>Found Event version different <diagnostics>Only the coordinate reference system listed in Appendix 1 of the GML Guidelines for Aviation Data shall be used.from '2.0'</diagnostics>
        <timeslice>All</timeslice>
   <timeslice/>
    <category>Standard (ICAO, industry, etc.)</category>
    <source>Digital NOTAM   <source>ICAO Annex 15<Event Specification</source>
        <reference>Appendix 1</reference><reference/>
    <context>It is prohibited  <schematron>
            <context>//*[@srsName]<that DVT</context>
            <code>@srsName=( 
                'urn:ogc:def:crs:EPSG::4326', 
                'urn:ogc:def:crs:EPSG::4258', 
                'urn:ogc:def:crs:EPSG::4322', 
                'urn:ogc:def:crs:EPSG::4230', 
                'urn:ogc:def:crs:EPSG::4668', 
                'urn:ogc:def:crs:EPSG::4312', 
                'urn:ogc:def:crs:EPSG::4215', 
                'urn:ogc:def:crs:EPSG::4801', 
                'urn:ogc:def:crs:EPSG::4149', 
                'urn:ogc:def:crs:EPSG::4275', 
                'urn:ogc:def:crs:EPSG::4746', 
                'urn:ogc:def:crs:EPSG::4121', 
                'urn:ogc:def:crs:EPSG::4658', 
                'urn:ogc:def:crs:EPSG::4299', 
                'urn:ogc:def:crs:EPSG::4806', 
                'urn:ogc:def:crs:EPSG::4277', 
                'urn:ogc:def:crs:EPSG::4207', 
                'urn:ogc:def:crs:EPSG::4274', 
                'urn:ogc:def:crs:EPSG::4740', 
                'urn:ogc:def:crs:EPSG::4313', 
                'urn:ogc:def:crs:EPSG::4124', 
                'urn:ogc:def:crs:EPSG::4267', 
                'urn:ogc:def:crs:EPSG::4269', 
                'urn:ogc:def:crs:OGC:1.3:CRS84' 
                )</code>
        </schematron>
    </rule>
<remarks/>
  </rule>

  <template uid="1ACF48">
        <!-- example for a templated rule -->
   1AA450">
    <profiles>
      <profile>
     <!-- for each applicable<name>eEAD</name>
profile, include a profile element here. -->
            <profile>
				<name>EAD</name>
				<level>Error</level>
			</profile>
            <profile>
				<name>etc. if applicable</name>
				<level>...</level>
			</profile>
     <level>Warning</level>
      </profile>
    </profiles>
    <name>Resolution    <!-- attention, the order of the fields is slightly different from the Excel export. References are at the end, as they are less important. -->
        <name>Mandatory unit of measurement</name>
   (horizontal) - ${Equipment} when used at aerodrome</name>
    <aixm_class>${entity}<class>Navaid</aixm_class>
   
    <aixm_attributes>${property}</aixm_attributes>
   attributes/>
    <aixm_association/>association>servedAirport, composedOf</aixm_association>
    <sbvr>
   <!-- empty fields should<keyword>It beis includedprohibited asthat</keyword>
they will make simpler the script for generating a HTML table at the end --> <noun_concept>NavaidTimeSlice</noun_concept>
      <verb_concept>has</verb_concept>
      <noun_concept>servedAirport@xlink:href</noun_concept>
   <sbvr>   <keyword>value</keyword>
      <keyword>and</keyword>
  <!-- export here rule tagged description --> <noun_concept>NavaidTimeSlice.navaidEquipment@xlink:href</noun_concept>
      <verb_concept>references-to</verb_concept>
        <keyword>Each </keyword><noun<noun_concept>${entityEquipment}</noun_concept>
     <keyword>with assigned<<keyword>and</keyword>
      <noun_concept>${propertyEquipment}</noun_concept> <keyword>shall</keyword>
      <verb_conceptconcept>has-concept>have<descendant</verb_concept-concept> <keyword>assigned</keyword>
      <noun_concept>${property}.uom<concept>gml:pos</noun_concept>
<keyword>value</keyword>      <keyword>value</keyword>
   </sbvr>   <keyword>coordinates-expressed-with</keyword>
     <comments>The Unit of measurement shall be specified if a value is specified for a property with uom attribute.</comments><keyword>less-than 5</keyword>
      <name>'decimals'</name>
    </sbvr>
    <comments>Latitude and Longitude  <diagnostics>Foundof ${entityEquipment}, withwhen assigned ${property} value missing unit of measurement</diagnostics>
   used for aerodrome operations, shall be published with 1/10 sec resolution</comments>
    <timeslice>All</timeslice>
        <category>Coding rule</category>
        <source>AIXM Model</source><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   <referencesnapshots</>timeslice>
    <category>Recommended practice (ICAO,  <schematron>industry, etc.)</category>
    <source>ICAO Annex 15</source>
    <reference>Table <context>//aixm:${entity}/aixm:${property} | //aixm:${entity}TimeSlice/aixm:${property}</context>A7-1</reference>
    <context>It is prohibited that DV and RF    <code>string-length(.)=0 or string-length(@uom)!=0</code>and DVT</context>
        </schematron>
   <remarks/>
    <instances>
     
      <instance UIDuid="AIXM-5.1.1_RULE-D8CC11AA451">
       
        <profiles>
            <profile>
       <!-- for each applicable profile specified, include a profile element here. --> <name>eEAD</name>
            <level>Warning</level>
          <profile>
						<name>etc. if applicable</name>
						<level>...</level>
					</profile>
       
        </profiles>
       
        <parameters>
         
          <parameter name="entity">AerialRefuellingAnchor</parameter>
                    <parameter name="property">speedLimit</parameter>
       Equipment">VOR</parameter>
        </parameters>
     
      </instance>
     
      <instance UIDuid="AIXM-5.1.1_RULE-D8CC31AA452">
   
            <profiles>
          <profile>
         <!-- for each applicable<name>eEAD</name>
profile specified, include a profile element here. -->         <level>Warning</level>
           <profile>
						<name>etc. if applicable</name>
						<level>...</level>
					</profile>
       
        </profiles>
       
        <parameters>
         
          <parameter name="entity">AerialRefuellingAnchor</parameter>
                    <parameter name="property">legLength<Equipment">DME</parameter>
                </parameters>
     
      </instance>
            <!-- etc. -->
        </instances>
    </template>
</AIXM-BR-SBVR>	...

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.
The transformation can also be done with a browser such as Internet Explorer, which is able to process the XSL styling information. For that purpose:
copy the AIXM-BR-SBVR.xsl transformation file next to the AIXM-BR-SBVR.xml export file,
open the AIXM-BR-SBVR.xml export file with Internet Explorer, or with any XSLT compatible tool (like an XML editor ).
The result in HTML tabular format looks like this:
Warning
The HTML export has an editorial issue - a <parameter> element appears in some places, after a line break. The new line is displayed as a white space in the Rule textual description and tagged description. For example, in rule D6D81 displayed below, there is a white space before the value 'M' (... equal-to ' M' has ... instead of ... equal-to 'M' has ...). This editorial issue is propagated in the Excel file created as explained further down. For system that used to import the Excel file with the rules and generate data verification code automatically, this can result into erroneous code.
Until the script is corrected, this editorial issue can be resolved by editing the HTML file with a text editor able to do find/replace based on regular expressions and removing all the new line and whitespace that precede the element <parameter name=....>. For example, in OxygenXML this can be done using
Find '\n\s*<parameter
Replace '<parameter
with "Regular expression" option enabled.
...

Excel

Finally, the HTML table was imported in Microsoft Word and then copied into 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 en an Excel table looks like this:

Image RemovedImage Added

Version	Old Version 3	New Version Current
Changes made by	POROSNICU Eduard	POROSNICU Eduard
Saved on	2023 Jul 14	2024 May 15

Versions Compared

Key

Rule editor

Publication format

XML file

Tabular format

Excel