Changes are desirable to reduce ambiguity and thus increase interoperability.
5.4.5
Specific change
Change wcsCapabilities.xsd to use the owsOperationsMetadata.xsd schema specified in Recommendation Paper 03-088r6, since that document specifies the meaning of repeated
OnlineResource values.
5.4.6
Changes to WCS specificationserverclient 5.4.6.1
Implementation specification
Significant changes to the WCS Implementation Specification, to make it more consistent with Topic 12, WMS, and WCS .
5.4.6.2 Server implementation
Moderate changes to getCapabilities XML response.
5.4.6.3 Client implementation
Moderate changes to parse WCS server’s getCapabilities XML response.
5.4.7
Implementation status
Change implemented in the ows’s ows19115subset.xsd schema.
5.5 Specify meaning of repeated values of the DCPType elements inside the WCSCapabilityType; Specify what is included in the WCSCapabilityType
when one or more of the specified WCS operations are not implemented by a server; Specify meaning of repeated values of the “Format” element inside
the “Exception” element; Specify what format identification information is included in the “Format” element inside the “Exception” element.
5.5.1
Requestor
Arliss WhitesideBAE Systems
5.5.2
Document
OGC 04-006
5.5.3
Affected sections, tables, figures
7.3.3, wcsCapabilities.xsd, Subclause
5.5.4
Purpose and reason for change
Improve Interoperability. Changes are desirable to reduce ambiguity and thus increase interoperability.
© Open Geospatial Consortium 2005 7
Specific change
Change wcsCapabilities.xsd to use the owsOperationsMetadata.xsd schema specified in Recommendation Paper 03-088r6, since that document specifies the meaning of repeated
OnlineResource values.
5.5.6
Changes to WCS specificationserverclient 5.5.6.1
Implementation specification
Significant changes to the WCS Implementation Specification, to make it more consistent with Topic 12, WMS, and WCS.
5.5.6.2 Server implementation
Moderate changes to getCapabilities XML response.
5.5.6.3 Client implementation
Moderate changes to parse WCS server’s getCapabilities XML response.
5.5.6.4 Implementation status
Implemented in the owsOperationsMetadata.xsd and owsExceptionReport.xsd schema. Server and client implemented to use the new owsOperationsMetadata.xsd and
owsExceptionReport.xsd.
5.6 Remove the “version” and “updateSequence” attributes from the CoverageDescription XML element
5.6.1
Requestor
Arliss WhitesideBAE Systems
5.6.2
Document
OGC 04-006
5.6.3
Affected sections, tables, figures
Subclause 8.3.1, XML Schema describeCoverage.xsd.
5.6.4
Purpose and reason for change
Ease of Client and Server Implementations, Improve Interoperability. The “version” required and “updateSequence” optional attributes are now included in
the CoverageDescription XML element, but no use for these attributes has been defined and I can think of no practical uses.
8 © Open Geospatial Consortium 2005
5.6.5
Specific change
Remove the “version” required and “updateSequence” optional attributes from the CoverageDescription XML element, in describeCoverage.xsd. Also, remove the sentence
about these attributes in Subclause 8.3.1.
Alternately, clearly specify how each of these attributes should or can be used. Also, correct the sentence about these attributes in Subclause 8.3.1, that currently reads
“CoverageOffering has two attributes, version required and updateSequence optional, both defined as for WCS_Capabilities 7.3.1 above.”
5.6.6
Changes to WCS specificationserverclient 5.6.6.1
Implementation specification
Minor changes to the WCS Implementation Specification, but probably no changes to current implementations of a WCS since these new attributes not yet implemented.
5.6.6.2 Server implementation
