WCS 1.1.2 Change_Request - Refactor XML Schemas
OGC Doc 08-196r1
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
WCS 1.1.2 CR 08-196
rev
R1
Current version:
1.1.2
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
Title:
WCS 1.1.2 Change Request - Refactor XML Schemas
Source:
PCI Geomatics
Work item code:
Category:
Other
Date:
D
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:
To separate the XML Schemas for requests from the response XML Schemas
Summary of change: The XML encodings for WCS requests and responses are defined in the same
file usually named after the request. It is better to split the request schemas and
the response schemas into separate files.
The coverage description response has also been refactored into
wcsDescribeCoverageResponse.xsd and wcsCoverage.xsd – this is a step
closer to making the WCS Coverage more independent of the WCS service so
that it can be reused outside of the WCS service.
Consequences if
not approved:
There are several request encodings (KVP, XML) but usually only one XML
response encoding so it makes sense to not integrate them both into the same
XML Schema document. Organizations implementing only the KVP request
encoding doesn’t care about the XML request schemas. There is also a slight
confusion when referring to the request or response XML Schemas because the
current method bases the XSD file name on the request name.
The coverage description refactoring will make it easier for the SWE group to
reuse coverages thus possibly making it easier to harmonize.
Clauses affected:
Other specs
Affected:
Supporting Doc.
Other core specifications
Abstract specifications
Recommendation Papers
The OGC Technical Committee Policies & Procedures 05-020r3
Other comments:
The change request is included in a ZIP file containing both this document and
the XML Schemas split between the requests and responses. Any changes to
the actual WCS specification due to this change request are not yet resolved by
this change request.
The XML schemas in this change request are fully backwards compatible with
the WCS 1.1.2 XML Schemas.
Another refactoring that could be done is to move the list of interpolation
methods out of the Field thus making the CoverageType more of a list of
metadata on a Coverage rather than listing what can be requested.
Status
Disposition
Last Revision Date: 14 January 2018
Page2
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
WCS 1.1.2 CR 08-196
rev
R1
Current version:
1.1.2
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
Title:
WCS 1.1.2 Change Request - Refactor XML Schemas
Source:
PCI Geomatics
Work item code:
Category:
Other
Date:
D
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:
To separate the XML Schemas for requests from the response XML Schemas
Summary of change: The XML encodings for WCS requests and responses are defined in the same
file usually named after the request. It is better to split the request schemas and
the response schemas into separate files.
The coverage description response has also been refactored into
wcsDescribeCoverageResponse.xsd and wcsCoverage.xsd – this is a step
closer to making the WCS Coverage more independent of the WCS service so
that it can be reused outside of the WCS service.
Consequences if
not approved:
There are several request encodings (KVP, XML) but usually only one XML
response encoding so it makes sense to not integrate them both into the same
XML Schema document. Organizations implementing only the KVP request
encoding doesn’t care about the XML request schemas. There is also a slight
confusion when referring to the request or response XML Schemas because the
current method bases the XSD file name on the request name.
The coverage description refactoring will make it easier for the SWE group to
reuse coverages thus possibly making it easier to harmonize.
Clauses affected:
Other specs
Affected:
Supporting Doc.
Other core specifications
Abstract specifications
Recommendation Papers
The OGC Technical Committee Policies & Procedures 05-020r3
Other comments:
The change request is included in a ZIP file containing both this document and
the XML Schemas split between the requests and responses. Any changes to
the actual WCS specification due to this change request are not yet resolved by
this change request.
The XML schemas in this change request are fully backwards compatible with
the WCS 1.1.2 XML Schemas.
Another refactoring that could be done is to move the list of interpolation
methods out of the Field thus making the CoverageType more of a list of
metadata on a Coverage rather than listing what can be requested.
Status
Disposition
Last Revision Date: 14 January 2018
Page2