Architecture
Total Page:16
File Type:pdf, Size:1020Kb
OGC® Open Geospatial Consortium Technology Office 4899 North Old State Road 37 Bloomington, IN 47408 Telephone: +1-812-334-0601 Facsimile: +1-812-961-2053 Request For Quotation and Call For Participation In the OGC Web Services 4 Initiative Initial Operating Capability and Demonstration Annex B: OWS-4 Architecture RFQ Issuance Date: April 11, 2006 Proposal Due Date: May 5, 2006 Due Date: May 5, 2006 Annex B: OWS-4 Architecture TABLE OF CONTENTS ANNEX B: OGC WEB SERVICES 4 (OWS-4) - ARCHITECTURE .................................................. 3 1 OVERVIEW ....................................................................................................................................... 3 2 OWS-4 THREAD SUMMARIES ..................................................................................................... 3 3 OWS-4 TECHNICAL BASELINE ................................................................................................... 7 3.1 OPENGIS REFERENCE MODEL ...................................................................................................... 7 3.2 OPEN GEOSPATIAL CONSORTIUM TECHNICAL BASELINE .............................................................. 8 3.3 OTHER STANDARDS RELEVANT TO OWS-4................................................................................... 9 4 OWS-4 ARCHITECTURE................................................................................................................ 9 4.1 SENSOR WEB ENABLEMENT (SWE) .............................................................................................. 9 4.2 GEO PROCESSING WORKFLOW (GPW)........................................................................................ 25 4.3 GEO-DECISION SUPPORT SERVICES (GEODSS)........................................................................... 43 4.4 GEODRM AND TRUSTED GEOSERVICES...................................................................................... 56 4.5 CAD/GIS/BIM ........................................................................................................................... 75 4.6 OGC LOCATION SERVICES (OPENLS)......................................................................................... 90 4.7 COMPLIANCE AND INTEROPERABILITY TEST AND EVALUATION (CITE) ..................................... 96 APPENDIX A: OWS 4 REFERENCES TO OTHER STANDARDS .............................................. 105 APPENDIX B: SCENARIO NARRATIVE ......................................................................................... 109 APPENDIX C: SENSOR WEB USE CASES ...................................................................................... 113 APPENDIX D: ACTM DATA DICTIONARY ................................................................................... 122 Page 2 Due Date: May 5, 2006 Annex B: OWS-4 Architecture Annex B: OGC Web Services 4 (OWS-4) - Architecture 1 Overview The architectures presented in this Annex are based upon a collaborative effort between OGC Web Services 4 (OWS-4) Sponsors and OGC’s IP Team. The architecture team used results from previous and ongoing OGC Interoperability Program initiatives, existing OGC discussion papers and specifications, OGC Technical Committee activities, and publicly available documentation from related standards initiatives and elsewhere. Section 2 provides an overview of the OWS-4 development threads. Section 3 discusses the architectural approach and technical baseline for OWS-4. Section 4 discusses the architectural approaches and issues for each of the OWS-4 development threads. Appendix A contains key references applicable to this RFQ. Appendix B is a description of a fictitious scenario that is to be used in support of the Sensor Web Enablement thread of OWS-4. Appendix C contains a set of Sensor Web scenarios. The OGC portal provides a Glossary of Terms at the following URL that may be useful to aid in understanding and interpretation of terms and abbreviations contained throughout this RFQ: http://www.opengeospatial.org/resources/?page=glossary 2 OWS-4 Thread Summaries OGC’s Interoperability Program is a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate specifications into OGC’s Specification Program, where they are formalized for public release. In OGC’s Interoperability Initiatives, an international team of technology providers’ work together to solve specific geo-processing interoperability problems posed by the initiative’s sponsoring organizations. OGC Interoperability Initiatives include test beds, pilot projects, interoperability experiments, and interoperability support services – all designed to encourage rapid development, testing, validation and adoption of open, consensus based standards specifications. In the Fall of 2005, the OGC issued a call for sponsors for an OGC OWS-4 Interoperability initiative testbed activity to advance OGC’s open framework for interoperability in the geospatial industry. Three meetings were conducted with potential OWS-4 sponsors to review the OGC technical baseline, to discuss OWS 3 results, and to identify OWS 4 requirements. Sponsors have expressed keen interest in advancing standards for sensor webs, geospatial digital rights management, geospatial semantics and knowledge management. After analyzing the sponsors input, the OGC Interoperability Team recommended to the sponsors that the content of the OWS-4 initiative be organized around the following 7 threads: 1) Sensor Web Enablement (SWE) 2) Geo Processing Workflow (GPW) 3) Geo Decision Support (GeoDSS) 4) Geo-Digital Rights Management (GeoDRM) 5) CAD / GIS / BIM 6) OGC Location Services (OpenLS) 7) Compliance Testing (CITE) Page 3 Due Date: May 5, 2006 Annex B: OWS-4 Architecture An introduction to these 7 threads is described below, followed by a detailed discussion of the architectural implications of the initiative threads. 2.1 Sensor Web Enablement (SWE) The Sensor Web subtask will continue to mature the existing set of SWE work items to enable the federation of sensors, platforms and management infrastructure into a single sensor enterprise. This enterprise will enable the discovery and tasking of sensors as well as the delivery of sensor measurements regardless of sensor type and controlling organization. The ultimate vision is of a sensor market place where users can identify, evaluate, select and request a sensor collection regardless of sensor type, platform or owner. Emphasis for SWE during this phase of the OWS project will be on: • Leveraging results of OWS-3 and SAS IE initiatives to refine, extend and integrate those specifications and implementations. • Developing examples of SWE Information Model schema elements (i.e., O&M, SensorML, TransducerML and SWE Common) for specific classes and uses of observation offers, phenomena, sensor systems, processes and transducers. • Harmonizing SWE concepts and specifications with other OGC specifications and initiatives. • Harmonizing SWE concepts and specifications with other complementary initiatives moving forward by other organizations, including IEEE, OASIS and US Government agencies and programs. • Demonstrating support for realistic operational scenarios per the SWE Enterprise Viewpoint and Use Cases. In OWS-4, emphasis of interoperability engineering activities for the SWE thread will be on integration and demonstration of physical sensors and simulators within a realistic operating environment. In addition, progress is expected on enhancements to the SWE specifications as described in the “Future work” clauses of the respective baseline documents. 2.2 Geo Processing Workflow (GPW) The Geo-Processing Workflow (GPW) thread will develop and demonstrate how to interconnect geo- processes through publish-find-bind and service chaining to meet workflow requirements. The result will be the creation of valued-added enterprise systems that demonstrate the power of interoperability and service-oriented architectures. The OWS-4 GPW thread brings together developments from several previous initiatives. The planned activities for GPW: • UML and GML3.2 application schema development • Producer to Customer Production Workflow • SWE Geo-processing Workflow • Catalog Services for OWS-4 Page 4 Due Date: May 5, 2006 Annex B: OWS-4 Architecture 2.3 Geo Decision Support (GeoDSS) Geo-Decision Support Services (GeoDSS) provide interoperable access to distributed geospatial web services to aid decision makers in forming, analyzing, and selecting alternatives. GeoDSS utilizes workflow management to produce context-specific results from information and knowledge from multiple communities. The GeoDSS subtask will extend the Decision Support and the Information Interoperability work done in OWS-3 to include multilingual interoperability and compressed GML data. Enhanced decision support using information provided from an increasingly wide variety of services places more demands on the ability of the user client software. The GeoDSS thread will develop and demonstrate client programs that will integrate many services, provide stand-alone relatively light-weight open-source GML visualization and 3D CAD visualization. Each of these clients offers an opportunity to exploit the wide variety of data for decision support. The planned activities for GeoDSS: • Portrayal • GeoDSS Clients • Coverage Portrayal Service • Multilingual services • WFS-Files and WFS-Database • WMS Tiled 2.4 Geo Digital Rights Management (GeoDRM) GeoDRM or Geospatial Digital Rights Management is defined