Copyright © 2010 Open Geospatial Consortium, Inc.
13
7.2 GetCapabilities request
7.2.1 GetCapabilities request parameters
A request to perform the GetCapabilities operation shall use the data structure described in Figure 2 and specified in Table 3.
Figure 2 — GetCapabilities operation request UML class diagram
GetCapabilities
+ service: CharacterString + request: CharacterString = GetCapabilities {frozen}
+ acceptVersions [0..1]: SequenceCharacterString + sections [0..1]: ListSection
+ acceptFormats [0..1]: SequenceCharacterString + updateSequence [0..1]: CharacterString
+ acceptLanguages [0..1]: SequenceCharacterString
«CodeList»
Section
+ serviceIdentification + serviceProvider
+ operationMetadata + contents
+ all
14
Copyright © 2010 Open Geospatial Consortium, Inc.
Table 3 — Parameters in GetCapabilities operation request
Names
a
Definition Data type and value
Multiplicity and use
service service
Service type identifier Character String type, not empty
Value is OWS type abbreviation e.g., ―WMS‖, ―WFS‖
One mandatory
request request
Operation name Character String type, not empty
Value is operation name e.g., ―GetCapabilities‖
One mandatory
accept Versions
Accept Versions
Prioritized sequence of one or more specification
versions accepted by client, with preferred
versions listed first Sequence of Character String
type, each not empty Value is list of x.y.z ―version‖
values Zero or one optional
When omitted, return latest supported
version see Subclause 7.3.2
sections Sections
Unordered list of zero or more names of requested
sections in complete service metadata
document
b
Sequence of Character String type, each not empty
Value is list of section names Allowed section names are
specified by each Implementation Specification
Zero or one optional When omitted or not
supported by server, return complete
service metadata document
c
update Sequence
update Sequence
Service metadata document version, value is
―increased‖ whenever any change is made in
complete service metadata document
Character String type, not empty Values are selected by each
server, and are always opaque to clients
Zero or one optional When omitted or not
supported by server, return latest service
metadata document
c
accept Formats
Accept Formats
Prioritized sequence of zero or more response formats
desired by client, with preferred formats listed
first Sequence of Character String
type, each not empty Value is list of format identifiers
Identifiers are MIME types of formats useful for service
metadata documents Zero or one optional
When omitted or not supported by server,
return service metadata document
using MIME type textxml
acceptLang uages
AcceptLan guages
Sequence of one or more languages for human
readable text requested by the client.
Sequence of Character String type, not empty
Value is list of language identifiers as specified in IETF
RFC 4646, plus ―‖ Zero or one optional
For use see section 7.3.6
a Although some values listed in the ―Name‖ column appear to contain spaces, they shall not contain spaces.
b The ―Sections‖ parameter specifies which XML elements within a service metadata document shall be
returned, within a usually abbreviated ―Capabilities‖ element. The allowed section name values shall be specified by each Implementation Specification, as specified in Subclause 7.3.3.
c When
in conflict, the ―UpdateSequence‖ parameter shall take precedence over the ―Sections‖ parameter when both parameters are present in a request. Table 7 lists the conflict condition.
NOTE 1 The name capitalization rules used here are specified in Subclauses 5.5 and 11.6.2.
NOTE 2 The data type of many parameters is specified as ―Character String type, not empty‖. In the
XML Schemas specified herein, these parameters are encoded with the xsd:string type, which allows an empty string. Nevertheless, ―not empty‖ is a normative requirement on the values of the associated
parameter, since all contents of these tables are normative.
Copyright © 2010 Open Geospatial Consortium, Inc.
15
7.2.2 Implementation requirements
Kategori