The specified platform-neutral data can be encoded in many alternative ways, each appropriate to one or more specific platforms. This document now specifies encoding
appropriate for use of HTTP GET transfer of operations requests using KVP encoding, and for use of HTTP POST transfer of operations requests using XML or KVP
encoding. However, the same operation requests and responses and other data could be encoded for many other specific platforms, including SOAPWSDL there may be
multiple SOAPWSDL DCPs.
EXAMPLES 2 Platform-specific specifications for KVP encoding are contained in Subclauses 7.2.2, 9.2.2, and 10.2.3.
EXAMPLES 3 Platform-specific specifications for XML encoding are contained in Subclauses 7.2.3, 7.4.8, 7.4.9, 8.5, 9.2.3, 10.2.4, 13.2.2, 13.3.3, 13.4.2, and 13.5.2.
For compliance with Clause 10 of OGC Topic 12 and ISO 19119, specific OWS specifications should follow the same pattern as used here. That is, operation requests and
responses should first be specified in platform-neutral fashion, using similar tables that serve as data dictionaries for the UML model included. Each platform-neutral
specification should be followed by one or more platform-specific encodings of this data. These platform-specific encodings shall be included for each specific platform supported
by that specific OWS specification.
5.5 Data dictionary tables
The UML model data dictionary is specified herein in a series of tables. The contents of the columns in these tables are described in Table 1. The contents of these data dictionary
tables are normative, including any table footnotes.
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
9
Table 1 — Contents of data dictionary tables
Column title Column contents
Names left column
Two names for each included parameter or association or data structure. The first name is the UML model attribute or association role name.
The second name uses the XML encoding capitalization specified in Subclause 11.6.2.
Some names in the tables may appear to contain spaces, but no names contain spaces.
Definition second column
Specifies the definition of this parameter omitting un-necessary words such as “a”, “the”, and “is”. If the parameter value is the identifier of something, not
a description or definition, the definition of this parameter should read something like “Identifier of TBD”.
Data type and value third column
or Data type
if no second items are included
in rows of table Normally contains two items:
The mandatory first item is often the data type used for this parameter, using data types appropriate in a UML model, in which this parameter is a named
attribute of a UML class. Alternately, the first item can identify the class or data structure referenced by this association, and references a separate table
used to specify the contents of that class or data structure.
The optional second item in the third column of each table should indicate the source of values for this parameter, the alternative values, or other value
information, unless the values are quite clear from other listed information. Multiplicity and use
right or fourth column
or Multiplicity
if no second items are included
in rows of table Normally contains two items:
The mandatory first item specifies the multiplicity and optionality of this parameter in this data structure, either “One mandatory”, “One or more
mandatory”, “Zero or one optional”, or “Zero or more optional”. Yes, these are redundant, but we think ISO wants this information.
The second item in the right column of each table should specify how any multiplicity other than “One mandatory” shall be used. If that parameter is
optional, under what conditions shall that parameter be included or not included? If that parameter can be repeated, for what is that parameter
repeated?
When the data type used for this parameter, in the third column of such a table, is an enumeration or code list, all the values specified by a specific OWS shall be listed,
together with the meaning of each value. When this information is extensive, these values and meanings should be specified in a separate table that is referenced in the third column
of this table row.
10
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
6 Document overview
This document is organized into clauses that discuss the subjects listed in Table 2.
Table 2 — Subjects discussed in this document
Subject XML names of specified parameters and data structures
GetCapabilities operation, provided by all OWSs
Clause 7 service
request AcceptVersions
Sections updateSequence
AcceptFormats ServiceIdentification
ServiceProvider OperationsMetadata
Contents ServiceType
ServiceType
Version Title
Abstract Keywords
Fees Access
Constraints ProviderName
ProviderSite Service
Contact Operation
Parameter Constraint
Extended Capabilities
name DCP
Metadata HTTP
Get Post
URL DatasetSummary
OtherSource
Exception
report responses, for all operations of all
OWSs Clause 8
ExceptionReport Exception
ExceptionText exceptionCode
locator version
lang
Other operations except GetCapabilities
Clause 9 service
request version
GetResourceByID ResourceID
Other parameters, used by multiple OWSs
Clause 10 BoundingBox
WGS84BoundingBox Lower
Corner Upper
Corner dimensions
crs CRS
Identifier Title
Abstract Keywords
OutputFormat Metadata
Available CRS
Access Constraint
Fees PointOf
Contact Language
Description Identification
Encoding of OWS operation requests and responses
Clause 11 none
Guidance for Implementation specifications
Clause 12 none
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
11
Subject XML names of specified parameters and data structures
Other data structures, used by multiple OWSs
Clause 13 Domaintype
UnNamedDomaintype name
defaultValue PossibleValues
AllowedValues AnyValue
NoValues ValuesReference
Value Range
Minimum
Value Maximum
Value Spacing
range Closure
DataType Meaning
ValuesUnit UOM
Reference
System Manifest
ReferenceGroup ReferenceBase
Reference OperationResponse
InputData ServiceReference
The annexes to this document provide related informative information on: a Abstract test suite
b Complete XML Schema Documents, ready to use normative c UML model of data structures specified herein informative
d Reasons for including various parameters informative
NOTE The following clauses and annexes are written to be relatively independent of one another.
They may thus be read in any order, depending on reader knowledge and interests. For example, Clause 11 “Operation request and response encoding” contains detailed information supporting Clauses 7 through 10,
and may be read first or last.
7 GetCapabilities operation
7.1 Introduction