Conclusion and Recommendation Improve Path Notation in Data Field Mappings .1 Problem Statement and Description

26 Copyright © 2011 Open Geospatial Consortium. TEMPDELTA” belongs to the same Airspace or to another Airspace though the former definitely makes more sense. The statement should be reconsidered and possibly removed, given that Tempdeltas with activation elements of the same Airspace may have the same validTime but different sequence or correction number. Furthermore, in some applications it might make sense to have Tempdeltas with overlapping validTime - e.g. when the application allows Airspace activations to be managed reserved and approved or disapproved and the according information is encoded via extension in Airspace activation elements. ● SAA.NEW Airspace activity code for Parachute – Section 4.4.5 of the DNES states: “If aixm:type=PJE, then the geometry of the area should not intersect the geometry of an existing Airspace with type ‘CTR’ or ‘TMA’.” The path should be Airspace.activation.activity and not aixm:type. Furthermore, the value should be PARACHUTE and not PJE. ● Event end time update handling of static data - The rules ER-01 and ER-02 in section 5.6.2.2 of the DNES should be aggregated into one rule, because updating an Event’s end time by issuing new Permdeltas and according Baselines usually is a combined activity. See section 5.4.4 for further details. ● Identification of schedule annotation for Event NOTAM - In section 5.2.6 of the DNES, a statement says that “[...] any eventual TS.note schedule annotations shall be converted into free text [...]”. It is not clear which element of a digital NOTAM is identified by “TS.note” PropertyWithSchedule.annotation, PropertyWithSchedule.timeInterval.annotation or something else. This should be clarified. ● Cancellation of Inactive Event ○ Change of FeatureLifetime - ER-02 in DNES section 5.6.3.2 states “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 sequenceNumber as the initial PERMDELTA, an increment correctionNumber ‘1’, an empty gml:validTime with nilReason=’inapplicable’ and an empty aixm:featureLifetime with nilReason=’inapplicable’.” First of all, there is a minor editorial issue: “PERMDELTA” should be replaced with “TEMPDELTA”. What is more important is that the Tempdelta timeslices for existing AIXM features are cancelled by providing a correction timeslice with both the validTime and the featureLifetime being empty and nilReason set to