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.

 

1. Geography Markup Language 3.3 SWG (GML SWG)

 

2. Purpose of this Standards Working Group

The purpose of the GML SWG is to revise the OpenGIS® Geography Markup Language (GML) Encoding Standard. The standard is also published by ISO as ISO 19136:2007.

The SWG may decide - in cooperation with the OGC TCC, the ISO/TC 211 Chairman and the JAG - that the revision should be a joint project with ISO/TC 211 and result in a revision of ISO 19136, too. In this case, the SWG will also deliver one or more ISO New Work Item Proposals for submission by OGC to ISO/TC 211.

The purpose of this Standards Working Group is to evaluate and resolve submitted Change Request Proposals (CRPs) assigned to the GML SWG.

The SWG will ensure that all changes are consistent with the OGC standards baseline and business plan and ISO/TC 211 standards baseline.

3. Scope of Work

This SWG is focused on processing CRPs to be included in the OpenGIS® Geography Markup Language (GML) Encoding Standard. 

The Scope of Work (SOW) will be to collect all outstanding 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. The cut-off date for version 3.3 was at the end of the OGC TC meeting in September 2008. 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 final deliverable will be a revision of the standard for consideration by the membership for adoption.

The SWG may decide to address selected CRPs immediately in a corrigendum of the current standard.

As part of the CRP review process the SWG will decide on the version number of the revised standard, i.e. 3.3 or 4.0.

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 3.2.1 of the OpenGIS® Geography Markup Language (GML) Encoding Standard (07-036) and all formally submitted CRPs. 

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

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

1. 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.
2. Completion of a 30 day public comment period.
3. Approval by the SWG membership of a recommendation to submit the document to the TC for consideration as a revision of the OpenGIS® Geography Markup Language (GML) Encoding Standard deprecating the current version.
4. The revision of the standard has been approved by the OGC Technical and Planning Committees.

In case of a joint project with ISO/TC 211, additional milestones may be required.

4. Description of deliverables

The following deliverables will result from the work of this SWG:

1. A candidate for the revision of the OpenGIS® Geography Markup Language (GML) Encoding Standard for submission to the TC. As part of the revision process the standard may be split into multiple parts.
2. Corresponding informative schema documents associated with the revision for publication in the OGC schema repository.
3. Release notes documenting the changes introduced in the revision.

The schedule of activities is documented on the Twiki pages of the GML SWG. The current plan is to submit a candidate of GML 3.3 before the September 2009 TC meeting.

The schedule is meant to serve as a general guideline to the SWG in order to determine completion milestones. However, the completion date and other target dates will be adjusted in order to accommodate a critical update to the document(s) or allow for a sufficient discussion of CRPs. The schedule shall be updated by the SWG at every TC meeting.

Although all change requests will be addressed, some may be postponed due to the need to more quickly produce deliverables resolving higher priority requests.

5. IPR Policy for this SWG

RAND-Royalty Free.

6. Anticipated Participants

The targeted participants of the GML SWG are implementers of GML and other standards using GML as well as content providers and prospective users of geographic information exposed as XML.

This includes the standards working groups of the OGC which develop and maintain OGC standards normatively referencing GML.

7. Other informative information about the work of this SWG

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

• Revisions to abstract standards normatively referenced by GML
• Revisions to the OGC specification best practice document (06-135r1)
• Results of the OGC Policy SWG
• Ongoing work in the SWE DWG and Coverages DWG and their associated SWGs
• Revision of ISO 19118

b. Details of the first meeting

The GML SWG kickoff meeting and teleconference was held Tuesday, 25 March 2008, from 10:00 to 12:00 Central time. The meeting took place during the March 2008 OGC TC meeting in St Louis, MO, USA.

c. Projected on-going meeting schedule

The work of this SWG will be carried out primarily by email, the Twiki and conference calls, with face-to-face meetings in principle at each of the OGC TC meetings as defined by the chair.

d. Supporters of the Proposal

The following people supported this proposal and are committed to the Charter and projected meeting schedule. These members are known as SWG Founding or Charter members.

Name	Organization
Clemens Portele	interactive instruments GmbH
Simon Cox	CSIRO
Ron Lake	Galdos Inc.
David Burggraf	Galdos Inc.
Andrew Woolf	British Atmospheric Data Centre (NCAS/BADC)

e. Convener

• Clemens Portele (interactive instruments GmbH)

1. Purpose of the Standards Working Group

The purpose of GMLJP2  Standards Working Group is to move the existing GMLJP2 version 1.0.0 standard through a revision process. The SWG will process impacts to this standard from updates of dependent standards, address omissions from the initial standard, process comments from OWS5, and assess future work items for the initial standard. The work of this SWG will also ensure alignment with all OGC processes, the OGC standards baseline, and OGC's business plan.

2. Scope of Work

The SWG will focus on revisions to the existing adopted standard by collecting all outstanding Change Request Proposals, evaluate each of the proposals, and make edits to the standard based on CRPs and related decisions of the SWG membership. The final deliverable of this SWG is an updated version of the candidate standard for consideration by the membership.

Specific items that are currently identified as being in scope may include (subject to approval by SWG membership):

• Updates to the standard based on updates to normative references within the standard
  • Update from GML 3.1/3.1.1 (OGC 03-105r1/OGC 04-092r4) to GML 3.2.1 (ISO 19136)
  • Update from ISO 19105:2000, Geographic information - Conformance and Testing to ISO19105:2005
  • Update from OWS Common 1.0 (OGC 05-008r1) to OWS Common 1.1.0 (OGC 06-121r3)
  • Update from URNs of Definitions in OGC Namespace (OGC 05-010) to Definition identifier URNs in OGC namespace 1.1.0 (OGC 06-023r1)
  • Update from Recommended XML/GML 3.1.1 Encoding of Common CRS Definitions (05-011)
• Agreed upon omissions from the original standard
  • standard encoding of null data values in an image
• Requirements specified as future work items in the original standard
  • use of unrectified grid coverages
  • external references into a GMLJP2/JPX file using a standardized URI Fragment Identifier Syntax
  • Accommodate specific needs of netCDF (network Common Data Form) for scientific data harmonization of observation syntax
  • temporal relationships between coverages
  • harmonization of observation work

2.1 What is out of scope?

For this activity, out of scope items are defined as:

• those items beyond the aforementioned scope of work that are not identified as Change Request Proposals and approved for inclusion by the membership before the end of calendar year 2007

2.2 Specific Contribution of Existing Work as a Starting Point

The starting point for this work will be:

• GML in JPEG 2000 for Geographic Imagery (GMLJP2) Encoding Specification (OGC 05-047r3)
• Geography Markup Language 3.2.1 (ISO 19136:2007)
• Geographic information - Conformance and Testing to ISO19105:2005
• OWS Common 1.1.0 (OGC 06-121r3)
• Definition identifier URNs in OGC namespace 1.1.0 (OGC 06-023r1)
• Change Request for Null Data Values against GMLJP2

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

The following rules define the completion criteria of the SWG:

• The impacts from updates to all normative references have been reviewed, decided upon, and integrated into the standard to the satisfaction of the SWG
• The evaluation of all future work items from version 1.0 have been completed, rolled into change requests, or either postponed or dropped from the scope to the satisfaction of the SWG.
• All Change Request Proposals submitted prior to Dec, 31, 2007 have been reviewed and decided upon to the satisfaction of the SWG.
• A completed revision of the GMLJP2 1.1 Specification Document has been produced by the SWG and has been approved for submission to the TC for approval as an adopted specification.

3. Description of deliverables

The deliverables for this SWG will be:

• a revision to the existing standard
• a revised set of schemas

The preliminary schedule of activities includes:

• December 2007 TC (Stresa in lago Maggiore, Italy) - Presentation of existing work and Change Request Cutoff publicized to accommodate OWS5
• March 2008 TC (St. Louis, USA) - Review/Presentation of Change Requests
• June 2008 TC (Bremen, Germany) - Draft Standard for IPR review
• September 2008 TC (College Station, Texas) - Approval of Standard Revision

 

4. IPR Policy for this SWG

This group is set up as RAND-Royalty Free.

 

5. Anticipated Audience

The anticipated audience of this standard is the community of hardware, software, and systems integration professionals that are involved in image acquisition, rectification, encoding, analysis, presentation, and preservation.

 

6. Other informative information about the work of this SWG

a. 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 the functionality anticipated by this committee's deliverables:

• Geography Markup Language
• JPEG 2000
• GeoXACML
• net-CDF
• Web Coverage Service
• Web Feature Service
• Sensor Observation Service
• Observations and Measurements

The SWG intends to seek and if possible maintain liaison with each of the organizations maintaining the above works.

b. Details of the first meeting

The first meeting of the committee will be held by telephone conference call at 12PM EDT on 8 October 2007. Call-in information will be provided to the SWG's e-mail list and on the portal calendar in advance of the meeting.

c. Projected on-going meeting schedule

The work of the committee will be carried out primarily by email and conference calls, every two weeks, 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.

• David Burggraf (Galdos Systems)
• Michael Gerlek (Lizardtech)
• Trent Hare (US Geological Survey)
• Steven Keens (PCI Geomatics)
• Martin Kyle (Sierra Systems)
• Lucian Plesea (Jet Propulsion Labs)
• Clemens Portele (Interactive Instruments)
• Alesandro Triglia (OSS Nokalva, Inc.)
• David Wesloh (National Geospatial Intelligence Agency)

e. Convener

Martin Kyle (Sierra Systems) was the convener of the SWG process, believing that it is time for a revision to the adopted standard.

1.    Project Description:

I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 SWG

2.    Purpose of this Standards Working Group

The purpose of this Standards Working Group is to update the "CIM (Cataloguing of ISO Metadata) Extension Package of ebRIM " (OGC Document 07-038), now renamed to "I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0", to the state of an adopted OGC standard. The SWG will achieve this objective by processing comments raised in the ESA SMAAD (Semantic-Web for Mediated Access Across Domains) project, in OWS9, in the ESA HMA (Heterogeneous Missions Access) AWG (Architecture Working Group) and by SWG members. The specification has been initially written in the frame of the ESA HMA project. The goal was to develop a specification of a catalogue service implementing the ebRIM Application Profile of CS-W for the discovery and management of ISO 19115 and ISO 19119 (in the future part of ISO19115) metadata encoded in ISO 19139 (the corresponding xml schema will in the future be part of ISO19115) and at a minimum equivalent in terms of capabilities to an OGC CSW ISO 19115/19119 Application Profile-compliant service. HMA is part of a European project called GMES (Global Monitoring for Environment and Security). The specification under development is actually at the state of an OGC Discussion Paper document

3.    Scope of Work

There are actually some implementations of this document already in semi production environment. Now, it is time to propose this document to the OGC community to promote it to an OGC standard.

For that, the SWG will organize the comments raised in ESA SMAAD, in OWS9 and in the ESA HMA AWG, evaluate them and process them by editing the document. The SWG will also work with the Catalog SWG and Catalog AP ebRIM SWG and propose Change Requests if some arise.

a.     What is out of scope?

Only those comments coming from the ESA SMAAD project, from OWS9 and from the ESA HMA AWG as well as further change requests submitted through the formal process as identified in the Policy and Procedures will be addressed.  Any items suggested through emails, vocal discussions, etc will be outside of the scope of this SWG until formally submitted.

The specification of the RIM-objects will be exclusively based on the ISO specifications 19115(-2), 19119 and 19139 which are ISO-standard at the time when the I15 (CIM) SWG resumes it´s work (Jan/2013).

b.    Specific Contribution of Existing Work as a Starting Point

ISO 19115 (part 1 & 2), ISO 19119 and ISO19139, Inspire directives, existing CSW ISO Application Profile specification, INSPIRE Conformance Class of current CIM

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

The I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 SWG will dissolve after the following three milestones have been achieved:

1. The SWG has completed evaluation and incorporation into the candidate standard of all comments received during the public comment period.

2. Approval by the SWG membership of 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.

4.    Description of deliverables

The following deliverables will result from the work of this SWG:

1. A final version of the Cataloging ISO19115 Metadata (I15) using the ebRIM profile of CS-W 1.0 Standard documents for submission to the TC.

2. Corresponding XML schemas associated with Cataloging ISO19115 Metadata (I15) using the ebRIM profile of CS-W 1.0 Standards documents.

The following schedule of activities is anticipated:

1. Resumption of the I15 (CIM) SWG work activities was achieved within a few ad hoc meetings in the context of the Redlands TC meeting (1/2013) and by subsequent emails.
2. Post I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 document and schema for a 30-day comment period beginning of September 2013
3. Resolve comments prior to December 2013
4. Post candidate standard with schema for vote beginning 2014

The above schedule is meant to serve as a guideline to the SWG in order to determine completion milestones.  However, based on the number and complexity of the actual Change Requests, completion dates may be adjusted to accommodate critical updates to the documents.  Although all change requests will be addressed, some may be postponed due to the need to more quickly produce a document containing higher priority requests.

5.    IPR Policy for this SWG

RAND-Royalty Free

6.    Anticipated Participants

The target audiences of the I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 include:

• Users/implementers of ISO catalogs

• National mapping agencies

• Services/Data managers

7.    Other informative information about the work of this SWG

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

The proposed standard is tightly linked to OASIS ebRIM, CSW AP ebRIM, CSW, CSW AP ISO, ISO 19115(-2)/19119/19139

e.     Will this be a persistent SWG?

No

f.      Details of the first meeting

Resume of the SWG was achieved within a few ad hoc meetings in the context of the Redlands TC meeting (1/2013) and by subsequent emails.

g.     Projected on-going meeting schedule

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

The teleconference calls will be scheduled as-needed and posted to the OGC portal. Call-in information will be provided to the SWG's e-mail list in advance of the meeting.

h.    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.

- Lorenzo Bigagli  (CNR, I, Lorenzo Bigagli (lorenzo.bigagli@cnr.it))

- Roger Brackin (envitia, UK, Roger Brackin (roger.brackin@envitia.com))

- David Burggraf (Galdos, CN, David Burggraf (dburggraf@galdosinc.com))

- Yves Coene (SPB, B, Yves Coene)

- Pier Giorgio Marchetti (ESA, EU, Pier.Giorgio.Marchetti@esa.int)

- Frederic Houbie (Geomatys, F, Frédéric Houbie)

- Michael Schick (EUMETSAT, EU, Michael Schick)

- Stefen Smolder (GIM, B, Steven Smolders)

- Uwe Voges (con terra, D, Uwe Voges)

i.      Convener(s)

Uwe Voges (con terra, D, Uwe Voges)

Purpose of this Standards Working Group

The purpose of this IndoorGML Standard Working Group is to develop an application schema of OGC GML and progress the document to the state of an adopted OGC standard. The goal of this candidate standard is to establish a common schema framework for indoor navigation applications. This SWG will start from the discussion paper (OGC 10-191r1, Requirements and Space-Event Modeling for Indoor Navigation), which summarizes the requirements and basic idea of a standard for indoor navigation.

Business Value Proposition

This SWG aims to provide a common schema framework for interoperability between indoor navigation applications, which cover a wide spectrum of application areas such as indoor LBS, indoor web map services, indoor emergency control, guiding services for visually handicapped persons in indoor space, and indoor robotics. Several commercial services for indoor spatial information have been recently launched such as Google Maps and Bing Indoor Maps. In order to meet the market demands from these application areas, we need indoor navigation information as an essential component. There are also strong demands of indoor navigation information from other standardization organizations including ISO/TC204 and IEEE RAS to extend existing standards to cover indoor space as well as outdoor space in a seamless way.

However, developing indoor navigation information is difficult and expensive due to the complexity of indoor space. The IndoorGML candidate standard will provide a framework of interoperability between systems and services for sharing indoor navigation information.

Scope of Work

The scope of work for this SWG is to develop a candidate standard of a GML 3.2 application schema for indoor navigation and progress it to the state of an adopted standard by using OGC RFC process as follows;

• development a candidate of OGC standard for indoor navigation: this candidate standard, called tentatively IndoorGML will provide a GML application schema for exchanging information related to indoor navigation,
• gathering comments from SWG member on the draft of candidate standard and reflecting them to the candidate standard,
• submitting the candidate standard to OAB for review and subsequent release for the 30-day public comment,
• resolving the comments from OGC members, and
• submitting the final version of candidate standard to the OGC TC for voting.

The aim of IndoorGML is to represent and exchange the geoinformation that is required to build and operate indoor navigation systems. IndoorGML will provide the essential model and data for important applications like building evacuation, disaster management, personal indoor navigation, indoor robot navigation, indoor spatial awareness, indoor location based services, and the support for tracking of people and goods. IndoorGML provides a framework for the flexible integration of different localization technologies and allows the ad-hoc selection of the appropriate navigation data according to the capabilities of the mobile device and the offered localization technologies of a building.

Indoor navigation comprises route planning, localization, and tracking of subjects (i.e. people) and objects (e.g. robots or other indoor vehicles). IndoorGML will support these activities in different modes of locomotion, i.e. walking, driving, and flying as well as navigation in virtual environments. Since there is no unique localization technology like GPS available indoors, many different types of indoor positioning techniques are used today, often in combination with each other. This makes it necessary to provide geospatial data about the different senders, receivers, and sensors and their respective signal ranges.

Existing standards for the representation of 3D building models like IFC or CityGML do not address these aspects. From the perspective of IndoorGML they can be considered as important data sources for the interior topography of buildings (and other structures like tunnels). IndoorGML, which will be also an application schema of GML, will be thus a complementary standard to CityGML and IFC to support location based services for indoor space, particularly indoor navigation. This candidate standard will mainly consist of two components; first an indoor spatial data model given by a multi-layer space model to describe different contexts of indoor space, and the representation of indoor symbolic space and topological properties, building upon the former component.

The requirements and use-cases for this candidate standard are given in detail in the OGC discussion paper (OGC 10-191r1).

4.2 Specific Contribution of Existing Work as a Starting Point

The work of this SWG will start from a discussion paper; OGC 10-191r1, Requirements and Space-Event Modeling for Indoor Navigation.

4.3 Determination of SWG Completion

The IndoorGML SWG will dissolve after the following three milestones have been achieved:

1. The SWG has completed evaluation and incorporation into the candidate standard of all comments received during the public comment period.
2. Approval by the SWG membership of 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.

Timeline

The tentative schedule of the activities for this SWG is;

1. SWG kickoff meeting: by Mar. 2012
2. IndoorGML v 0.1: by June 2012
3. SWG internal review of the document and preparation of an updated version v0.2 : by Aug. 2012
4. Revision for version v 0.3: by Sept. 2012
5. SWG voting for submission to OGC OAB/NA and 30 days public comment period: March 2013
6. Public comment period: from April 1 2013 to May 1, 2013
7. Reflection of public comments and revision: by August 2013
8. SWG internal voting for formal submission to OGC TC: September 2013
9. In case of approval for the formal submission to OGC TC, the final candidate standard will be sent to OGC TC for voting: by September 2013

Chair and vice-chairs

Chair:

Ki-Joune Li (Pusan National Univ. South Korea)

Vice Chairs:

Jiyeong Lee (University of Seoul, South Korea)
Sisi Zlatanova (TU Delft, the Netherlands)
Jeremy Morley (University of Nottingham, UK

 

1. OGC KML 2.3 SWG

2. Purpose of this Standards Working Group

The purpose of this SWG is to develop a first minor revision (V2.3) to the OGC® KML 2.2 Implementation Standard (OGC 07-147r2) to accomodate known issues and extensions identified in formal OGC Change Request Proposals (CRPs) and tested through implementation experience. The SWG will also make corresponding revisions to the companion OGC® KML 2.2 Abstract Test Suite Implementaiton Standard (07-134r2).

The SWG will achieve this objective by evaluating and resolving the submitted KML Change Request Proposals (CRPs) following the criteria in the KML Development Best Practices (OGC 08-125r1).

The SWG will ensure that all changes are consistent with the OGC standards baseline and business plan.

3. Scope of Work

The SWG will be focused on processing CRPs to the OGC® KML 2.2 ImplementationStandard as there are formal outstanding CRPs to this existing OGC standard.

The Scope of Work (SOW) will be to collect all outstanding CRPs, to evaluate and respond to each of the proposals, and if applicable, to make edits to the standard based on CRPs and related decisions of the SWG membership. The SWG, at their discretion, may also ask the membership for any additional change requests that have not been previously submitted. Each of the outstanding CRPs will be evaluated by the SWG according to the criteria identified in the KML Development Best Practices document (OGC 08-125r1). The SWG will then resopond to each CRP, which may include adopting the proposal with or without modification, rejecting the proposal, or postponing the proposal to a later version.

The SWG will address the existing CRPs in the V2.3 revision in accordance with the OGC TC Policy and Procedures. Additional CRPs submitted after the official formation of the SWG may be addressed at the discretion of the SWG based on criticality of the change and available time and resources.

3.1 What is Out of Scope?

This SWG will be focused only on outstanding CRPs submitted through the formal process as identified in the OGC TC Policy and Procedures. Any items suggested through emails, vocal discussions, etc., will be outside the scope of this SWG until formally submitted. CRPs that out of scope, if any, will be determined at the discretion of the SWG membership.

3.2 Specific Contribution of Existing Work as a Starting Point

The starting point for this work will be the evaluation of the outstanding CRPs directed at the existing OGC® KML 2.2 Standard.

3.3 Determination of SWG Completion

The KML 2.3 SWG will dissolve when: 

1. All CRPs submitted up until the official SWG formation date have been reviewed and evaluated to the satisfaction of the SWG. This may include adopting the proposal, rejecting the proposal or postponing the proposal to a later version.
2. Recommendations to submit documentation to the TC as a revised standard as approved by the SWG membership
3. The  revised standard has been approved by the OGC Technical and Planning Committees as an Adopted OGC Standard.

4. Description of Deliverables

The following deliverables will result from the work of this SWG: 

1. A candidates for version 2.3 of the OGC® KML Standard for submission to the OGC TC.
2. Corresponding schema documents associated with the revision for publication in the OGC schema repository.
3. An annotated list of all CRPs including the comment, submitter, comment type/priority, the response of the SWG, and supporting rationale.
4. Release notes documenting the changes introduced in the revision.

5. IPR Policy for this SWG

RAND-Royalty Free.

6. Anticipated Participants

The target audience of KML v2.3 includes search engine developers, GIS vendors, mass market software vendors interested in geographic based applications, and consumers.

7. Other Informative Remarks about the SWG

Details of the First Meeting

The first meeting of the SWG will be held at the OGC TC Meeting in Brussels, the proposed time and date is Tuesday, November 29^th at 1:00 PM local time in Brussels.

Projected On-going Meeting Schedule

The work of the SWG will be carried out primarily by email and conference calls, with face-to-face meetings in principle at each of the OGC TC meetings as defined by the chair. Other face-to-face meetings may be called if this can expedite the work of the SWG.

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
Ed Parsons	Google
David Burggraf	Galdos Systems (Chair)
Lucio Colaiacomo	EUSC
Kuo-Yu (Slayer) Chuang	ITRI
Satish Sankaran	ESRI
Sean Askay	Google (Vice-chair)

 

Convener

Ed Parsons, Google.

Applications using moving feature data, typically on vehicles and pedestrians, have recently been rapidly increasing. Innovative applications are expected to require the overlay and integration of moving feature data from different sources to create more social and business values. Efforts in this direction should be encouraged by ensuring smoother data exchange because handling and integrating moving feature data will broaden the market for geo-spatial information such as Geospatial Big Data Analysis.

The purpose of this Moving Features Standard Working Group is to develop a candidate  standard for moving features and progress the document to the state of an adopted OGC standard. The goal of this candidate standard is to establish an encoding format for handling moving feature data. This SWG will start from the discussion paper (OGC 12-117r1, OGC Standard for Moving Features; Requirements). This document summarizes the requirements for and basic idea of a standard for applications using moving feature data.

Market demand is rapidly increasing recently for better integration of moving feature data with GIS and other geospatial technologies. Example applications using moving feature data include traffic congestion information services using probe cars or taxis equipped with GPS to measure the travel time of each road link, tracking systems on auto-trucks for logistics management, and agent-based road traffic simulation systems for forecasting traffic situations. Systems relying on single-source moving feature data are now evolving into more integrated systems. Integration of moving feature data from different sources is a key to developing more innovative and advanced applications. This SWG aims to provide a standard for handling and sharing moving features data.

The scope of work for this SWG is to develop a candidate standard for moving features and progress it to the state of an adopted standard by using OGC RFC process as follows;

• development a candidate of OGC standard for moving feature: this candidate standard, called tentatively “OGC Moving Features Encoding Standard” will provide an encoding format for exchanging moving feature data,
• gathering comments from SWG member on the draft of candidate standard and reflecting them to the candidate standard,
• submitting the candidate standard to OAB for review and subsequent release for the 30-day public comment,
• resolving the comments from OGC members, and
• submitting the final version of candidate standard to the OGC TC for voting.

The requirements for standards on moving features are summarized below;

1. “ISO19141:2008 Schema for Moving Features” should be referred to as the conceptual framework for this development. A standard data model should describe the movement of zero to three-dimensional geometric features including changes in attitude or rotation along with the movement. The target of this specification is rigid features mentioned in ISO 19141:2008.
2. The implementation specifications on moving features should be prioritized, which more directly contributes to the system development because moving feature data is becoming more popular with the very rapid growth of smart phone users worldwide, and this is strongly pushing system developers towards the integration of moving feature data rather than using the moving feature data from a single source. Implementation specifications of general framework to handle movements of features and its derivation for 2D geometries are starting point. The scope of the standardization should be expanded incrementally through communication and discussions with system developers and potential users.
3. Methods specific to moving feature data handling, such as the detection of collisions, could be standardized after data model development arrives at certain level of maturity, based on further analysis of the technology and market trends.
4. Visualization and spatio-temporal interpolation of geometric features are already supported by popular standards such as X3D (http://www.web3d.org/x3d/). Unnecessary overlaps should be avoided, while popular standards should be referred to in developing a new specification on the moving features.

The use cases for standards on moving features are summarized below;

1. Integrated simulation for disaster risk management: Moving feature data is collected/integrated from different simulation systems such as people evacuation simulations, road vehicle simulations including emergency vehicles, and tsunami simulations. Many of them, except the tsunami simulations, are agent-based simulation systems that explicitly output the trajectories of individual agents, i.e., pedestrians and vehicles. The trajectories are described in this specification.
2. Traffic information services: Traffic congestion and the trafficability of roads can be estimated to provide guidance information to road users from real-time vehicle trajectory data collected from probe cars. Sources are becoming diversified from a fleet of taxis with GPS belonging to a single company to the mixture of auto-trucks, buses, and navigation system users. This trend makes it more necessary to integrate data using different models and formats. Integrated data have recently been used to identify traffic accident hot spots by analyzing a large amount of data on vehicle trajectories and velocity/acceleration changes.
3. Security services: This service requires the generation and sharing of situational information as a common picture by integrating and visualizing data on pedestrian and vehicle movements collected from heterogeneous sensors like surveillance cameras, GPSs, and mobile phones.
4. Navigation for Robots: Robots are expected to guide and help in the movement of elderly or handicapped people in public spaces like shopping malls. Since robots can identify only near-by obstacles and moving features with laser range and/or vision sensors, they may require situational information on a larger scale, and this requires integration of the trajectory data from the moving features collected through sensor networks.
5. Aviation, maritime traffic monitoring: Track information should be shared among organizations for air traffic control, ocean monitoring, etc. This specification is applicable to such track information and systems including vessel tracking systems and emergency management systems for oil spill monitoring.

The justifications of the new candidate OGC standard are summarized below:

1. ISO 19141:2008 compliant implementation standard
2. Massive data handling

The relation between this new candidate OGC standard and other existing standards are summarized below;

1. Harmonized with: ISO19141:2008 Schema for Moving Features (trajectory and prism model)

The RoadMap plan of the activities for this SWG is;

1. 2013/01 Discussion paper v 0.2, Ad-hoc meeting
2. 2013/03 SWG charter post & review & approved
3. 2013/03 SWG Kickoff meeting
4. 2013/06 Moving Feature v 0.1
5. 2013/09 Moving Feature v 0.2
6. 2013/12 Moving Feature v 0.3
7. 2014/01 SWG voting for 30 days public comment period
8. 2014/02 Public comment period
9. 2014/05 Reflection of public comments and revision for Moving Feature v 0.4
10. 2014/06 SWG internal voting for formal submission to OGC TC
11. 2014/07 In case of approval for the formal submission to OGC TC, the final candidate standard will be sent to OGC TC for voting

4.1        What is Out of Scope?

The following activities are out of scope for the initial OGC Moving Features specification, but may be in scope for future versions of the OGC Moving Features specification, or other related specifications as indicated.

l  Non-rigid features (future or related)

l  Moving Features data service interfaces (related)

l  Coverage data (i.e. water movement) (related)

l  Sensor measurements data (related)

4.2        Specific Contribution of Existing Work as a Starting Point

The work of this SWG will start from a discussion paper; OGC 12-117r1, OGC Standard for Moving Features; Requirements.

4.3        Determination of SWG Completion

The Moving Features SWG will dissolve after the following three milestones have been achieved:

1. The SWG has completed evaluation and incorporation into the candidate standard of all comments received during the public comment period.
2. Approval by the SWG membership of 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.

The following deliverables will result from the work of this SWG;

• A final version of Moving Features standard documents for the submission to the TC, and
• Corresponding schemas associated with Moving Features.

R RAND-Royalty Free.    RAND for fee

Those involved in the design, development, implementation, or use of elements listed above in "Scope of the Work". This includes search service providers, prospective users of search services exposed as XML, information architects and bibliographic, metadata, and content provider.

 

a. 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 the functionality anticipated by this committee's deliverables:

• ISO 19141:2008 Geographic information -- Schema for moving features
• OGC Simple Features Specification for SQL
• Web3D X3D

b. Details of the First Meeting

The first meeting of the SWG will be held at the OGC TC in Abu Dhabi on March 17-21 2013. Call-in information will be provided to the SWG's e-mail list and on the portal calendar in advance of the meeting.

 

c. Projected On-going Meeting Schedule

The work of the SWG will be carried out primarily by email and conference calls, possibly every month, 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
Ryosuke Shibasaki	The University of Tokyo
Akinori Asahara	Central Research Laboratory, Hitachi, Ltd.
Thomas H. Kolbe	Technische Universität München
Ki-Joune Li	Pusan National University
Kuo-Yu slayer Chuang	Industrial Technology Research Institute
Carl Stephen Smyth	OpenSitePlan
Jiyeong Lee	University of Seoul
Mike Botts	Botts Innovative Research
Steve Liang	University of Calgary
John Herring	Oracle
Christine Perey	PEREY Research & Consulting
Toshiaki Iwata	National Institute of Advanced Industrial Science & Technology (AIST)
David Burggraf	Galdos Systems Inc

 

e. Convener(s)

Ryosuke Shibasaki (Center for Spatial Information Science, The University of Tokyo)

 

1.    Observations and Measurements v2 Standards Working Group

 

2.    Purpose of this Standards Working Group

The purpose of the O&M v2 SWG is to consider revisions to the OpenGIS® Observations and Measurements Implementation Standard..

A revision of O&M has been triggered by submission of OGC O&M to ISO/TC 211 as a proposed New Work Item. The submission was made under the liaison arrangement between ISO/TC 211 and OGC, and the Work Item has been assigned the number 19156. If the document submitted to ISO is approved as a Committee Draft, then an Editing Committee will be formed to process the document. It is expected that the ISO processes will result in changes to the standard, and an OGC SWG can provide a liaison with OGC, to ensure that the concerns and requirements identified by OCG members are attended to and that the final document is suitable as a revised OGC standard as well as an ISO standard. The SWG will ensure that the results of  harmonization efforts involving OGC WCS and SWE activities are introduced to the EC if appropriate.

This Standards Working Group will also evaluate and resolve submitted Change Request Proposals (CRPs) assigned to the O&M v2 SWG. The OGC SWG may propose intermediate revisions of O&M for publication through OGC only.

The SWG will ensure that all changes are consistent with the OGC standards baseline and business plan and ISO/TC 211 standards baseline.

3.    Scope of Work

As a New Work Item in ISO/TC 211 the management of the proposed standard is under the rules of ISO/TC 211. However, as a joint project between OGC and ISO/TC 211, OGC members are eligible to serve on a Joint Editing Committee together with those nominated directly by ISO/TC 211. Hence, the most direct way for OGC members to be involved in the progress of O&M is to nominate for the Joint Editing Committee. Nevertheless, there will be OGC members who choose not to join the ISO EC, so the O&M SWG will provide a means for them to maintain an interest in the progress and status of the work

The Scope of Work (SOW) of the O&M SWG will be to (a) monitor the progress of the ISO 19156 Editing Committee, review changes proposed to the standard, and respond to ISO/TC 211 in a timely manner (b) collect CRPs submitted by OGC members, evaluate each of these proposals, and dispose of them in a manner which is consistent with OGC processes respecting the liaison arrangement with ISO/TC 211. This shall be achieved by (i) referring the content of CRPs that are found to impact on core O&M to ISO 19156 EC for disposal, while (ii) CRPs that extend or profile core O&M may be considered independently by the O&M SWG.

The "core O&M " is defined by the scope statement in the O&M draft document submitted to ISO (see 3.2), and corresponds with the  elements in the UML packages in the model described in that document. The OGC O&M SWG shall provide timely feedback to ISO 19156 EC on issues raised by OGC members relating to the core O&M models.

The SWG may announce cut-off dates for the submission of CRPs that are to be addressed in accordance with the OGC TC Policy and Procedures. 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 deliverables of the SWG will be revisions of the standard for consideration by the membership for adoption.

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 either  (a) of ISO/TC 211, or (b) as identified in the OGC TC Policy and Procedures, will be addressed.  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

In support of the NWIP submission to ISO/TC 211, a revised draft of the O&M specification document was prepared using the ISO template with the content modified to conform to ISO expectations.  This is based on OGC O&M (07-022r1 and 07-002r3) and has been made available through the OGC portal as OGC document 08-141. This will form the baseline for the work of the SWG.

The primary changes relative to OGC O&M are (i) re-organization into the ISO template, (ii) consistent use of normative language, (iii) re-structuring of the presentation around the normative elements in the UML model, and (iv) re-packaging of the model and encoding to better support conformance testing. In most cases the changes to the document have no effect on the functional content of the standard, though a small number of changes to the model have been made in response to application experience.  The proposed normative changes are described in an Annex F of 08-141.

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

The SWG will remain active until the disbandment of the ISO 19156 EC, with the expectation that standard(s) issued as a result of the work of ISO 19156 EC be also issued as an OGC standard(s). Documents describing extensions to, or profiles of, the O&M standard may be submitted to the OGC TC for publication as separate standards.

The work on revision of O&M will be finished after the following milestones have been achieved:

1.       The SWG has completed the evaluation of all CRPs submitted prior to the cut-off date, and their referral to ISO/TC 211 for resolution, or resolution and incorporation into the candidate extensions or profiles of the standard within OGC.

2.       A revised version of O&M has been issued by ISO, and then provided for publication through OGC.

3.       Completion of a 30 day public comment period.

4.       Approval by the SWG membership of a recommendation to submit the document to the TC for consideration as a revision of the OpenGIS® Observations and Measurements Standard deprecating the current version.

5.       The revision of the standard has been approved by the OGC Technical and Planning Committees.

4.    Description of deliverables

The following deliverables will result from the work of this SWG:

1.       Candidates for the revision of the OpenGIS® Observations and Measurements Implementation Standard for submission to the TC. The primary document ("ISO/OGC O&M") is expected to be a major revision of the O&M standard that is identical to the result of the work of ISO 19156 EC. As part of the revision for OGC, re-classification of the standard as a Topic of the Abstract Specification might be recommended. The ISO standard may or may not include a normative XML implementation, though the OGC version is expected to. Additional standards that comprise extensions to, or profiles of, ISO/OGC O&M may also be produced.

2.       Corresponding XML schema documents associated with the revision for publication in the OGC schema repository.

3.       Release notes documenting the changes introduced in the revision.

The SWG will report the version(s) of O&M that the SWG is working on in its reports to the TC including the anticipated schedule.

Although all change requests will be addressed in each revision, some may be postponed due to the need to more quickly produce deliverables resolving higher priority requests.

5.    IPR Policy for this SWG

X RAND-Royalty Free.  ?  RAND for fee

6.    Anticipated Participants

The targeted participants of the O&M v2 SWG are (a) members of the ISO 19156 EC who are also OGC members (b) OGC members with an interest in Observation metadata, sampling of the natural environment, and sensor-web applications.

 

7.    Other informative information about the work of this SWG

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

An NSF funded project "Scientific Observations Network" (SONet), PI Mark Schildhauer (UCSB), has recently been established, with the goal of harmonizing various models for observations in environmental studies. The SWG will seek and if possible maintain liaison with this project, with the intention of generating CRPs for O&M to assist in alignment with the results of the SONet project, if applicable.

b. Details of the first meeting

The first meeting of the SWG will be held at 11am-1pm on Wednesday 3^rd December in conjunction with the meeting of the Valencia OGC Technical Committee. Call-in information will be provided to the SWG's e-mail list and on the portal calendar in advance of the meeting. The primary business of the first meeting will be to arrange for a request for comments to OGC members, to complement the ISO 19156 EC process.

c. Projected on-going meeting schedule

The work of the SWG will be carried out primarily by email and conference calls. The SWG will commence regular work when the ISO 19156 EC has been formed and its schedule announced. The volume of meetings will be determined by the number of changes proposed by ISO 19156 EC and through CRPs submitted through OGC. There will be face-to-face meetings SWG in conjunction with OGC TC meetings when needed.  

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.

Name	Organization
Simon Cox	CSIRO
Andrew Woolf	e-Science Centre, Rutherford Appleton Laboratory
Ingo Simonis	International Geospatial Services Institute
Luis Bermudez	Southeastern Universities Research Association
Alexandre Robin	Spot Image
Stefano Nativi	CNR-IMAA
Yvan GHIRARDELLI	Thales
Mike Botts	UAH
Phillip Dibner	Ecosystem Associates
Gerry Creager	TAMU

 

 
e. Convener(s)

Simon Cox, CSIRO Exploration and Mining.