Copyright © 2010 Open Geospatial Consortium
41
11.2.2 DescribeData request KVP encoding
mandatory
Servers shall implement HTTP GET transfer of the DescribeData operation request, using KVP encoding. The KVP encoding of this request shall use the parameters
specified in Table 49.
EXAMPLE A valid DescribeData operation request KVP encoded for HTTP GET is:
http:foo.barfoo? Service=TJS
Version=1.0 Request=DescribeData
FrameworkURI=http:foo.bar2Provinces2001 DatasetURI=http:foo.bar2001Census2001
Language=en-CA
NOTE: For clarity, the parameter values in the above example have not been URL encoded.
11.2.3 DescribeData request XML encoding
optional
Servers may also implement HTTP POST transfer of the DescribeData operation request, using XML encoding only, in accordance with the tjsDescribeData_request.xsd XML
schema.
11.3 DescribeData operation response
11.3.1 DescribeData normal response parameters
The normal response to a valid DescribeData operation request shall be a DataDescriptions data structure, which contains descriptions of one or more Attributes
for which data is available on this service. The structure of this response is shown in Table 50. Note that the Framework and Dataset data structure portions of this response
are similar to the equivalent structures in the DescribeDatasets response.
Table 50 — DescribeData response data structure
Name Definition
Data type Multiplicity and use
DataDescriptions General description of all
attribute data available on this server
DataDescriptions data structure, see Table 51
One mandatory
Table 51 — DescribeData response: DataDescriptions data structure
Name Definition
Data type and values Multiplicity and use
service Service type identifier
Character String type, not empty Value is “TJS”
One mandatory version
TJS standard and schema version
Character String type, not empty Value is “1.0”
One mandatory
42
Copyright © 2010 Open Geospatial Consortium
Name Definition
Data type and values Multiplicity and use
lang Language of the human-
readable text e.g. “en- CA”
Character String type, not empty Value is an RFC 4646 language
tag One mandatory
capabilities GetCapabilities request
URL for this service implementation
URL type One mandatory
Framework Description of a spatial
framework for which data is available
Partial data structure defined in Table 6, excluding the
FrameworkDatasetRowset element.
One mandatory
Note 1: The shaded elements in this table are identical to those in Table 43.
11.3.2 DescribeData normal response XML encoding
The DescribeData operation response shall be encoded in XML in accordance with the tjsDescribeData_response.xsd XML schema see Annex B.
11.3.3 DescribeData exceptions
When a TJS server encounters an error while performing a DescribeData operation, it shall return an exception report message as specified in Clause 8 of [OGC 06-121r3]. The
allowed standard exception codes shall include those listed in Table 20 of that document. For each listed exceptionCode, the contents of the “locator” parameter value shall be as
specified in the right column of Table 52.
Table 52 — Exception codes for DescribeDatasets operation
exceptionCode value Meaning of code
“locator” value
OperationNotSupported Request is for an operation that is not supported by this server
Name of operation not supported
MissingParameterValue Operation request does not include a parameter value, and this server did not declare a default
value for that parameter Name of missing
parameter InvalidParameterValue
Operation request contains an invalid parameter value
Name of parameter with invalid value
OptionNotSupported Request is for an option that is not supported
by this server Identifier of option
not supported
NoApplicableCode No other exceptionCode specified by this service
and server applies to this exception None, omit “locator”
parameter NOTE The values listed above are copied from Table 20 in Subclause 8.3 of [OGC 06-121r3].
Copyright © 2010 Open Geospatial Consortium
43
12 GetData operation optional
12.1 Introduction
Kategori