40
Copyright © 2010 Open Geospatial Consortium
11.2 DescribeData operation request
11.2.1 DescribeData request parameters
A request to perform the DescribeData operation shall include the parameters listed in Table 49. This table also specifies the source of values and multiplicity of each listed
parameter, plus the meaning to servers when each optional parameter is not included in the operation request.
Table 49 — Parameters in DescribeData operation request
Names Definition
Data type and values Multiplicity and use
service Service type identifier
Character String type, not empty Value is “TJS”
One mandatory request
Operation name Character String type, not empty
Value is “DescribeData” One mandatory
version Service version
identifier Character String type, not empty
Value is “1.0” Zero or one
optional When included,
return the matching version
When omitted, return latest supported
version language
Language identifier for human readable text
Character String type, not empty Value is a two or five character
IETF RFC 4646 language identifier
Zero or one optional
For use see section 7.6
Framework URI
URI of a spatial framework to which
the attribute table can be joined.
URI type, not empty Value is a FrameworkURI as found
in the DescribeFrameworks response.
One mandatory
DatasetURI URI of an attribute table,
which can be joined to the spatial framework
identified by the FrameworkURI.
URI type, not empty Value is a DatasetURI as found in
the DescribeDatasets response. One mandatory
Attributes The names of the
attributes for which descriptions are
requested from the server.
Character String type, not empty Value is one or more
ColumnsetAttributesColumn names as found in the
DescribeData response, in comma-delimited format.
Zero or one optional
a
a Attribute names are normally unknown during an initial DescribeData request to the server, and therefore this parameter is normally absent from such a request. If this parameter is absent, the response shall include descriptions of all attributes
available for the specified dataset.
NOTE 1 The parameters shaded in gray above are largely copied from Table 3 in Subclause 7.3 of this document.
NOTE 2: The values for all fields shall be encoded using the standard Internet practice for encoding URLs [IETF RFC 1738].
Copyright © 2010 Open Geospatial Consortium
41
11.2.2 DescribeData request KVP encoding
Kategori