Retrieve by Designator Portion

10 Copyright © 2012 Open Geospatial Consortium.

6.1.1.5 Retrieve by GML Identifier

In contrast to the previous model, this model retrieves all Airport TimeSlices which are valid for a specified time. The query limits the result to only match the Airport with a specific gml:identifier represented via a UUID. Besides the UUID matching the temporal filtering methods of the WFS instance are tested within this model. An example request is provided in Listing 2. Listing 2 – Retrieve by GML Identifier Request. wfs:GetFeature xmlns:fes = http:www.opengis.netfes2.0 xmlns:wfs = http:www.opengis.netwfs2.0 xmlns:gml = http:www.opengis.netgml3.2 xmlns:aixm = http:www.aixm.aeroschema5.1 service = WFS version = 2.0.0 count = 100 wfs:Query typeNames = aixm:AirportHeliport fes:Filter xmlns:fes = http:www.opengis.netfes2.0 fes:And fes:PropertyIsEqualTo fes:ValueReference gml:identifier fes:ValueReference fes:Literal C12-E7AB-5FC6-1EEEE040A8C0020260C5-1868 fes:Literal fes:PropertyIsEqualTo fes:AnyInteracts fes:ValueReference aixm:timeSlicegml:validTime fes:ValueReference gml:TimePeriod gml:id = validTimeStart gml:beginPosition 2010-11-09T10:28:58+0100 gml:beginPosition gml:endPosition 2012-11-09T10:28:58+0100 gml:endPosition gml:TimePeriod fes:AnyInteracts fes:And fes:Filter wfs:Query wfs:GetFeature

6.1.2 Transactional Models

As the WFS’s within the OWS-9 Aviation thread have to deal with dynamic features the designed test models have to take the dynamic nature of features into account as well. On top of that, the AIXM 5.1 specifics also have to be considered. In particular, this includes the TimeSlice CommissioningCancellation patterns defined in the AIXM 5 Temporality Model [1]. The WFS-T models developed within this work follow these guidelines. Detailed workflows are described in the following sections.

6.1.2.1 Workflow

Similar to the GetFeature model the RequestResponse pattern is applied. Though, four Permdelta + Correction respectively two Tempdelta requests have been posted to the WFS within one test cycle. Figure 4 illustrates the workflow of the transactional model. Copyright © 2012 Open Geospatial Consortium. 11 Figure 4 - WFS Transactional Model Workflow.

6.1.2.2 Parameters

The parameters of the inserted features are generated using an internally developed algorithm based on randomization of textual patterns. Thus, the user needs to provide a limited set of parameters. These are described in the following table. Parameter Description Default Value Testing Period The overall time of model execution in minutes. The model performs a check after execution cycle if it has exceeded the testing periods. 1440 = 1 day Request interval Defines the time in seconds the tool will wait after successful execution of a test cycle before starting the next. 40 Maximum Response Time Similar to the ES models this parameter defines a threshold. If it is exceeded the request is considered as overdue. Note: this parameter is currently not taken into consideration in the evaluation. 5

6.1.2.3 Evaluation

The evaluation of the Transactional model is in similar to the GetFeature model evaluation. It differs as the number of requests differs for a single test cycle. For the insertion of PermdeltasCorrection four requests 1 commissioning, 1 correction, 2 cancellations are needed, the insertion of a Tempdelta creates two requests 1 insertion,