Open Geospatial Consortium
OGC Doc 08-127
CR-Form-v3
CHANGE REQUEST
SensorML CR ?
rev-
Current version: 1.0.1 For
HELP
on using this form, see bottom of this page or look at the pop-up text over the symbols.
Proposed change affects: AS Imp Spec X Best Practices Paper Other
Title: GML 3.2 implementation of XML schemas in 07-000
Source: CSIRO
Work item code: Date: 2008-08-25
Category: B
Use one of the following categories:
F (Critical correction)
A (corresponds to a correction in an earlier release)
B (Addition of feature),
C (Functional modification of feature)
D (Editorial modification)
Detailed explanations of the above categories can be found in the TC Policies and Procedures.
Reason for change: A GML 3.2 binding of the SensorML schemas is required for applications that wish to use the current version of GML 3.2. It is also necessary to underpin an orderly revision process for SensorML and SWE Common, in which
implementation specifics are handled separately from functional changes.
Summary of change: 1. Add ANNEX E "GML 3.2 XML Schemas for SWE Common (Normative)" containing the schema documents in the accompanying zip document
Proposed namespace
http://www.opengis.net/swe/1.0/gml32
Dependencies
- GML 3.2
http://www.opengis.net/gml/3.2
2. Add ANNEX F "GML 3.2 XML Schemas for SensorML (Normative)" containing the schema documents in the accompanying zip document
Proposed namespace
http://www.opengis.net/sensorML/1.0/gml32
Dependencies:
- GML 3.2
http://www.opengis.net/gml/3.2
- SWE Common
http://www.opengis.net/swe/1.0/gml32
Consequences if
not approved: 1. GML 3.2 applications incompatible with SensorML and SWE Common2. Confused process for functional upgrades
Clauses affected: New Annex E and F
The OGC Technical Committee Policies & Procedures 05-020r3 Affected: Abstract specifications
Best Practices Document Supporting Doc.
Other comments: The strategy of issuing GML 3.2 bindings of the current schema, separate from upgrades to the model, appears to be consistent with recent updates to OGC's versioning and namespace policies.
The details of the namespace pattern have been discussed with Clemens Portele and Paul Daisey.
One minor issue that emerged is that use of the schema/@version tag may be improved. Per OGC policy the namespace name shall be changed for both major and minor upgrades. This means that the namespace name is the key identifier for a schema, and the version attribute can be used to supplement this with the bug-fix number, rather than reproducing information encoded or implied by the namespace name.
Status
Disposition
How to create CRs using this form: Comprehensive
information and tips about how to create CRs can be found at:
Fill out the above form. The symbols above marked
contain pop-up help information about the field that they are closest to.
Obtain the latest version for the release of the specification to which the change is proposed. Use the MS Word "revision marks" feature (also known as "track changes") when making the changes. All Open GIS specifications can be downloaded from the OGC server under
http://www.opengeospa tial.org/specs/
If a Word version of the document is not available, please contact the TCC or his designee.
With "track changes" disabled, paste the entire CR form (use CTRL-A to select it) into the specification just in front of the clause
The OGC Technical Committee Policies & Procedures 05-020r3
containing the first piece of changed text. Delete those parts of the specification that are not relevant to the change request.
