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: 

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 KML 2.2

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 the KML 2.2 candidate standard. The OGC invites public comment on this candidate standard. All comments will be collated and used in the evaluation of KML 2.2 as an OGC standard. In late first quarter 2008, the OGC committee working on the KML 2.2 candidate standard will seek approval by OGC members for KML 2.2 an OpenGIS(R) Encoding Standard.

The OpenGIS Candidate Implementation Standard specifies XML grammar used to encode and transport representations of geographic data for display in an earth browser. Put simply: KML encodes what to show in an earth browser, and how to show it. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for KML 2.2. Documentation of this draft standard can be downloaded below:

Candidate Submission: Thur, 2007-08-30
TC and PC vote to issue request: Fri, 2007-09-21
Begin request period: Tue, 2007-12-4
Close request period: Thu, 2008-01-03

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?SUBJECT=KML%202.2%20Comment&BODY=Part%20A%20to%20be%20completed%20once.%20%20Iterate%20Part%20B%20as%20needed.%0D%0DPART%20A%0D%0D1.%20Evaluator:%20%5BCONTACT%20INFORMATION%5D%0D%0D2.%20Submission:%20%5BOpenGIS%20Project%20Document%20Number,%20Name%5D%0D%0DPART%20B%0D%0D1.%20Requirement:%20%5BGeneral,%20#%5D%0D%0D2.%20Implementation%20Specification%20Section%20number:%20%5BGeneral,%20#%5D%0D%0D3.%20Criticality:%20%5BMajor,%20Minor,%20Editorial,%20etc.%5D%0D%0D4.%20Comments/justifications%20for%20changes:%20%5BComments%5D%0D%0D">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 Sensor Alert Service

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 Alert Service (SAS). 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 Sensor Alert Service (SAS) Draft Implementation Specification specifies interfaces for requesting information describing the capabilities of a Sensor Alert Service, for determining the nature of offered alerts, the protocols used, and the options to subscribe to specific alert types.

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

Candidate Submission: Thur, 2007-06-15
TC and PC vote to issue request: Fri, 2007-07-13
Begin request period: Wed, 2007-11-15
Close request period: Fri, 2007-12-15

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 Comments (RFC) on Candidate Specification 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 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 membership of the Open Geospatial Consortium, Inc. (OGC) is requesting comments from the public on the candidate OGC Document, "The OGC Specification Model - Writing Modular Specifications".

This document, prepared by the Policy 1.0 Standards Working Group, derives from the collective experience of members in developing and implementing OGC standards, geospatial applications, platforms and services. It provides a logical model and template for candidate standards to assure their internal logic and conformance to accepted software development procedures and the OGC's policy and rules regarding the structure of standards and the types of information that they must provide. The policy guidance will make implementation of OGC standards and the construction of compliance tests easier through enforced traceability of requirements to implementation tests, and it will make modularization of both standards and implementations more explicit and consistent across dependent standards and implementations.

This standard has been referred to as the "core and extension model" due to the insistence on a modular structure throughout all parts of a standard and its implementation. Eventually, all OGC standards will be transitioned to the new structure. This will help standardize the manner in which OGC standards are written and implemented, making implementations easier to test for compliance, thus improving interoperability between and swap-ability between implementations.

The 30 day public comment period begins March 12, 2009 and closes on April 11, 2009. Comments will be reviewed and processed by the OGC Membership. The intent is to edit the Specification Model candidate standard and move the document to be an approved OGC standard. The Specification Model 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: 

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: 

Request for Comments (RFC) on the GeoLinking Service 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 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 membership of the Open Geospatial Consortium, Inc. (OGC) is requesting comments on the candidate standard OpenGIS(R) GeoLinking Service (GLS) Interface.

The candidate GLS standard defines an interface for services that provide the ability to "link" data that contain information about geographic objects, such as census tract population statistics, with data in another repository that contains the actual geometry (points, lines, polygons). For example, a table of populations of cities on one server may not contain the geometry information that describes the cities' locations and boundaries, while a second server may house the cities' geometry. The candidate GLS standard describes a set of interfaces for both servers that lets the city name be used as a "common geographic identifier" to join the population data to its geometry, so the user can create a map or perform geospatial analysis on the linked data.

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 Comments on Candidate PUCK Protocol 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 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®) seeks public comment on the candidate OGC PUCK Protocol Encoding Standard.

Most sensor networks require careful manual installation and configuration by technicians to assure that software components are properly associated with the physical instruments that they represent. Instrument driver software, configuration files, and "metadata" describing the instrument and its capabilities must be manually installed and associated with a physical instrument port. Sometimes these manual procedures must be performed under physically challenging conditions, increasing the chances of human error. PUCK addresses these challenges by defining a standard instrument protocol to retrieve metadata and other information from the device itself. This information can include OGC SWE SensorML and IEEE 1451 Transducer Electronic Data Sheet (TEDS) documents, as well as actual instrument driver code. Computers on the network can use the PUCK protocol to retrieve this information from installed instruments and utilize it appropriately, e.g. to automatically identify, configure and operate the instruments. Thus PUCK enables automatic self-configuring "plug-and-work" sensor networks.

PUCK is relatively simple, and several manufacturers have implemented the protocol in their instruments' firmware. PUCK augments but doesn't replace existing instrument command sets, so can be implemented without abandoning existing firmware and software applications. PUCK was originally developed by the Monterey Bay Aquarium Research Institute (MBARI) for oceanographic applications, but is useful in any sensor network containing RS232 or Ethernet-connected instruments. PUCK-enabled instruments have been deployed on ocean observatories in the USA and Europe, and the protocol is being considered for adoption by other projects as well. The OGC Technical Committee’s PUCK Standards Working Group was chartered to process the existing MBARI PUCK protocol as a candidate OGC standard compatible with the OGC Sensor Web Enablement (SWE) standards baseline.

The candidate OGC PUCK 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: 

Request for Comments on Candidate Web Map Tiling 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 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 membership of the Open Geospatial Consortium, Inc. (OGC®) is requesting comments from the public on the candidate OpenGIS® Web Map Tiling Service (WMTS) Interface Standard.

The candidate WMTS Interface Standard is much like the OGC's popular Web Map Server (WMS) Interface Standard, but it enables better server performance in applications that involve many simultaneous requests. To improve performance, instead of creating a new image for each request, it returns small pre-generated images (e.g., PNG or JPEG) or reuses identical previous requests that follow a discrete set of tile matrices. This proposed standard provides support for multiple architectural patterns - KVP, REST and SOAP.

The 30 day public comment period for this document begins February 26, 2009. Comments are due by March 29, 2009. After the OGC's WMS Standards Working Group has addressed comments received in response to the WMTS RFC the draft documents will be submitted to the OGC Technical Committee and Planning Committee for their review and possible approval as an adopted OGC Standard.

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

Pages