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
4 Copyright © 2011 Open Geospatial Consortium,
Inc. All Rights Reserved.
services deployed on it. Work on SOAP and WSDL for OGC Web Services has been performed in
previous OGC initiatives see OGC 08-009r1. This work should be reviewed and updatedextended to take into account IT standards such as WS-Addressing,
WSDL 2.0 and the WS-I BasicProfiles.
Temporality Model as standalone specification and better support for time varying data in OGCISO standards – The AIXM Temporality Model defines
encoding as well as business rules that enable applications to keep track of time varying data, in this case of AIXM features and their properties. Refactoring the
Temporality Model into a standalone specificationstandard would be beneficial for the following reasons: a enable re-use of the concepts defined by the
Temporality Model in other domains that deal with time varying data, b improved maintenancegovernance of the Temporality Model itself, c improved
interoperability and usability when handling and managing time varying data via web services. Section 10.1.6 explains this in more detail. The ideas and
suggestions presented in that section should be considered in the future. Improved usability and interoperability in model design and encoding as well as
management and access of time varying information are key benefits of the suggested refactoring. Section 10.1.6 also outlines how this could be achieved by
revisingextending a set of OGC and ISO standards.
Aviation Event Architecture
o
Dynamic spatial filtering – Future work on the dynamic spatial filter
Kategori