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: 

OGC Calls for Participation in FAA Information Dissemination Pilot

Status: 
Please note: This Request is scheduled to close on 18 October 2010 at 9:00 PM EDT.
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 Special Activity Airspace (SAA) Dissemination Pilot, sponsored by the US Federal Aviation Administration (FAA).

 

The RFQ/CFP is below. Responses are due by October 18, 2010. A bidders’ teleconference will be held on October 4, 2010. The Point of Contact for the SAA SWIM Pilot is Nadine Alameh nalameh [at] opengeospatial.org.

 

The FAA SAA Dissemination Pilot will extend the SAA SWIM Services to enable the dissemination of SAA information (including updates and schedule changes) to National Airspace System (NAS) stakeholders and other external users via services that implement OGC Web Services (OWS) standards.

 

In support of the Next Generation Air Transportation System (NextGen), the FAA SWIM program seeks to achieve systems interoperability and information management for diverse Air Traffic Management (ATM) systems using Service-Oriented Architectures (SOA). The FAA SWIM capabilities include supporting the exchange of SAA information between operational ATM systems. SAAs include Special Use Airspaces (SUA) - regions of airspace designated for use by the military ensuring no other traffic uses that airspace during scheduled times.

 

The FAA SAA DisseminationPilot shall build on SAA SWIM Services leveraging the OGC Web Feature Service (WFS), the OGC Feature Portrayal Service (FPS), the (draft) Event Service and the Aeronautical Information Exchange Model (AIXM), Support the filtering, access and portrayal of SAA information as well as the notification to subscribed users of SAA updates and schedule changes,and support the evolution towards end-to-end automated information flow from the US Department of Defense (DoD) - originators of SAA activation requests - to airlines and other NAS stakeholders.

OGC Requests: 

The OGC Seeks Comments on Candidate GeoPackage Standard

Status: 
Please note: This call is now closed.
Closing Date: 
Thu, 09/05/2013 - 04: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 (SWG) will consider all submitted comments when they prepare a final draft of the GeoPackage Standard.

The candidate OGC GeoPackage Standard provides an open, non-proprietary, platform-independent SQLite container for distribution and direct use of all kinds of geospatial data, including vector features and tile matrix sets.  GeoPackage can be used by mobile device users who require geospatial application services and associated data in disconnected or limited network connectivity environments where open, sharable geospatial data to support their applications is frequently unavailable. GeoPackage supports applications that involve creation of geospatial data products in enterprise computing environments, data product distribution to other computing environments, mobile workforce data capture and updates, and volunteered geographic information.

The GeoPackage container and related GPKG SQLite Extension configuration and API will increase the cross-platform interoperability of geospatial applications and web services in the mobile world.  Standard configuration and APIs for access and management of GeoPackage data will provide consistent query and update results across such applications and services. 

All OGC standards are free and publicly available. Download the candidate GeoPackage Standard below, or check it out on GitHub. Comments are due by 5 September 2013.

Comment: 

Comments can be submitted 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. There are three ways to provide input into the candidate standard:

  1. Edit the document on GitHub: if you are familiar with GitHub, please make your proposed changes directly. Instructions are in the README.md file in that repository.
  2. Submit an "issue" on GitHub: GitHub offers a simple interface for posting an issue/comment. Just click the green "New Issue" button.
  3. Submit an issue via email: Comments can be submitted to a dedicated email reflector 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: 

OGC Seeks Comments on SWE Common Service Model Interface Standard

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

The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the candidate OGC Sensor Web Enablement (SWE) Common Service Model Interface Standard Version 2.0. The SWE Service Model provides a common set of data types and defines a common set of interface mechanisms that can be used with other SWE interface standards.

There are two "SWE Common" standards: The OGC SWE Common Service Model Interface Standard is applicable to all services that provide or require information from or about sensors. It is designed for uses cases in which sensors need to be accessed and managed through service interfaces. A related standard, the OGC SWE Common Encoding Standard, provides a standard model (and XML implementation of the model) for the representation, nature, structure and encoding of sensor related data. It is used for describing static data (files) as well as dynamically generated datasets (on-the-fly processing), real-time streaming data, and process and web service inputs and outputs.

Both of the SWE Common standards are designed to be used with other existing OGC® Sensor Web Enablement standards such as OGC Sensor Model Language (SensorML) Encoding Standard, Sensor Observation Service (SOS) Interface Standard and Sensor Planning Service (SPS) Interface Standard.

The proposed OGC SWE Service Model 2.0 Standard and information on submitting comments on this document are available below. The public comment period closes on 25 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 announces Call for Participation in MilOps Geospatial Interoperability Experiment

Status: 
Please note: This Request is closed as of 4 March 2013. 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: 
Mon, 03/04/2013 - 05:00
Description: 

The Open Geospatial Consortium (OGC) has announced a Call for Participation (CFP) in the OGC MilOps Geospatial Interoperability Experiment (MOGIE). The CFP document is available below. 

Command and Control (C2) Core (https://c2core.gtri.org) has been an emerging data exchange capability within Department of Defense over the past three years.  DoD CIO is now moving toward adopting the National Information Exchange Model (NIEM) (http://niem.gov). C2 Core, which is 93% aligned with NIEM technical standards, will be used as the foundation for developing a Military Operations (MilOps) Domain in NIEM. 

The purpose of this experiment is to ensure interoperability of the MilOps Domain with the OGC's geospatial standards and with tools built on those standards. This experiment will demonstrate that the MilOps Domain model and NIEM v2.1 technical concepts work in combination with OGC standards, such as the Geography Markup Language (GML) Encoding Standard and the Web Feature Service (WFS) Web coverage Service (WCS) and Web Mapping Services (WMS) interface standards.

The OGC members that are acting as initiators of the Interoperability Experiment are:

Expressions of interest for participation are due by 4 March 2013.

Contact Frank Klucznik (Frank.Klucznik [at] gtri.gatech.edu) for further details and to register as a participant.

Georgia Tech Research Institute (GTRI) is also one of the organizations that will be participating in the Interoperability Experiment. GTRI and other organizations planning to participate will develop tools, implement and deploy OGC service components or client applications, design a test plan, and prepare reports that contribute to the overall objectives of the experiment.

OGC testbeds, pilot projects and interoperability experiments are part of the OGC's Interoperability Program, a global, hands-on collaborative prototyping program designed to rapidly develop and test candidate specifications and then deliver these proven specifications into the OGC's Standards Program, where they are formalized for public release as OGC standards. These initiatives enable users and providers of geospatial technology to share the costs of developing standards that provide a foundation for "future-proof" enterprise architectures. Providers reduce their costs of developing and maintaining interfaces and encodings while gaining industry recognition, the confidence of an initiative's sponsoring organizations, and the market growth that results from open standards.

An OGC Interoperability Experiment is a rapid, low overhead, formally structured OGC-facilitated activity in which members achieve specific technical objectives that further the OGC Technical Baseline.

OGC Requests: 

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

Candidate Submission: Mon, 2005-10-17 09:00
Close request period: Fri, 2005-11-11 09:00
TC and PC vote to issue request: Fri, 2006-01-20 09:00
Begin request period: Sun, 2006-02-19 09:00
 

Downloads: 


This document defines an application profile of an OGC Catalogue service; it is primarily based on the HTTP binding (the CSW part) described in Clause 11 of the OGC Catalogue Services Specification, version 2.0 (OGC 04-021r3). The profile constrains the usage of several base specifications and introduces some additional search, retrieval, and transaction capabilities.
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: 

Fusion Request for Information

Status: 
Please note: This Request is scheduled to close on 12 August 2009.
Description: 

The Open Geospatial Consortium (OGC®) has issued a Request for Information (RFI) to solicit industry input into a Fusion Standards Study to be conducted in preparation for the planned OGC Web Services, Phase 7 (OWS-7) Testbed. OGC also seeks to establish alliances with other Standards Development Organizations (SDOs) having technology relevant to fusion.

In the context of this RFI, "Fusion is the act or process of combining two or more pieces of data or information regarding one or more entities in order to improve the capability for detection, identification, or characterization of that entity".

This RFI is based on requirements and contributions from several OGC Member organizations, including the National Geospatial-intelligence Agency (NGA), BAE Systems - C3I Systems, and Lockheed Martin.

The Study will conduct a survey of standards and implementations that support geospatial fusion. It will review existing standards regarding fusion; recommend future standards or integration or harmonization of standards; and plan for evaluating standards through OGC's OWS-7 testbed to be conducted later this year.

Responses to the RFI are requested by August 12, 2009. The RFI below includes instructions for how organizations can respond. Please contact George Percivall at gpercivall [at] opengeospatial.org with any questions.

OGC testbeds, pilot projects and interoperability experiments are part of OGC's Interoperability Program, a global, hands-on 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.


Downloads: 

Telecon: Dial-in +1 512 225 3050 passcode:55699#

Date / Time: 07/28/2009 : 11:00 AM - 01:00 PM

WorldTime: See Fixed Time World Clock Website ** This is not an OGC resource, OGC is not responsible for errors.

Location: Herndon Conference Room - 483B Carlisle Dr. Herndon, VA 20170

WebEx Session Logistics:

- To join the teleconference use this dial-in information: +1 512 225 3050 passcode: 55699#.

- To join the Webex session: 
1. Go to https://opengeospatial.webex.com/opengeospatial/j.php?ED=114548557&UID=0
2. Enter your name and email address.
3. Enter the meeting password: FusionRFI28
4. Click "Join Now".

 

 

OGC Requests: 

OGC seeks comments on Climate and Forecast (CF) extension to NetCDF Core data model 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: 
Fri, 09/21/2012 - 04:00
Description: 

The Open Geospatial Consortium (OGC®) membership seeks comments on an OGC candidate standard, the CF-netCDF Data Model extension to the existing OGC Network Common Data Form (netCDF) Core Encoding Standard version 1.0. 

The CF-netCDF Data Model is a flexible data model widely used in climate and weather forecast systems as well as for other types of environmental data. The candidate CF-netCDF Data Model extension to the existing OGC Network Common Data Form (netCDF) Core Encoding Standard version 1.0 is the latest step in establishing CF-netCDF as an OGC standard for binary encoding.  This will enable standard delivery of data in binary form via several OGC service interface standards.

The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena. NetCDF (network Common Data Form) is widely used internationally to communicate and store many kinds of multidimensional data, although it was originally developed for the Earth science community.  The netCDF data model is particularly well suited to providing data in forms familiar to atmospheric and oceanic scientists: namely, as sets of related arrays. 

The conventions for climate and forecast (CF) metadata are designed to promote the processing and sharing of files created with the netCDF API.  The conventions define metadata that provide a definitive description of what the data in each variable represents, and the spatial and temporal properties of the data. This enables users of data from different sources to decide which quantities are comparable, and facilitates building applications with powerful extraction, regridding, and display capabilities.

NetCDF was developed and is maintained and actively supported by the University Corporation for Atmospheric Research (UCAR) (www.ucar.edu). UCAR and other OGC members introduced the first netCDF specification as a candidate OGC standard to encourage broader international use and greater interoperability among clients and servers interchanging data in binary form. 

The candidate CF-netCDF Data Model extension to the existing OGC Network Common Data Form (netCDF) Core Encoding Standard version 1.0 and information about submitting comments on this document are available below. The public comment period closes on September 21, 2012.

Downloads: 
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: 

Request for Comments (RFC) on the Earth Observation (EO) Products Extension Package for ebRIM (ISO/TS 15000-3)

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 members of the Open Geospatial Consortium, Inc. (OGC) have submitted a Request for Comments (RFC) on version 0.2.2 of the Earth Observation (EO) Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 (OGC document 06-131). (ebRIM is the electronic business Registry Information Model from the OASIS standards organization. CSW (“Catalog Services - Web”) is an OGC standard that specifies a catalogue application profile based on ISO19115:2003/ISO19119:2005 metadata with support for XML encoding per ISO/CD TS 19139  and HTTP protocol binding.)

The EO Products Extension Package for ebRIM Profile of CSW 2.0 draft standard is an OGC Best Practice. It specifies an Application Profile of CSW 2.0 that is based on the OpenGIS® Geography Markup Language (GML) Encoding Standard Application Schema for EO Products.

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