OGC Requests

Request for Comment on Image Geopositioning Service (IGS)

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS Image Geopositioning Service (IGS). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Image Geopositioning Service (IGS) Draft Implementation Specification defines an Image Geopositioning Service (IGS) interface to services that perform triangulation. (NOTE: The name of this service has not yet been formally agreed upon.) Accompanying this draft specification is a separate OpenGIS Image Geopositioning Metadata Geography Markup Language (GML) Draft Application Schema, which is structured to provide consistency between the IGS and other OGC Web Services (OWS) specifications.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for the IGS. Documentation of this draft specification can be downloaded below:

Candidate Submission: Thur, 2007-03-22
TC and PC vote to issue request: Fri, 2007-04-20
Begin request period: Tue, 2007-05-15
Close request period: Thu, 2007-06-14

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

Request for Comment on Geospatial eXtensible Access Control Markup Language (GeoXACML)

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called Geospatial eXtensible Access Control Markup Language (GeoXACML). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Geospatial eXtensible Access Control Markup Language (GeoXACML) Draft Implementation Specification (OGC Document 07-026) defines a geo-specific extension to the eXtensible Access Control Markup Language (XACML) OASIS standard. "Access control systems" enable management of access to information only until it is obtained by the user and stored locally, as opposed to "rights management systems" that remain in force regardless of where the content of the original resource is located or reproduced.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for GeoXACML. Documentation of this draft specification can be downloaded below:

Candidate Submission: Thur, 2007-03-22
TC and PC vote to issue request: Fri, 2007-04-20
Begin request period: Tue, 2007-05-15
Close request period: Thu, 2007-06-14

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

OGC Web Services, Phase 5 (OWS-5) Request For Quotation and Call For Participation

Status: 
This Request is Closed.
Description: 
RFQ Issuance Date: 11 May, 2007
OWS-5 Bidder's Conference: 22 May, 2007
Proposal Due Date: 8 June, 2007

 


Overview

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 January of 2007, the OGC issued a call for sponsors for an OGC OWS-5 Interoperability initiative testbed activity to advance OGC's open framework for interoperability in the geospatial industry. Three meetings were conducted with potential OWS-5 sponsors to review the OGC technical baseline, to discuss OWS-4 results, and to identify OWS-5 requirements. Sponsors have expressed keen interest in advancing standards for geospatial workflow, sensor webs, geospatial digital rights management, GML information communities, and KML. After analyzing the sponsors input, the OGC Interoperability Team recommended to the sponsors that the content of the OWS-5 initiative be organized around the following 6 threads:

  1. Sensor Web Enablement (SWE)
  2. Geo Processing Workflow (GPW)
  3. Information Communities and Semantics (ICS)
  4. Agile Geography
  5. Compliance Testing (CITE)
  6. CAD / GIS / BIM

Introductions to these 6 threads are below.


OWS-5 Sponsors

  • BAE Systems - Network Systems
  • Google
  • Lockheed Martin Integrated Systems & Solutions
  • Northrop Grumman
  • US National Aeronautic and Space Administration (NASA)
  • US National Geospatial-Intelligence Agency (NGA)

OWS-5 Threads

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. In OWS-5,interoperability engineering activities will focus 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.

Emphasis for SWE during this phase of the OWS project will be on:

  • Leveraging results of OWS-4 to extend and integrate those specifications and implementations.
  • Demonstrating SWE's ability to meet the geospatial needs of large enterprise system by integrating SWE into realistic enterprise workflow scenarios supported by Use Cases.
  • Continuing previous test-bed efforts to integrate IEEE 1451 sensor into SWE
  • Establishing cross thread collaboration with CGB by integrating sensors into 3D models.
  • Harmonizing SWE concepts and specifications with other OGC specifications and initiatives.
  • Developing compliance test for SWE specification to accelerate adoption

2) Geo Processing Workflow (GPW)

No geo-process is an island, or more exactly no geo-process should be an island. By interconnecting geo-processes through service chaining and orchestration to meet workflow requirements, creation of valued-added enterprise systems is possible that demonstrate the power of interoperability and service oriented architectures. The OWS-2 Image Handling for Decision Support (IH4DS) thread extended the baseline of OWS service types with image processing services. OWS-3 Common Architecture activities built on that work by applying the services developed in OWS-2 to the SWE and GeoDSS environments. OWS-4 furthered workflow service development by investigating the patterns for building general purpose geo-processing services and prototyping a feature editing scenario.

OWS-5 will further mature geoprocessing workflows by bringing together more services in real-world image processing scenarios, developing a SOAP/WSDL framework for all OGC services, and incorporating rights-based access to resources. The GPW thread in this testbed is organized into the following inter-related work areas:

  • Enterprise integration and refinement of OGC Web Service architecture
  • Enterprise integration of OGC Web Services using service chaining and workflow to implement the full service life cycle for the Publish-Find-Bind pattern
  • Integrate GeoRM services and components in the workflow with focus on Identity, Authorization, Authentication and Trust model

3) Information Communities and Semantics (ICS)

The ICS thread seeks to advance the understanding and use of complex geographic information types within an interoperability architecture. A variety of geospatial data types will be modeled in UML and converted into GML using the UGAS ShapeChange tool. Information about these data and the services provisioning them will be registered in a number of catalogs and utilized in workflows developed in the GPW thread.

This activity will test the ability of OGC standards to facilitate one of the core scenarios in any spatial data infrastructure-information publication.

4) Agile Geography

This testbed focuses on process integration and ‘right-sizing' of services to demonstrate the power of interoperability and service-oriented architectures using OGC Web Services. The Agile Geography thread explores this goal through two distinct activities.

The first explores the future of KML, OWS Context, and lightweight payloads of geospatial information on the Web in general, applying the concepts of links, bookmarks and Web pages to digital cartography and geospatial information management. Participants will explore the harmonization of KML and OWS Context XML encodings and prototype client and server software that exploits these document types.

The second activity-GeoSynchronization and Sharing-extends the WFS-Transactional architecture to target a federated environment comprised of loosely affiliated parties who desire to collaborate, in full or in part, on the maintenance of a shared geospatial data set.

5) Compliance Testing (CITE)

The OGC Interoperability Program and the OGC Specification Program have achieved a great deal of momentum as a result of the multiple OGC Web service specifications that have recently been published. Key consumers in the geospatial industry are modernizing their enterprises and realizing spatial data infrastructures (SDIs) based on the applicability and interoperability of OGC web services.

The major geospatial industry consumers require verifiable proof of compliance with OGC specifications in order to reach the desirable outcome of interoperability. In OWS-5 the CITE thread advances testing for Web Coverage Service and Catalog Service for the Web to versions 1.1 and 2.0.2 respectively. OWS-5 also initiates Sensor Web compliance testing, with the first Sensor Observation Service and Sensor Planning Service tests.

Also included in the requirements are reference implementations of these specifications. A reference implementation is an open source, fully functional implementation of a specification in reference to which other implementations can be evaluated. The OGC provides open source reference implementations to ensure maximum transparency of its specifications for both vendors and customers.

6) CAD / GIS / BIM (CGB)

NOTE: Work items within the CAD/GIS/BIM thread are provided for comment -- with the anticipation that CGB will be conducted in Phase 2. Comments on CGB are solicited now to support a future RFQ/CFP for Phase 5.2 as defined in Master Schedule.

The CGB activities in the OWS program are directed toward bridging the information models and workflows of the various communities involved with the representation of the built environment in three dimensions. Standards for interoperable exchange of information about buildings and standards for representing and exchanging information about cities at broad-scale are beginning to enable owners, administrators and toolmakers to make investments in developing assets based on these standards. Applications of integrated city models are emerging in the mass-market sphere, witness Google Earth and Microsoft Local Live. One can imagine the extension of these tools into the domains of location-based services to emergency preparedness and response. These applications will require the integration of semantically rich authoritative information that is likely to be created in a highly distributed fashion. This thread of OWS-5 focuses on developing a services-based architecture that will bring the necessary information together, and to make it accessible in a secure way.

Downloads: 

Proposals for cost reimbursement are due by June 8, 2007.

Click a link to download the .zip archive:
DOWNLOAD COMPLETE PACKAGE
Complete OGC Web Services, Phase 5 (OWS-5) RFQ (zip format)

OGC Web Services, Phase 5 (OWS-5) Bidder's Conference Information


A Bidder's Conference is currently scheduled for May 22.
Time: 15:00 UTC, 5:00 PM CEST, 11:00 AM EDT, 8:00 AM PDT
Phone line: +1 512-225-3050 passcode:36429#.

Clarifications to OWS-5 RFQ/CFP

The following clarifications apply to the Request for Quotation/Call for Participation in OGC Web Services, Phase 5 (OWS-5) as issued on 11 May 2007. This list will be updated as additional clarifications are needed. The most current list will always be posted here:

Download OWS-5 RFQ/CFP Clarifications

 


OGC Requests: 

Architecture Implementation Pilot Call for Participation (CFP)

Status: 
Please note: The submission period for this request is closed.
Description: 

CFP Issuance Date: 18 April 2007
Response Due Date: 11 May 2007
Pilot Kickoff Meeting: 5-6 June 2007

This Call for Participation (CFP) seeks participants in a coordinated Geospatial Architecture Implementation Pilot. A Pilot is a collaborative effort that applies open standards for interoperability to achieve user objectives in an environment representative of operational use. Outcomes include best-practices and interoperability arrangements suitable for an operational capability. An aim of the Pilot is to reach consensus on architectural elements that initiatives supporting geospatial information systems can carry forward into operations, thereby increasing the overall level of interoperability.

This CFP seeks proposals from organizations involved with Earth Observation systems to:

  • Identify components with services, e.g., portals, catalogs and other services;
  • Participate in confirming the interoperability of those identified services using standards and interoperability arrangements as identified in the preliminary architecture of this CFP; and,
  • Participate in the collaborative development of societal benefit scenarios to guide testing and demonstrations of the identified interoperable services.

Organizations responding to the CFP should plan to fully participate in the Pilot development activities beginning with the Kickoff Workshop.

The CFP was initiated to solicit response for the GEOSS Architecture Implementation Pilot identified by the GEOSS Architecture and Data Committee as an essential step in moving forward to an operational capability. The Pilot aims to incorporate contributed components consistent with the GEOSS Architecture - using a GEO Web Portal and a GEOSS Clearinghouse search facility - to access services through GEOSS Interoperability Arrangements in support of the GEO Societal Benefit Areas. The GEO Task AR-07-02 will conduct this pilot consistent with the request of the GEO Plenary.

Interest in the Geospatial Pilot has already been expressed by two other organizations which have offered their pilots for collaboration with GEOSS. In the interest of providing a broad assessment of capabilities, the collaboration of these pilots provides opportunities to address interoperability on a broad scale. The Pilots are:

  • The Tri-Lateral Interoperability Pilot is a collaborative, open standards development, supporting collective requirements of organizations responsible for national and regional "Spatial Data Infrastructures" in Europe (INSPIRE), Canada (GeoConnections), and the U.S.A. (FGDC)
  • The Federated Earth Observation Missions (FedEO) Pilot provides a broad international venue for operational prototyping and demonstration of Earth Observation (EO) requirements and protocols as defined by the European Space Agency (ESA), together with other space agencies (ASI, CNES, CSA, DLR) and users (EUSC) and other OGC members.
OGC Requests: 

Canadian Geospatial Data Infrastructure Interoperability Pilot (CGDI IP): Request For Quotation And Call For Participation

Status: 
Please note: The submission period for this request is closed. Clarifications have been issued.
Description: 

The Open Geospatial Consortium (OGC) is releasing a Request For Quotation and Call for Participation (hereafter referred to as RFQ/CFP) to solicit your proposal in response to a refined set of requirements for the CGDI Interoperability Pilot. This request is issued as an RFQ/CFP for two reasons. The first reason is that GeoConnections as sponsor is providing cost-sharing funds to offset expenses uniquely associated with the initiative. The second reason is that GeoConnections and OGC intend to involve as many participants in the initiative as possible and thus are soliciting contributory proposals that will enhance and/or make use of the initiative outcomes.

Candidate Submission: Tue, 2007-04-10 12:00
Close request period: Wed, 2007-05-02 23:59

CGDI Interoperability Pilot Overview

 

Clarifications have been issued. updated: 2007-04-27 10:25:24

 

Background

One of the tenets of the CGDI is the widespread dissemination of data which is at the same time managed at or near its source. Late in 2005, GeoConnections commissioned AMEC of Oakville, Ontario to investigate the use of technology based on the Open Geospatial Consortium's Web Feature Service (WFS) standard to better meet this objective. Recommendations made in the ensuing AMEC 2006 report, "Web Feature Services, Considerations for CGDI Government Partners" included taking primary steps to properly adopt and effectively use WFS within the CGDI.

In spring of 2006 some CCOG members approached GeoConnections about enhancing their current services in order to provide framework data to GeoBase within a distributed computing environment. As a follow-up to the AMEC report and CCOG requests, GeoConnections then invited CCOG and IACG members to participate in a pilot project to assess the opportunities afforded by WFS technology to improve the management and dissemination of CGDI data.

Objectives and Benefits

The renewed GeoConnections program is primarily focused on both enhancing and applying the CGDI. This opportunity for working in collaboration with the provincial partners will test better mechanisms for the distribution and updating of framework data, providing users with access to the most current and authoritative data, avoiding version disparities, and minimizing duplication.

Provincial partners have communicated interest in establishing WFS as a standard for providing wide access to data from distributed locations closest to their source. As source data providers for GeoBase framework data, provincial stakeholders will receive assistance with the implementation of onsite WFS components both in a technical and business sense. Assistance will be made available in the form of financial contributions for labour, software, and data publishing. This will allow providers to maintain control over the data they own while contributing at the same time to a national view of that data. Project results will aid CCOG members in planning the future production implementation of a distributed architecture for GeoBase data management and distribution.

Data users require authoritative geospatial information, accessible directly from as close as possible to its source, in order to make timely and effective decisions. Evolving the GeoBase portal to operate in a more distributed fashion and making maintenance transactions more efficient will help to meet those user requirements. Such GeoBase improvements will be realized through the development of partnerships, data standards and encouragement of sharing. Working with data providers to improve the maintenance of GeoBase framework data is a particular priority for GeoConnections.

Private sector technology providers will be brought into the project through a competitive process. They will assist the project partners in the deployment of the WFS technology.

Scope

This project proposed by GeoConnections in conjunction with CCOG members will focus on three vector-based data themes:

  • Geographic Name;
  • National Road Network;
  • Administrative Boundaries;

The functional scope of this project includes investigations in the following areas:

  • Access by users to closest-to-source data
  • Transactional updates exchanged between data suppliers and GeoBase
  • Use of a distributed services architecture to support performant end-user online applications

The project will include participants from provincial and federal agencies and from the private sector. Agencies will participate at different levels, some will work with private sector partners while others will use their existing infrastructures to provide access to manage and disseminate data. The information gained during the execution of this project will benefit all project participants as well as the broader CGDI community.

Schedule

Discussions with potential project partners for this project were initiated in the second half of 2006. A contract with Open Geospatial Consortium, Herndon, Va., to provide technical management and architecture support was initiated in January 2007. Refinement of the requirements and the Project Concept document is completed in March 2007 and the competition to select industrial partners will be completed by May 2006. The technology deployments will be complete by October 2007 and this will be followed by a 6 month pre-operational phase.

 

Clarifications have been issued.

 

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
OGC Requests: 

Observations and Measurements: Request for Public Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called Observations and Measurements. OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for Observations and Measurements. Documentation of this draft specification can be downloaded here:

Candidate Submission: Tue, 2006-11-07 14:00
Close request period: Thu, 2007-03-08 14:00
TC and PC vote to issue request: Fri, 2006-12-15 14:00
Begin request period: Tue, 2007-02-06 14:00

 

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

Gazetteer Profile of WFS: Request for Public Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called Gazetteer Profile of WFS. OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Application Profile of the OpenGIS Web Feature Service (WFS). The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for Gazetteer Profile of WFS. Documentation of this draft specification can be downloaded here:

Candidate Submission: Mon, 2006-06-05 14:00
Close request period: Thu, 2006-08-24 14:00
TC and PC vote to issue request: Fri, 2006-06-30 14:00
Begin request period: Tue, 2006-07-25 14:00
 

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

OGC Request for Information on "Contextual State Description" Services

Status: 
Please note: This Request is closed.
Description: 

Introduction

With this Request for Information (RFI), The Open Geospatial Consortium Inc. (OGC) is soliciting input on technologies related to Contextual State Descriptions (CSD).  A CSD describes the "environment" or context in which a service chain executes. The objective of this request is to identify existing capabilities that can provide a robust metadata foundation for supporting agile, adaptive, autonomous processes capable of producing repeatable, predictable results with no intervention.

In August, 2004, the Open Geospatial Consortium Inc. (OGC) issued a call for sponsors for an OGC Web Services 3 (OWS-3) interoperability initiative, a multi-threaded test bed activity to advance OGC's open framework for interoperability in the geospatial industry.  Key Components of OWS-3 will Sensor Web Enablement (SWE) and Service Chaining.  Each of these components are described below followed by some potential uses for CSD in OWS-3.

Organizations with relevant technology regarding CSD are urged to respond to this RFI. Information on how to respond are at the end of this RFI.  The contents of the OWS-3 request for quotations (RFQ) will be based in part on the RFI response to the CSD RFI.

 

Sensor Web Enablement and OpenGIS SensorWeb™

A key component of OWS-3 will be Sensor Web Enablement (SWE), in which OGC members are developing standard interfaces and encodings that will enable real time integration of heterogeneous sensor webs into the information infrastructure. Developers will use these specifications in creating applications, platforms, and products involving web-connected devices such as flood gauges, air pollution monitors, stress gauges on bridges, mobile heart monitors, Webcams, and robots as well as space and airborne earth imaging devices. Several elements of SWE have already been developed and are being finalized before they are submitted to the OGC membership for adoption. CSD is a potential new element of SWE.

OWS-3 will combine the previous work on SensorWeb with the OWS-2 Image Handling and Decision support results to provide automated workflow management to produce value-added products. SensorWeb is the source of tremendous amounts of geospatial data, e.g.,  in-situ, imagery and simulation data.  The Decision Support component of OWS-3 will continue the work of OWS-2 Service Chaining to produce value-added information products derived from SensorWeb data.

 

Using CSD for Service Chaining

A major thrust of OWS-2 was Image Handling for Decision Support. The Image Handling component of OWS-2 increased the ability to access and process geographic imagery into value-added products using open web services.  The Decision Support component of OWS-2 demonstrated automated service chaining of imager processing services.  This automation was achieved with an emerging open specification of workflow management: BPEL.

This RFI seeks input on the technology related to Contextual State Descriptions (CSD).  A CSD could describe the "environment" or context in which a service chain "executes". A well-characterized service chain or workflow derives a repeatable result given equivalent sources, methods, and processing state or context.  A workflow script defines the order of service invocation in a service chain but the details of the services are hidden behind the web service interface. A CSD provides information about the distributed processing environment and resources that are hidden behind the interfaces.  A CSD is specifically designed to address environmental state descriptions, in such a manner that an equivalent state can be recreated at some future point to provide identical, repeatable results from a specified process, assuming identical sources, services and scripting are utilized.

When workflows are manually executed and interpreted, complexity can be addressed through human intuition and experience.  However, in an autonomous environment, complexity must be distilled into codified states, before business logic can be characterized to facilitate autonomous processing with any level of confidence.  Thus, a CSD is specifically designed to facilitate the autonomous processing of complex workflows in a predictable, repeatable fashion.

The promise of complex autonomous processing is the increased productivity of end user "analysts" that presently focus an inordinate amount of their time preparing data instead of analyzing it.  Thus, the transition of data into information into knowledge into some form of decision or course of action is largely still a manual process that cannot be reliably repeated.  True autonomous processing will not determine the ultimate course of action from a workflow, but can relieve the analyst from having to manually shepherd data through this workflow process, freeing them to focus on interpreting the derived knowledge into alternative courses of action in less time than the current process requires to develop a single course of action manually.

CSD does not describe the workflow business logic, but the contextual state that the workflow executes within.  Thus, the CSD would describe the systems configuration, the hardware configuration, the firmware used by each device, the operating system, including patches, the software configuration, including external dependencies (shared libraries), and any data.  All of this information characterizes the operational state or context of the system. Any change in this contextual state may result in discrepancies when the workflow is re-executed.

 

Potential use for CSD in OWS3

OWS-3 will apply service chaining to enable use of SensorWeb technologies for decision support.  This technology will allow sensor measurements and modeling predictions to be processed into higher-value information specific to a given decision making context.  CSD may be used to capture the state of the service chain including the SensorWeb components and the geo-processing services and the workflow management components.  Capturing this information in a CSD will allow for post-processing analysis of the decision support information.

For instance, this initiative could describe each of the sensor components of the current SensorWeb, as well as a corresponding set of metadata to describe the processing chain.  Quality metrics embedded within the data stream can describe the resultant accuracies associated with any point in the stream.  However, when a degraded signal is recorded within the sensor stream, there is no context to interpret the cause and effort on the resulting value-added information.  The CSD associated with this process could describe the environmental context or state that the SensorWeb was operating within to illustrate the reason for the degraded decision support information.

Due to the potential iterative nature of CSDs, a normalizing relationship structure must be provided to "relate" voluminous descriptive metadata references, without requiring these references to be redundantly embedded within a single CSD.  Several compelling technologies and standards currently exist to address these specific issues.  The net result of an CSD-enabled workflow would be a greater understanding of the situational context present when the SensorWeb was captured.  These concepts are not new and have often been referred to as "fusion", multi-INT/multi-Source, and/or horizontal integration.

CSD could be applied to the OWS-2 Image Handling results including automated image orthorectification.  In OWS-2, the orthorectification was accessible by a single web service request without exposing the underlying processing hardware.  While retaining this simple web service interface, CSD could be used to capture a description of the underlying processing environment.  For example, orthorectification may be performed by a cluster-based computing task with the processing load distributed across all available nodes in the cluster.  Depending upon the load on the system, the number of nodes available during processing time, the system resources allocated to each node and the system, the methods and availability of source materials (raw imagery and control information), and the business logic applied to the process (tiling inputs, parallel vs. serial processing, types of control applied), the resultant orthorectified images will be created with varying degrees of accuracies and latencies.  Once sufficiently populated, these accuracies and latencies (CSDs) can be mined to support the development of an adaptive system, whereby an orthorectification request can be fulfilled based on the degrees of freedom provided by varying the accuracies or latency in the fulfillment of this request.

 

Objective Requirements

The objective of this RFI is to identify existing capabilities that can provide a robust metadata foundation for supporting agile, adaptive, autonomous processes capable of producing repeatable, predictable results with no intervention.  These objectives are purposely abstracted to describe a wide variety of processes or workflows, beyond just computer system processes.

A CSD shall describe the contextual state of a process or workflow. The structure of a CSD shall be such that a subsequent re-execution of a specified process will generate equivalent results, assuming the state from which the original process executed can be faithfully replicated.  A CSD shall be capable of relating or referencing other external processes, services, or data as part of a contextual state.  External references embedded within a CSD should not require the inclusion of the full reference, but rather a form of relation that will support normalized, iterative references.  CSD shall not be explicitly tied to computer system processes or workflows, but must support a much broader, abstracted description of a process and/or workflow.

CSD is information, i.e., metadata, about the processing environment. OGC has adopted and implemented ISO 19115:2003, Geographic Information - Metadata in OGC Abstract Specification, Topic 11 - Metadata. While ISO 19115 is primarily for the description of datasets, it includes metadata to describe the processing history of a dataset.  While the objectives of CSD exceed the elements in ISO 19115, CSD implementations must utilize elements of ISO 19115 when appropriate in lieu of defining new terms for the same concept.

Methodologies need to be developed to couple CSDs with processes and workflows as logical metadata structures.  Methodologies need to be provided to extract the contextual state from a system, process or workflow and codify that state within a specified CSD. Additional methodologies need to be provided to extract a contextual state from a CSD to reconfigure (to the extent physically possible) a described system capable of re-executing the process or workflow associated with the CSD.  Methods need to be developed that can identify and codify the differences between two CSDs, forming the basis for determining whether two CSDs are essentially equivalent.  A CSD shall be capable of being described in a service context that will facilitate autonomous processing of CSD attributed processes and workflows.

 

Responding to this Request

Organizations responding to this request should send a short document to:

George Percivall
Executive Director, Interoperability Architecture
Open Geospatial Consortium

percivall [at] opengeospatial.org

A response to this RFI must contain the following information:

  • A description of the technology relevant to CSD
  • Descriptions of example implementations of the relevant technology
  • Applicability of the technology to OWS3, e.g., SWE and Service Chaining.

Documents in pdf format are preferred.

Submission of proprietary information is discouraged. Any response containing proprietary information must place that information in a separate file.  Do not send proprietary information unless your organization has previously executed a Non-Disclosure Agreement with OGC.

Any organization with relevant technology can respond to this RFI.  You need not be a member of OGC to respond.  There is no reimbursement for responding to this RFI. By accepting an RFI response, OGC implies no endorsement of the technology and there is no implied agreement that the contents of an RFI response will be reflected in the OWS-3 RFQ.

For more information about CSD Services, contact:

Brent Bursey
President, Great-Circle Technologies, Inc.,
703 764-9140,

BBursey [at] Great-CircleTech.com

The OGC is an international industry consortium of more than 250 companies, government agencies and universities participating in a consensus process to develop publicly available interface specifications. OpenGIS(R) Specifications support interoperable solutions that "geo-enable" the Web, wireless and location-based services, and mainstream IT. The specifications empower technology developers to make complex spatial information and services accessible and useful with all kinds of applications. Visit the OGC website at http://www.opengeospatial.org.

Candidate Submission: Tue, 2004-08-10 17:00
Close request period: Thu, 2006-08-10 17:00
TC and PC vote to issue request: Thu, 2006-08-10 17:00
Begin request period: Thu, 2006-08-10 17:00
 

OGC Requests: 

GML in JPEG 2000 for Geographic Imagery (GMLJP2) Implementation Specification: Request for Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called GML simple features profile. OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification Profile. The purpose of this Request for Comment (RFC) is to obtain comments on the proposal for technologies and needed interfaces required for GML in JPEG 2000 for Geographic Imagery (GMLJP2) Implementation Specification. Documentation of this draft specification can be downloaded here:

Candidate Submission: Mon, 2005-05-23 17:00
Close request period: Fri, 2005-06-17 17:00
TC and PC vote to issue request: Mon, 2005-06-27 17:00
Begin request period: Wed, 2005-07-27 17:00
 

Downloads: 


The Geography Markup Language (GML) is an XML grammar for the encoding of geographic information including geographic features, coverages, observations, topology, geometry, coordinate reference systems, units of measure, time, and value objects. JPEG 2000 is a wavelet based encoding for imagery that provides the ability to include XML data for description of the image within the JPEG 2000 data file. The "GML in JPEG 2000 for Geographic Imagery (GMLJP2) Implementation Specification" defines the OGC standard method of using GML within JPEG 2000 images for geographic imagery.
Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

GML simple features profile: Request for Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called GML simple features profile. OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification Profile. The purpose of this Request for Comment (RFC) is to obtain comments on the proposal for technologies and needed interfaces required for GML simple features profile. Documentation of this draft specification can be downloaded here:

Candidate Submission: Mon, 2005-05-23 17:00
Close request period: Fri, 2005-06-17 17:00
TC and PC vote to issue request: Tue, 2005-07-05 17:00
Begin request period: Thu, 2005-08-04 17:00

Downloads: 


This profile defines a restricted but useful subset of XML-Schema and GML to lower the "implementation bar" of time and resources required for an organization to commit for developing software that supports GML. It is hoped that by lowering the effort required to manipulate XML encoded feature data, organizations will be encouraged to invest more time and effort to take greater advantage of GML's rich functionality.
Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

Pages