OGC Requests

Observations and Measurements: Request for Public Comments

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

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

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

 

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

Gazetteer Profile of WFS: Request for Public Comments

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

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

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

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

OGC Request for Information on "Contextual State Description" Services

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

Introduction

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

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

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

 

Sensor Web Enablement and OpenGIS SensorWeb™

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

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

 

Using CSD for Service Chaining

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

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

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

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

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

 

Potential use for CSD in OWS3

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

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

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

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

 

Objective Requirements

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

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

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

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

 

Responding to this Request

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

George Percivall
Executive Director, Interoperability Architecture
Open Geospatial Consortium

percivall [at] opengeospatial.org

A response to this RFI must contain the following information:

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

Documents in pdf format are preferred.

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

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

For more information about CSD Services, contact:

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

BBursey [at] Great-CircleTech.com

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

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

OGC Requests: 

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

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

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

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

Downloads: 


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

GML simple features profile: Request for Comments

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

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

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

Downloads: 


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

GITA Interoperability Demonstration Call for Participation

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

On April 24, 2006, the Opening Session of GITA`s Annual Conference 29 in Tampa, Florida, will include a feature completely new to the event. Foregoing the traditional keynote speaker, GITA`s Board of Directors has approved a motion by the Annual Conference Committee to conduct an educational and entertaining Interoperability Demonstration. In doing so, GITA is challenging the industry to meet the theme for this year`s conference, "No Barriers: Connected. Responsive. Prepared". This demonstration will feature integrated data, products, solutions, and services from multiple organizations, showing how standards-based, commercial off-the-shelf geospatial software, data and services can be used to remove the barriers within a geospatial community. GITA`s Geospatially Enabling Community Collaboration initiative, or GECCo, is a project that is helping local communities protect their critical infrastructure. Based around a to-be-determined GECCo scenario that will hopefully include the Tampa Bay area, participants will be able to demonstrate to an estimated 1,200 session attendees how critical and complex tasks that used to take days now take a fraction of that time to complete; all through the use of open architecture and standards-based implementation. Although this session will be based on technology and special attention being given to Web services, the goal of the demonstration is to show decision-makers how the use of interoperable technology provides will help facilitate quicker, more accurate, and less costly decisions. This Call for Participation is open to everyone; however, all participating organizations must be members of GITA. A committee has been established to review submissions for participation. Based upon those responses, selections will be made for participation. GITA will not provide funding or reimburse costs associated with this demonstration. Commercial presentations and product demonstrations will not be accepted. It will be the responsibility of the submitting organization to attend regularly scheduled teleconferences and collaborative demonstration dry runs during the planning and preparation stages (if applicable, a data or service provider may only need to be available if situations or questions arise). All costs, other than standard audio/visual support at the live demonstration and the collaborative preparation environment, will be at the expense of the participants. If your organization is interested in participating in this unique demonstration, please send a short description of your offering, along with complete contact information, to interop.proposal [at] opengeospatial.org prior to October 14, 2005. Pending membership in GITA, nonmembers may be provisionally accepted to participate in the demonstration.

Candidate Submission: Wed, 2005-09-14 17:00
Close request period: Fri, 2005-10-14 17:00
TC and PC vote to issue request: Fri, 2005-10-14 17:00
Begin request period: Wed, 2005-09-14 17:00
 

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending 2005-10-14, Comments received will be consolidated and reviewed by the official review committee. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments)
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: 

GML 3.1.1 grid 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 grid 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 3.1.1 grid CRSs 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 grid coverage (including image) Coordinate Reference Systems (CRSs) plus related coordinate Transformations. This document also specifies some Universal Resource Names (URNs) for definitions in the "ogc" URN namespace, in addition to those specified in [OGC 05-010]. Additional specific URNs are defined for definitions of the datums, coordinate systems, and coordinate system axes which are often used in definitions of grid and image CRSs.

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 "GridCRS" as a better name for a DerivedCRS that uses a CartesianCS. 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: 

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

GML 3.1.1 CRS support 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 CRS support 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 09:00
Close request period: Fri, 2005-11-11 09:00
TC and PC vote to issue request: Thu, 2005-12-08 09:00
Begin request period: Sat, 2006-01-07 09:00
 

Downloads: 


This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for supporting other profiles for encoding definitions of Coordinate Reference Systems (CRSs) and Coordinate Operations. This profile can be used without a GML Application Schema, and such use is assumed in this document.
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