Copyright © 2011 Open Geospatial Consortium.
35
8.1.2 Coverage of Normative Statements in Chapter 3 - AIXM Event Schema
Normative Statement Source
Rule Coverage
[...] when the validity of an Event is extended or shortened, this will result in an additional
PERMDELTA TimeSlice for the Event feature, including the text of the NOTAM R or C that is
published on that occasion. DNES 3.2
TBD
The initial TimeSlice remains associated with the original NOTAM New, while the new TimeSlice [...]
DNES 3.2 TBD
It shall be noted that the Event is a regular AIXM feature, therefore it has TimeSlices. This allows
updating an Event:
each Event will be first encoded as a PERMDELTABASELINE TimeSlice pair;
an eventual change in the Event information the equivalent of a NOTAM Replacement or
Cancellation shall be encoded as an additional Event TimeSlice PERMDELTA and modified
BASELINE. DNES 3.2
TBD Requires
BASELINE data to be available
Note: see section 5.4.4 for further
information on handling
Permdeltas Baselines for
DNOTAM Events.
an AIXM feature TimeSlice that belongsTo an Event should have the same start of validity as the
Event lifetime start and the same end of validity as the Event lifetime end. This rule is true for most events,
but exceptions are possible because complex events such as an airshow, involving many features, could
have slightly different startend dates for the TimeSlices of the affected AIXM features
DNES 3.3 TBD
Needs explicit rules on when it
applies.
If type of TranslatedNOTAM is TEXT_ONLY, then only simpleText is allowed and language is
mandatory; DNES 3.3
TBD Possible
additional rule coherence checks between the NOTAM B and C items
with the included AIXM feature TimeSlice start of validity.
DNES 3.3 TBD
Possible additional rule
Each scenario has an identifier … this value shall be DNES 3.4
dnes-3.4.1
36
Copyright © 2011 Open Geospatial Consortium.
Normative Statement Source
Rule Coverage
put into the “scenario” attribute of the Event feature
Note that the scenario attribute is not mandatory for delta timeslices. The effect of the scenario attribute not being present is
that Schematron cannot know what scenario type the event is and will not apply any scenario-specific rules.
The scenario attribute should contain one of the following:
SAA.ACT, ATSA.ACT, SAA.NEW, ATSA.NEW, RTE.CLS, RTE.OPN, AD.CLS, RWY.CLS,
NAV.UNS, OBS.NEW, OBS.WDN, TWY.CLS, AD.CONT, OTHER
DNES 3.4 dnes-3.4.2
8.1.3 Coverage of Normative Statements in Chapter 5 - Data Encoding Rules 8.1.3.1 Coverage of normative statements in DNES section 5.1
Normative Statement Source
Rule Coverage
events that have an estimated end of validity shall be updated before that time is reached
DNES 5.1
According to the results of a QA
telcon performed during OWS-8 with
sponsors, this is a rule for both the
NOTAM operator and the originator
system. They shall find and warn of all
event for which the estimated end of
validity is approaching.
Therefore, this statement is not
applicable for the validator.
Kategori