OGC Requests

Request for Comments on Earth Observation Metadata profile of the OGC Observations and Measurements Standard

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 Standards 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®) seeks public comment on the candidate standard “Earth Observation Metadata profile of the OGC Observations and Measurements Standard.” 

The Earth Observation (EO) profile of Observations and Measurements is intended to provide a standard schema for encoding Earth Observation metadata to support the description and cataloguing of products from sensors aboard EO satellites.

 

This second version of the Earth Observation metadata profile is based on Observations and Measurements, an OGC and ISO standard used in several communities. For example, O&M is used as a basis for the application schemas in several draft INSPIRE Annex II+III data specifications.

 

The metadata elements defined in this candidate standard are applicable for use in catalogues and applications, including various EO cataloguing applications based on OGC standards like the ebRIM Application Profile of the OGC Catalog Services – Web (CS-W) Interface Standard.

 

EO products are differentiated by parameters such as date of acquisition and location as well as characteristics pertaining to the type of sensor, such as cloud, haze, smoke or other phenomena obscuring optical imagery. Metadata used to distinguish EO product types are defined in this candidate standard for generic products and also for specific thematic EO products, such as optical, radar, atmospheric, altimetry, limb-looking and synthesized products. In addition, this document describes the mechanism used to extend these schemas to specific EO missions.

 

The candidate OGC Earth Observation Metadata profile of Observations & Measurements Standard documents are available for review and comment below.

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] lists.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: 

AAtS Standards Harmonization Guidance Initiative

Status: 
Please note:  This call is now closed.

The community workshop has been re-scheduled to December 17-18 in Washington DC. Contact nalameh [at] opengeospatial.org (Nadine Alameh) if you're interested in participating.

Closing Date: 
Tue, 10/22/2013 - 04:00
Description: 

The Open Geospatial Consortium (OGC) has issued a Request for Information (RFI) to engage the aviation community in identifying standards efforts relevant to the provision of aircraft connectivity to the FAA’s System Wide Information Management (SWIM) infrastructure.

RFI Information:

  • Responses are due by 5 pm EST on 22 October 2013. 
  • A public Q&A webinar was held 1 October 2013 to provide the community with more information on the context and objectives behind this RFI. Documentation below. 

The FAA’s Aircraft Access to SWIM (AAtS) initiative is in a preliminary stage of requirements development and standards identification. Its goal is to establish a common operating environment between the flight deck, air traffic management and Airline Operational Control/Flight Operational Control (AOC/FOC) for collaborative strategic decision-making. Distribution of the operational information needed to support the safe movement of aircraft during all phases of flight in the National Airspace System (NAS) will increase capacity and efficiency and result in more timely departures and arrivals.  

There are a number of aviation standards in development, concurrently and independently, by a variety of industry groups that are also pursuing the development of requirements and standards to leverage ground-based aviation related information and data networking technology to support aircraft operations. The need to understand the scope, applicability and relationship between these efforts is both critical and timely.

Staff and members of all such industry groups are encouraged to respond to this RFI and to participate and contribute information on:

  • Technologies, standards and general trends relevant to AAtS
  • Practical recommendations on harmonization opportunities and challenges
  • Insights on how to best craft an interim path for the community and to develop a technical architecture that is forward thinking and can accommodate this emerging and evolving environment.
  • Global harmonization considerations 

Responses provided will guide the discussion at a community workshop, scheduled for 17-18 December 2013 in Washington DC, and will be considered in the development of a report that will form the basis for harmonization guidance and recommendations. 

Downloads: 

References:

Community Workshop: 

    • The community workshop, originally scheduled for Nov 5-6, has been rescheduled to Dec 17-18, 2013. Email nalameh [at] opengeospatial.org if you're interested in attending. 
    • All organization representatives interested in participating in the workshop are strongly encouraged to submit a concise response to the RFI, in order to help us organize the workshop efficiently and incorporate everybody's interests.

     

    Further Information:

    Please send an email to techdesk [at] opengeospatial.org if you have questions or need further information.

    Webinar:

    Links to the webinar material:

    Clarifications: 

      Download the Clarifications.

        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: 

        Request for Comments on Earth Observation Satellite Tasking Extension for OGC® Sensor Planning Service (SPS)

        Status: 
        Please note: This Request is scheduled to close on 16 September, 2010.
        Description: 

        The Open Geospatial Consortium, Inc. (OGC®) members are seeking comments on the "Earth Observation Satellite Tasking Extension for OGC® Sensor Planning Service (SPS)." The SPS configuration proposed in this profile supports the programming of Earth Observation (EO) sensor systems. The candidate standard describes a single SPS configuration that can be supported by many satellite data providers who have existing facilities for managing sensor system programming requests.

        This SPS standard defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor, where the sensor may be any type of sensor with a digital interface. The SPS and EO-SPS standards are part of the OGC Sensor Web Enablement (SWE) (http://www.opengeospatial.org/ogc/markets-technologies/swe) suite of standards. SWE standards enable developers to describe, discover, task, and access any Internet or Web accessible sensor, transducer and sensor data repository.

        The candidate OGC® Sensor Planning Service Application Profile for Earth Observation Sensors and information on submitting comments on this document are available below.

        The public comment period closes on September 16, 2010.

        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 Calls for Participation in Major Interoperability Testbed - OWS-10

        Status: 
        Please note: This call is now closed.

         

        Go Directly to Clarifications

        Closing Date: 
        Mon, 08/26/2013 - 04:00
        Description: 

        The Open Geospatial Consortium (OGC®) has issued a Request for Quotations/Call for Participation (RFQ/CFP) to solicit proposals in response to requirements for the OGC Testbed 10.

        The RFQ/CFP is available at http://www.opengeospatial.org/pub/www/ows10/rfq/index.html.

        Organizations who haven't previously been engaged in OGC Testbeds are encouraged to check out the quickstart guide for help on navigating the RFQ.

        Responses are due by 5 pm EST on 26 August 2013.

        An IP Program and Testbed 10 Q&A Webinar will be held on 6 August 2013 at 10 am EDT (Check your local time http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130806T14). Register here https://portal.opengeospatial.org/public_ogc/register/130806ows10.php. For the most efficient use of this webinar, please send your questions in advance to techdesk [at] opengeospatial.org.

        You are also invited to follow us on twitter, Linkedin or Facebook to stay updated on the Q&A Webinar, clarifications to requirements, kickoff details, etc.

        The OGC Testbed 10 Kickoff event for the CCI and Open Mobility threads (see below) will be held 7-9 October 2013 in Washington, DC. The Aviation thread kickoff will be held 27 September in Frascati, Italy during the week of the OGC Technical Committee Meeting in Frascati.

        The Point of Contact is Nadine Alameh: techdesk [at] opengeospatial.org.

        The OGC Testbed 10 sponsors are:

        • AGC (Army Geospatial Center, US Army Corps of Engineers)
        • ESA (European Space Agency)
        • EUROCONTROL
        • FAA (US Federal Aviation Administration)
        • GeoConnections - Natural Resources Canada
        • Harris Corporation
        • Lockheed Martin Corporation
        • NGA (US National Geospatial-Intelligence Agency)
        • NOAA National Weather Service
        • USGS (US Geological Survey)
        • UK DSTL (UK MoD Defence Science and Technology Laboratory)

        OGC Testbed 10 builds on the outcomes of prior OGC initiatives (http://www.opengeospatial.org/resource/demos) and is organized around the following threads:

        -   Cross-Community Interoperability (CCI): Increase Geospatial community interoperability by building on CCI OWS-9 work in semantic mediation, volunteer geographic information (VGI), provenance and data quality, and Global Gazetteer. Explore the potential of interoperability in the hydrology domain and utilizing ontologies to more easily share and visualize geospatial data.

        -   Open Mobility: Explore the geospatial standards requirements needed to support the growing emerging mobile environment where client applications are mobile, information services are mobile, and increasingly distributed across cloud infrastructures. The Open Mobility thread will address these requirements while leveraging on the work achieved in the OWS-9 Testbed in the areas of Geopackages and Geopackaging services and new OWS Context encodings.

        -   Aviation: Develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) and the Flight Information Exchange Model (FIXM), building on the work accomplished in prior testbeds to advance the applications of OGC Web Services standards in next generation air traffic management systems to support European and US aviation modernization programs.

        The RFQ/CFP includes details of these threads as well as details on participation eligibility, selection process and kickoff workshop information.

        OGC testbeds, pilot projects and interoperability experiments are part of the OGC Interoperability Program, a global, hands-on collaborative agile prototyping program designed to rapidly develop, test and deliver proven candidate standards into the OGC Standards Program, where they are formalized for public release.

        Downloads: 

        Click a link below to download individual files or a complete package for the RFQ/CFP.

        DOWNLOAD RFP/CFP PACKAGE (as .zip archive)

        Complete OWS10 RFQ/CFP (pdf zip format) *UPDATED 22 July 2013*

        INDIVIDUAL FILES

        OWS10 RFQ Main Body (pdf)
        OWS10 RFQ Main Body (doc)
        OWS10 RFQ Annex A (pdf) *UPDATED 22 July 2013*
        OWS10 RFQ Annex A (doc) *UPDATED 22 July 2013*
        OWS10 RFQ Annex B (pdf)
        OWS10 RFQ Annex B (doc)
        OWS10 RFQ Annex C (pdf)
        OWS10 RFQ Annex C (doc)
        OWS10 RFQ Annex D (pdf)
        OWS10 RFQ Annex D (doc)

        RFQ/CFP RESPONSE TEMPLATES (also included in above zip)

        OWS10 RFQCFP Template Proposal (doc)
        OWS10 Template Spreadsheet (xls)

         

        CLARIFICATIONS

        Response to questions and any other clarifications are posted here:

        Clarifications

        OGC Requests: 

        GML 3.1.1 common CRSs profile: 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 GML 3.1.1 common CRSs profile. OGC invites public comment on a candidate profile specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification Profile. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for GML CRS support profile. Documentation of this draft specification can be downloaded here:

        Candidate Submission: Tue, 2005-10-11 17:00
        Close request period: Fri, 2005-11-11 17:00
        TC and PC vote to issue request: Thu, 2005-12-08 17:00
        Begin request period: Sat, 2006-01-07 17:00
         

        Downloads: 


        This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of commonly-used Coordinate Reference Systems (CRSs) plus related coordinate Conversions.

        This profile can be used without a GML Application Schema, and such use is assumed in this document. However, a GML Application Schema that uses this profile could be specified. For example, an Application Schema could specify a specialized "TransverseMercatorConversion", as discussed in Annex F. Or an Application Schema could allow or require more information to be encoded for an OperationParameter (such as specified in Subclause 14.3.2 and wctsOperationParameter.xsd of OGC Discussion Paper [OGC 05-013]).

        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 Seeks Comments on Modular, GML-based Web Coverage Service 2.0

        Status: 
        Please note: This Request is scheduled to close on 14 April 2010.
        Description: 

        The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the draft OGC Web Coverage Services (WCS) Interface Standard Version 2.0.  The OGC WCS standard supports electronic retrieval of geospatial data as "coverages" - that is, digital geospatial information representing space/time-varying phenomena such as satellite imagery or digital elevation models. The WCS 2.0 draft has several significant enhancements over previous versions. WCS 2.0 is harmonized with the Geography Markup Language coverage model, leading to increased interoperability across OGC standards. Further, WCS 2.0 is highly modular and follows the core/extension design pattern, which allows for standard that is easier to understand and implement.

        The WCS standard defines a standard interface and operations that enable interoperable access to single or multi-dimensional geospatial coverages.  Services implementing this standard provide an interface with a standard set of operations for accessing original or derived sets of geospatial coverage information. An important aspect of the WCS standard is that it allows access and retrieval of raw, unprocessed imagery, which is often required by rendering and processing services. Further information about WCS can be found at the WCS Service page ( http://www.ogcnetwork.net/wcs ) of the OGC Network.

        The proposed OGC WCS 2.0 standard and information on submitting comments on this document are available below. The public comment period closes on 14 April 2010.

        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: 

        The OGC Seeks Comments on Candidate GeoPackage Standard

        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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
        Closing Date: 
        Thu, 02/07/2013 - 05:00
        Description: 

        The Open Geospatial Consortium (OGC®) seeks public comments on the current draft of the candidate OGC GeoPackage (GPKG) Standard. The GPKG Standards Working Group will consider all comments when preparing a final draft of the candidate standard.

        Mobile device users who require geospatial application services and associated data and who operate in disconnected or limited network connectivity environments frequently do not have open, available geospatial data to support their applications. Applications include such things as mobile workforce data capture and updates, volunteered geographic information, and real time annotations of map data in an emergency event.

        The candidate OGC GeoPackage (GPKG) Standard provides an open, non-proprietary, platform-independent container for distribution and direct use of all kinds of geospatial data. The GeoPackage container and related API will increase the cross-platform interoperability of geospatial applications and web services in the mobile world.  Standard APIs for access and management of GeoPackage data will provide consistent query and update results across such applications and services.  

        Future enhancements to the GeoPackage standard, a future GeoPackage Web Service standard, and modifications to existing OGC Web Service (OWS) standards to use GeoPackages as exchange formats will allow OWS to support provisioning of GeoPackages throughout an enterprise or information community.

        Interoperability of GeoPackage implementations by several participants is being tested and will be demonstrated in the 15 January 2013 OGC Web Services Testbed (OWS-9) Demonstration. The current reference implementation bases, SQLite and SpatiaLite, are open source resources developed by OGC members. The SQLite reference implementation is sponsored in part by the SQLite Consortium, which includes a number of OGC members. SpatiaLite is built on OS-Geo open source libraries by the president of GFOSS.it and others.

        The current draft of the candidate OGC GeoPackage (GPKG) Standard can be downloaded below:

        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] lists.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: 

        OpenGIS® Sensor Model Language (SensorML): 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 OpenGIS® Sensor Model Language (SensorML). 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 encodings required for OpenGIS® Sensor Model Language (SensorML). Documentation of this draft specification can be downloaded here:

        Candidate Submission: Wed, 2006-02-01 16:00
        Close request period: Fri, 2006-03-10 16:00
        TC and PC vote to issue request: Wed, 2006-04-05 16:00
        Begin request period: Fri, 2006-05-05 16:00
         

        Downloads: 

        This document specifies models and XML encoding for the core SensorML. SensorML provides a common framework for any process and process chain. Within SensorML, sensors and transducer components (detectors, transmitters, actuators, and filters) are all modelled as processes that can be connected and participate equally within a process chain, and which utilize the same process model frame as any other process.
        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 Calls for Comment on revision to OGC Web Services Common Standard

        Status: 
        Please note: This Request is scheduled to closed on 20 May 2009.
        Description: 
        The members of the Open Geospatial Consortium, Inc. (OGC®) request comments to a revision to the OpenGIS® Web Services Common Standard. This document specifies many of the aspects that are common to multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily parameters and data structures used in operation requests and responses. Examples of common usage are how to handle bounding boxes, exception processing, URL requests, URN expressions, key value encoding, and so forth.

        The primary use of OWS Common is as a normative reference for other OWS standards. Those standards currently include the OpenGIS Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS) Standards. Rather than continuing to repeat this material in each Implementation Standard, each standard normatively references each relevant part of OWS Common.

        The 30 day public comment period begins April 20, 2009 and closes on May 20, 2009. Comments will be reviewed and processed by the OGC Membership. The intent is to edit the OWS Common standard and move the revised document to be an approved OGC standard. The OpenGIS® Web Services Common Standard Request for Comment document can be downloaded below.

        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