2 Copyright © 2011 Open Geospatial Consortium,
Inc. All Rights Reserved.
1.2 Document contributor contact points
All questions regarding this document should be directed to the editor or the contributors:
Name Organization
Costantino Saponaro Luca Giallombardo
IDS Daniel Tagesson
Carmenta David Burggraf
Galdos Debbie Wilson
Snowflake Jan Hermann
TUM Jeroen Dries
Luciad Jérôme Jansou
AtoS Jim Groffen
Lisasoft Johannes Echterhoff editor
iGSI Matthes Rieke
IfGI Nadine Alameh
OGC Rob Atkinson
CSIRO Simon Cox
CSIRO Simon Merrick
Envitia Thibault Dacla
Atmosphere Timo Thomas
Ulrich Berthold Comsoft
Yuqi Bai GMU
Zdenek Farana Frequentis
1.3 Revision history
Date Release
Editor Primary
clauses modified
Description
2011-08-24 0.1
Johannes Echterhoff
all initial word version
2011-09-09 0.2
Johannes Echterhoff
throughout integrated a number of contributions and
completed various sections 2011-09-30
1.0 Johannes
Echterhoff throughout
final version
Copyright © 2011 Open Geospatial Consortium,
Inc. All Rights Reserved.
3
1.4 Future work
The following items were identified for consideration in future initiatives:
Data validation via WPS - The work performed on validating the Digital
NOTAM Event Specification DNES revealed that integrating a validation tool to check DNOTAM business rules on given dnotam:Event instances into the
Aviation service infrastructure can be facilitated by encapsulating the validation process in a web service.
Development of a WPS profile for validation of XML instances against their respective schema and possibly existing business rules appears to be a valuable
effort - not only for the Aviation domain but also for the general OGC community - see future work item “Invocation of validation tools” in the DNOTAM ER for a
more detailed discussion of this idea
Testing and integration of automatic unit of measure conversion functionality - Automated UoM conversion as described in section 10.3 would
improve the filter capabilities of OGC Web Services. Especially when the UoM of a feature property is not constant, the mechanism helps to perform meaningful
comparison operations. The discussion performed in OWS-8 on this topic did not cover all relevant aspects see section 10.3 for further details. Therefore, a future
activity should further develop the automatic UoM conversion mechanism, integrate it into actual OGC Web Service implementations like WFS and Event
Service that support OGC Filter Encoding Specification and test it. Eventually, the mechanism can then be integrated in or become an extension of the OGC
Filter Encoding Specification.
Investigate, improve and provide guidance on service bootstrapping – During
OWS-8 participants made experience with bootstrapping of SOAP based web services. Apparently there is a need for additional experience and guidance both
for web service providers and clients on bootstrapping to such services. While the traditionally used OGC service bindings – HTTP GET KVP and HTTP POST –
are sufficiently described via an OGC service’s Capabilities document, this is not the case for SOAP based web services. Here, the WSDL document provides
additional information that has not been considered for an OWS Capabilities document such as SOAP version and operation action identifiers. Section 10.2.2
explains the issue and possible solutions in more detail. Future work should consider testing the various options with different types of
OGC web services and generic clients. Guidance should be developed regarding the way that clients can readily start interacting with a SOAP based OGC web
service and also the information that needs to be contained in the metadata of that service. Ultimately, this work would help integrating and using OGC services –
but also clients that want to interact with these services – in environments that apply standards and technologies from the more general IT world. Such an
environment would be, for example, an Enterprise Service Bus ESB with OGC
Kategori