Download Charter document

This Standards Working Group (SWG) is focused on processing the OGC GeoServices REST 1.0 candidate standard.

This OGC GeoServices REST Candidate Standard Version 1.0 standard is derived from the “Esri GeoServices REST Specification Version 1.0” which was developed to provide interoperability between ArcGIS Server and the broader information technology community. The candidate standard is designed to be implemented without the use of Esri products. The OGC version differs from the Esri version in that it is presented in a vendor neutral fashion appropriate for an OGC standard. The specification currently provides a JSON encoding, but does not limit alternate JSON representations (such as GeoJSON).

The scope of work includes addressing the OAB comments and adjudicating the comments received during the public review, additional edits to the candidate standard based on the comments, and removal of “esri” references and prefixes. The final deliverable of the OGC GeoServices REST SWG is a version of the candidate standard that follows the OGC Modular Specification policy.

A public review of a draft of the candidate standard was started in July 2012. The SWG has processed the comments and the resolution of the comments is documented in OGC 12-164.

Based on the comment resolution a revised draft of the candidate standard has been prepared and submitted to the OGC Technical Committee. During the ongoing adoption vote in the OGC Technical Committee several comments have been received. The response to these comments are documented in OGC 13-031r1.

Information about the process can be found in the OGC Technical Committee Policies and Procedures.

The OGC GeoSPARQL standard supports representing and querying geospatial data on the Semantic Web. GeoSPARQL defines a vocabulary for representing geospatial data in RDF, and it defines an extension to the SPARQL query language for processing geospatial data.

The first version of the GeoSPARQL standard has been completed. OGC document 11-052r4 GeoSPARQL – A Geographic Query Language for RDF Data was published on June 12, 2012 as an OGC Implementation Standard.

More information about the standard, including downloads for the standard document and associated ontologies, can be found on the GeoSPARQL standard web page:
http://www.opengeospatial.org/standards/geosparql

This work has been harmonized with the OGC Simple Features standard, ISO 19107, and with the SPARQL working group in the W3C.

 

GeoSynchronization Service

Agile spatial data infrastructures based on OGC standards allow content provider organizations to deploy increasingly efficient networks capable of responding to dynamic requirements for using geospatial or location referenced content. In this context, content provider organizations are being more and more called upon to deliver current, timely and verified data over the World Wide Web.

 

In order to satisfy these requirements, content providers must collaborate with outside entities to collect new data and/or update their existing data holdings. This may, for example, mean synchronizing their data with closest-to-source providers as might be the case between municipal, state/provincial and/or federal levels of government. This may also mean crowd-sourcing (see http://en.wikipedia.org/wiki/Crowdsourcing) their data production or supporting volunteer geographic information (VGI). Crowd-sourcing or VGI has proven to be a very effective mechanism for emergency management / disaster relief situations as is evidenced by the response to the Haiti earthquake of 12-JAN-2010.

 

Regardless of the nature of the collaboration, there is a need for a service to mediate the interaction between data providers and outside entities acting as data collectors. The service must support data entry with validation, notification of changes to interested parties and allow replication of the data provider's features.

 

A Geosynchronization service, deployed by a data provider, sits between the features a provider offers via a WFS and data collectors. It allows data collectors to submit new data or make modifications to existing features without directly affecting the features in the provider's data store(s) until validation has been applied thus ensuring that the data published by the provider is of high quality.

 

The concept of a GeoSynchronization service was developed during the Canadian Geospatial Data Infrastructure (CGDI) Interoperability Pilot project. The CGDI-IP project was an activity developed by GeoConnections in collaboration with the OGC's Interoperability Program to test the feasibility of using open, standards-based technology to improve the management and dissemination of geospatial data in Canada. In particular, this project demonstrated that technology from multiple vendors based on the Open Geospatial Consortium’s Web Feature Service (WFS) standard could interoperate to provide access to the most current and authoritative data; thereby maintaining currency, avoiding unnecessary versioning and minimizing duplication of the data. The main development of CGDI-IP was conducted from April 2007 to January 2008. The initial concept was further enhanced during the OGC Web Service Phase 5 project, a project in Canada with the Ministries of Natural Resources Québec and Transport Québec and several projects with Army TEC in the United-States. All the projects tested and extended the concepts of a federated Geosynchronization system.

 

Purpose of the Standards Working Group

The purpose of the Geosynchronization Service SWG is to produce a version 1.0.0 implementation standard.

Scope of Work

The SWG shall review and edit the "OWS-7 Engineering Report -- Geosynchronization service" to produce a version 1.0 implementation standard. The review shall be both a technical and editorial review. The items that need to be addressed by the SWG include:

1. Update 10-069r2 to conform to the latest OGC document directives including the Modular Specifications Policy.

2. Add an abstract test suite.

3. Validate all schemas and examples.

4. Address any other technical and/or editorial issues that arise during the review period.

Only those change requests and comments submitted through the formal process as identified in the Policy and Procedures shall be addressed.  Any items suggested through emails, vocal discussions, etc. will be outside of the scope of this SWG untilsubmitted as a formal CR.

What is out of scope?

As describe in Clause 1, the Geosynchronization service has been under development since 2007 and has been tested in a good number of test beds and projects.

 

As a result, the scope of work shall be tightly confined to the current contents of OGC 10-069r2 and aspects of the service not already described in OGC 10-069r2 shall be out of scope.

 

In other words, the feature list shall be limited to what is already described in the OWS-7 engineering report.

Existing Work as a Starting Point

The starting point for this implementation standard shall be OGC 10-069r2.

How it is to be Determined when the Work of the SWG has been Completed

The Geosynchronization Service SWG shall be dissolved after the following three milestones have been achieved:

•  

  1. The SWG has reviewed and edited 10-069r2 to produce a V1.0 candidate standard.

  2. SWG membership approves a recommendation to submit the document to the TC for consideration as an OGC Adopted Standard.

  3. The candidate standard has been approved by the OGC Technical and Planning Committees as an Adopted OGC standard.

Description of deliverables

There shall be two deliverables:

1. A document containing a list of proposed changes resulting from the review period and the disposition of each CR.

2. A V1.0 candidate standard.

IPR Policy for this SWG

The IPR Policy for the Geosyncronization SWG will be RAND and Royalty Free.

Anticipated Audience

Any organization that has a requirement for mediating changes to content in a distributed or federated environment.

Other informative information about the work of this SWG

Similar or applicable standards work (OGC and elsewhere).

The following standards and projects may be relevant to the SWG's planned work, although none currently provide all the functionality anticipated by this committee's deliverables:

• IETF RFC 4287, The Atom Syndication Format

• IETF RFC 5023, The Atom Publishing Protocol

• OGC 06-050r2, An Introduction to GeoRSS: A Standards Based Approach for Geo-enabling RSS feeds

• OpenGIS Web Feature Service (WFS) Implementation Specification V1.0, V1.1, V2.0

• OpenGIS Filter Encoding Implementation Specificatons V1.0, V1.1, V2.0

• OpenGIS GML Simple Features Profile V1.0 and V2.0

• Open Search v1.0 (Draft 4)

• Open Street Maps (http://www.openstreetmaps.org)

Details of the first meeting

The first meeting of the committee will be held by telephone conference call at —AM EDT on 22 Sept. 2010. Call-in information will be provided to the SWG's e-mail list and on the portal calendar in advance of the meeting.

Projected on-going meeting schedule

The work of the committee will be carried out primarily by email and conference calls, possibly every two weeks, with face-to-face meetings perhaps during each of the OGC TC meetings.

Supporters of the Proposal

The following people support this proposal and are committed to the Charter and projected meeting schedule.

 

Name	Email	Organization
Boisvert, Eric	Eric.Boisvert@RNCan-NRCan.gc.ca	Natural Resources Canada
Fegeas, Robin	rfegeas@usgs.gov	U.S. Geological Survey
Goldstein, Nuke	ngoldstein@thecarbonproject.com	The Carbon Project
Harrison, Jeff	jharrison@thecarbonproject.com	The Carbon Project
Keighan, Edric	ekeighan@cubewerx.com	CubeWerx Inc.
Mattson, Mark	mmattson@thecarbonproject.com	The Carbon Project
Métivier, Romain	romain.metivier@mrnf.gouv.qc.ca	Ministère des resources naturelles et de la faune du Québec (MRNF)
Poulin, Gaetan	gaetan.poulin@mtq.gouv.qc.ca	Ministère des transports du Québec (MTQ)
Stowe, Glenn	gstowe@cubewerx.com	CubeWerx Inc.
Vretanos, Panagiotis (Peter) A.	pvretano@cubewerx.com	CubeWerx Inc.
David, Wesloh	David.G.Wesloh@nga.mil	National Geospatial-Intelligence Agency

 

Convener(s)

Panagiotis (Peter) A. Vretanos (CubeWerx Inc.)

Jeff Harrison (The Carbon Project)

 

1.    GeoXACML Standards Working Group

 

2.    Purpose of this Standards Working Group

One purpose of the persistent GeoXACML Standards Working Group (SWG) is to develop an OGC Web Services Profile of GeoXACML and to progress it to the state of an adopted OGC standard. This profile will standardize the guidelines how to use GeoXACML to protect OGC Web Services and thereby providing enhanced interoperability in GeoXACML based access control systems for OWS. This profile will also support an easier applicability and implementation of XACML or GeoXACML based access control systems in OWS environments, as the guidelines in the profile that describe precisely how to use the access control language in the OWS use case, will be less generic.

Another purpose of the persistent GeoXACML SWG is to coordinate OGC's work on GeoXACML with the work of the OASIS XACML WG. The aim of this cooperation is to harmonize the closely related and sequential work of both standardization bodies. As shown in the OWS-6 GeoXACML ER (09-036), it is desirable to develop Change Request Proposals (CRPs) for GeoXACML's underlying base standards (e.g. OASIS' eXtensible Access Control Markup Language (XACML) Version 2.0 specification, the Hierarchical resource profile of XACML v2.0 and the Multiple resource profile of XACML v2.0) These CRPs will help improve the underlying standards and enable them to handle the OWS specific requirements.

This SWG will also evaluate and resolve CRPs referring to the OpenGIS® GeoXACML implementation specification and incorporate all submitted CRPs into a candidate revision of the GeoXACML v.1.0 standard. The SWG will ensure that all changes are consistent with the OGC standards baseline and business plan.

3.    Scope of Work

The initial Roadmap plan of this SWG can be divided into the following work items:

1.       Develop an OGC Web Services Profile of GeoXACML and progress it to the state of an adopted OGC standard. The following topics have to be covered in the OGC Web Service Profile of GeoXACML (for details see 09-036 - the OWS-6 GeoXACML ER)

o    guidelines for interoperable (Geo)XACML access control decision requests in the OWS context

o    guidelines for interoperable (Geo)XACML access control rules for OWS

o    guidelines how to use XACML's obligation mechanism in an OASIS conformant way in the OWS use case

2.       Cooperation and coordination with OASIS' XACML WG. As explained above and in detail in the GeoXACML ER, it is necessary and promising to improve the OASIS Multiple and Hierarchical resource profile of XACML and the XACML specification itself, in order to be able to handle the complexity of the access control for OWS use case adequately.

3.       Cooperation with other OGC Working Groups. Members of the Security DWG, OWS Common DWG and GeoXACML SWG should cooperate and coordinate their work in order to generate interoperable, general-use and harmonized security solutions. Some topics that need to be addressed by these cooperating groups are (for details see 09-036):

o    develop unique guidelines how to bind return values of the access control process and other Security Services with OWS responses and how to bind security information to OWS requests

o    define standardized security related exception codes

o    define normative bijective transformation rules between different protocol bindings (e.g. transform uniquely from KVP encoded OWS requests to XML encoded requests)

o    ensure an interoperable interplay of GeoXACML with other services of OGC's security architecture

o    specification of minimal requirements for OWS specifications in order to support the sound and strait forward applicability of generic security solutions for OWS

4.       Another scope of work of this SWG will be to process CRPs referring to the GeoXACML Standard. Hence the SWG will collect all GeoXACML related CRPs, evaluate each of these proposals, and make edits to the standard based on change requests and related decisions of the SWG membership. Changes required to the standard to align it with revisions of the standards baseline or business plan also require the submission of CRPs. The SWG may announce a cut-off date for the submission of CRPs that are to be addressed in the next revision. Additional CRPs submitted after the cut-off date may be addressed at the discretion of the SWG based on criticality of the change and available time and resources. The SWG may decide to address selected CRPs immediately in a corrigendum of the current standard.

3.1       What is out of scope?

Only those change requests submitted through the formal process as identified in the OGC TC Policy and Procedures will be addressed. Therefore, any items suggested through emails, vocal discussions, etc. will be outside of the scope of this SWG until formally submitted.

3.2       Specific Contribution of Existing Work as a Starting Point

The starting point for the work will be version 1.0 of the OpenGIS® GeoXACML implementation specification (07‑026r2), OASIS' eXtensible Access Control Markup Language (XACML) Version 2.0 specification, the Hierarchical resource profile of XACML v2.0 and the Multiple resource profile of XACML v2.0.

3.3       How it is to be Determined when the Work of the SWG has been Completed?

The GeoXACML SWG may dissolve after the following milestones have been achieved (note that this is not automatic as the GeoXACML SWG is a persistent SWG):

• Approval by the SWG membership of a recommendation to submit an OGC Web Services Profile of GeoXACML document to the TC for consideration as an OGC Adopted Standard.
• Approval by the SWG membership of a recommendation to submit a document to the TC for consideration as a revision of the OpenGIS® GeoXACML Standard deprecating the current version.
• The OGC Web Services Profile of GeoXACML or a revision of the GeoXACML standard has been approved by the OGC Technical and Planning Committees.
• The SWG has completed the evaluation, resolution and incorporation of all CRPs submitted prior to the cut-off date into the candidate revision of the standard.
• Completion of a 30 day public comment period.

4.    Description of deliverables

The initial focus of this SWG will be to develop the following two deliverables:

1. (Candidate) standard: the OGC Web Service Profile of GeoXACML
2. Change Request Proposals for GeoXACML's underlying base standards (e.g. OASIS' eXtensible Access Control Markup Language (XACML) Version 2.0 specification, the Hierarchical resource profile of XACML v2.0 and the Multiple resource profile of XACML v2.0).

Other deliverables might result from the work of this SWG, after the two deliverables mentioned above have been completed. The SWG might e.g. continue work on the GeoXACML specification and deliver a candidate for the revision of the OpenGIS® GeoXACML 1.0 Standard for submission to the TC.

The schedule of activities will be documented on the Twiki pages of this SWG and shall be updated by the SWG after every TC meeting. The current plan is to submit a candidate of the OGC Web Services Profile of GeoXACML as soon as possible; ideally before the December 2009 TC meeting. The coordination work between the GeoXACML SWG and the OASIS XACML WG can start as soon as the organizational frame (within the OGC and between the OGC and OASIS is established).

5.    IPR Policy for this SWG

RAND-Royalty Free.

6.    Anticipated Participants

The targeted participants of the GeoXACML SWG are those involved in the design, development, implementation, or use of GeoXACML or XACML based access control systems for (OGC) Web Services as well as spatial content providers, traders or users and prospective GeoXACML users. This includes participants of standards working groups of the OGC which develop and maintain OGC standards that can be secured by GeoXACML or referencing GeoXACML.

7.    Other informative information about the work of this SWG

a. Similar or applicable standards work (OGC and elsewhere).

• OASIS' XACML WG - XACML 3.0 and certain profiles of XACML 3.0
• OGC's OWS Common DWG - OGC Web Service Common specification
• W3C's XML XPATH and XQuery WG

The SWG will seek and if possible maintain liaison with each of the organizations/WGs maintaining the above works.

b. Details of the first meeting

The first meeting of the SWG will be held as a face-to-face meeting during the June 2009 OGC TC meeting in Boston

c. Projected on-going meeting schedule

The work of the SWG will be carried out primarily by email, Twiki, conference calls and with face-to-face meetings perhaps at each of the OGC TC meetings.

d. Supporters of the Proposal

The following people support this proposal and are committed to the Charter and projected meeting schedule. These members are known as SWG Founding or Charter members. Once the SWG is officially activated, this group is immediately "opted-into" the SWG and have voting rights from the first day the SWG is officially formed. Extend the table as necessary.

 

Name	Organization
Jan Herrmann	Technische Universität München
Andreas Matheus	Universität der Bundeswehr München
Cristian Opincaru	Secure Dimensions GmbH
Martin Kyle	Sierra Systems, Inc.
Ron Lake	Galdos Systems, Inc.
David Burggraf	Galdos Systems, Inc.
David Wesloh	National Geospatial-Intelligence Agency

 
e. Convener(s)

Jan Herrmann, Technische Universität München.