section is provided in the attached owsContents.xsd file. The XML Schema Document that specifies the Contents section for a specific OWS to which these minimum contents
are applicable shall build upon or adapt this owsContents.xsd file. This XML Schema Document file might be named xxxContents.xsd.
7.4.9 Capabilities document XML encoding
In a “Capabilities” or service metadata XML document, all sections shall be encoded as XML elements, using the names and capitalization shown in Table 10. The XML Schema
fragment for a generic service metadata document is:
complexType name
= CapabilitiesBaseType
annotation documentation
XML encoded GetCapabilities operation response. This document provides clients with service metadata about a specific
service instance, usually including metadata about the tightly-coupled data served. If the server does not implement the updateSequence
parameter, the server shall always return the complete Capabilities document, without the updateSequence parameter. When the server
implements the updateSequence parameter and the GetCapabilities operation request included the updateSequence parameter with the
current value, the server shall return this element with only the version and updateSequence attributes. Otherwise, all optional
elements shall be included or not depending on the actual value of the Contents parameter in the GetCapabilities operation request. This base
type shall be extended by each specific OWS to include the additional contents needed.
documentation annotation
sequence element
ref =
ows:ServiceIdentification minOccurs
= element
ref =
ows:ServiceProvider minOccurs
= element
ref =
ows:OperationsMetadata minOccurs
= sequence
attribute name
= version
type =
ows:VersionType use
= required
attribute name
= updateSequence
type =
ows:UpdateSequenceType use
= optional
annotation documentation
Service metadata document version, having values that are increased whenever any change is made in service
metadata document. Values are selected by each server, and are always opaque to clients. When not supported by server, server shall not
return this attribute. documentation
annotation attribute
complexType
The above XML Schema fragment does not include the Contents section, which is different for each specific OWS and often for each version thereof. The
CapabilitiesBaseType defined shall be extended by each specific OWS to include the additional sections needed. The above schema fragment uses three separate XML Schema
Documents, named owsServiceIdentification.xsd, owsServiceProvider.xsd, and owsOperationsMetadata.xsd, which specify the contents of the ServiceIdentification,
ServiceProvider, and OperationsMetadata sections.
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
39
The XML Schema fragment for the standard “ServiceIdentification” section of Capabilities XML documents shall be as attached in the owsServiceIdentification.xsd
file. This XML Schema Document uses part of the attached owsDataIdentification.xsd file. This XML Schema Document also uses parts of an XML encoding of ISO 19115
metadata, as specified in the attached ows19115subset.xsd file.
The XML Schema fragment for the standard “ServiceProvider” section of Capabilities XML documents shall be as attached in the owsServiceProvider.xsd file. This XML
Schema Document also uses parts of an XML encoding of ISO 19115 metadata, as specified in the attached ows19115subset.xsd file.
The XML Schema Document for the standard “OperationsMetadata” section of Capabilities XML documents shall be as attached in the owsOperationsMetadata.xsd file.
This XML Schema Document uses part of the attached owsDataIdentification.xsd and owsDomainType.xsd files. This XML Schema Document may be built upon to define an
extended “OperationsMetadata” section for a specific OWS.
The XML Schema fragment for the typical minimum “Contents” section of Capabilities XML documents shall be as attached in the owsContents.xsd file. This XML Schema
Document may be built upon to define the Contents section for a specific OWS. If the ContentsBaseType in this XML Schema Document cannot be restricted and extended to
define the Contents section for a specific OWS, all other relevant parts defined in owsContents.xsd shall be used by the “ContentsType” in the wxsContents.xsd prepared
for the specific OWS.
All these XML Schema Documents contain documentation of the meaning of each element, attribute, and type, and this documentation shall be considered normative as
specified in Subclause 11.6.3.
7.4.10 Service metadata XML example
