40
Copyright © 2011 Open Geospatial Consortium.
The AIXM encoding shall be done according to guidelines contained in
the Use of GML for aviation data document.
DNES 5.3.2
“Use of GML for
aviation data”
Not covered through DNOTAM schematron rules, as this is a
requirement for general AIXM data, not one added through DNOTAM
business rules. It should thus be covered through general AIXM
schematron rules.
8.1.3.6 Coverage of normative statements in DNES section 5.4
Normative Statement Source
Rule Coverage
consistency rules between the uom value and the reference value in “...Limit” and “...LimitReference”
properties like “upperLimit”, “lowerLimit”, “maximumLimit”, “minimumLimit”
DNES 5.4.1.1 TBD
In addition to numerical values, the ...Limit attributes can use four coded values GND, UNL,
FLOOR, CEILING which also have special encoding rules regarding the uom attribute
DNES 5.4.1.2 TBD
for a “...Limit” property, the values FLOOR and CEILING may be used only in AirspaceLayer, in
relation with AirspaceActivation, AirspaceLayerClass, RouteAvailability. The
...Reference attribute shall be left empty in this situation. However, even if another uom is used or
even if the ...Reference attribute gets a value, they should be ignored by a recipient application because
they do not have any meaning in combination with these coded values
DNES 5.4.1.2 TBD
8.1.3.7 Coverage of normative statements in DNES section 5.6.2
Normative Statement Source
Rule Coverage
Copyright © 2011 Open Geospatial Consortium.
41
Normative Statement Source
Rule Coverage
ER-01 the Event update shall be encoded as a new PERMDELTA TimeSlice of the corresponding Event
feature, with an incremented sequenceNumber. The PERMDELTA shall contain the updated value for the
featureLifetime property. If the new end of validity is estimated, then the rules for Events with estimated end
of validity shall be followed
4
DNES 5.6.2.2 TBD
ER-02 If the original Event has been encoded as one or more TEMPDELTA TimeSlices for existing AIXM
Features, then the update shall be encoded as a correction TimeSlice for each affected feature. A
new TEMPDELTA shall be created having the same content and sequenceNumber as the original one, an
incremented correctionNumber and an updated end of validity. If the new end of validity is estimated, then
the rules for Events with estimated end of validity shall be followed.
DNES 5.6.2.2 TBD
ER-03 If the original Event has been encoded as one or more PERMDELTA BASELINE TimeSlices for a
new AIXM Feature, then the update shall be encoded as an additional PERMDELTA TimeSlice, with an
incremented sequenceNumber. A new BASELINE shall be created having the same data content as the
original one, an incremented sequenceNumber, an updated end of validity and an updated feature
lifetime.
5
DNES 5.6.2.2 TBD
ER-04 If the Event update is an immediate cancellation of the condition that has triggered to the original event,
DNES 5.6.2.2 According to
sponsors, this
4
see section 5.4.4 for further details on the usage of Permdeltas and Baselines for dnotam:Events
5
This rule can be combined with ER-01 in DNES section 5.6.2.2 - see list item “Event end time update handling of static data” in section 5.4.8 for further details.
