OSGi bundling of OGC service components. The relevant service components need to OGC component integration with SAA SWIM services. Several potential approaches to Use of OGC components to directly access FAA data stores. Rather than creating local FAA st

2 Copyright © 2011 Open Geospatial Consortium.

1.4 Future work

The following future work items for the use of OGC-based components for SAA data dissemination have been identified in the conduct of this study:

1. OSGi bundling of OGC service components. The relevant service components need to

actually be deployed on the same FUSE Enterprise Service Bus ESB. This may require the re-engineering of existing component software. Section 8.12 provides more details on the Open Services Gateway initiative OSGi and FUSE ESB integration results as well as issues identified by the Pilot Study participants.

2. OGC component integration with SAA SWIM services. Several potential approaches to

OGC service interoperability with SAA SWIM services could be explored to facilitate transition of SWIM clients to the use of OGC Web Services. Existing service adapters could be modified to exchange messages with the SWIM services, and stored queries in the WFS could be used to present an OGC-standard facade for SWIM service operations,

3. Use of OGC components to directly access FAA data stores. Rather than creating local

copies of SAA data, the WFS and Event Service components could be adapted to use data from existing FAA repositories

4. FAA standards for SAA data portrayal. Depending on the user role, such as military

versus civilian flight planner, the client software could use Style Registry metadata to present customized formats to facilitate visual recognition of the feature properties and status.

5. Use of Style Registry to customize cross-section display content. The WPS used for the

Envitia client currently does not support parsing an SLD to govern how the cross-section image is styled.

6. Automation of business rules for SAA dissemination in AIXM 5.1. Schematron

expressions could be used to guard the integrity of AIXM-format messages that use SAA schema extensions, and to enforce constraints and conventions for timesheet usage. This would entail business rule development, test and integration with the OGC services.

7. Event Service enhancements. A dedicated getServerStatus operation, rather than