32
Copyright © 2010 Open Geospatial Consortium
Table 39 — GetCapabilities response encoding: Languages data structure
Name Definition Data type and
values Multiplicity and
use
defaultLanguage Default language of all service
responses e.g. “en-CA”
Character String type, not empty
One mandatory Language
Language which can be selected for all service responses
Character String type, not empty
One or more optional
Note: the default language must be present in the set of Language elements. This approach facilitates the creation of a language pick list.
An example of the languages element follows
tjs:Languages defaultLanguage
=“ en-CA
” ows:Language
en-CA ows:Language
ows:Language fr-CA
ows:Language tjs:Languages
See also section 7.6
8.3.4 Identification of WSDL location
The optional WSDL element in the service metadata identifies the location from which a Web Services Description Language WSDL document describing the service can be
retrieved. Table 40 indicates the structure of this section of the Capabilities document.
Table 40 — GetCapabilities response encoding: WSDL data structure
Name Definition Data type and
values Multiplicity and
use
href The URL from which the WSDL
document can be retrieved. URL type, not
empty One mandatory
An example of the WSDL element follows
tjs:WSDL xlink :href
=”http:foo.barfoo”
8.3.5 Capabilities document XML encoding
The XML schema for a TJS service metadata document extends ows:CapabilitiesBaseType in owsCommon.xsd of [OGC 06-121r3], and is found on the
OGC website at http:schemas.opengis.net, and replicated in Appendix A.
As indicated, this XML Schema Document uses the owsServiceIdentification.xsd, owsServiceProvider.xsd, and owsOperationsMetadata.xsd schemas specified in [OGC
06-121r3]. It also uses an XML Schema Document for the “Contents” section of the TJS
Copyright © 2010 Open Geospatial Consortium
33 Capabilities XML document, which shall be as attached in the
tjsCapabilitiesContents .xsd file. 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 of [OGC
06-121r3].
8.3.6 Exceptions
When a TJS server encounters an error while performing a GetCapabilities operation, it shall return an exception report message as specified in Clause 8 of [OGC 06-121r3]. The
allowed exception codes shall include those listed in Table 5 of Subclause 7.4.1 of [OGC 06-121r3].
9 DescribeFrameworks operation optional
9.1 Introduction
The DescribeFrameworks operation returns an XML document that describes one or more spatial frameworks for which data is available from the server. This description
includes information that uniquely identifies each spatial framework, and descriptive information about each framework. This information can be used to populate a user
interface to identify the spatial framework for which the user would like to obtain attribute data. When the optional FrameworkURI parameter is included, the response can
be used to populate an “about” page for a specific framework. This operation shall be supported for all servers that implement data access, as identified
in section 6.1.1.
9.2 DescribeFrameworks operation request
9.2.1 DescribeFrameworks request parameters
A request to perform the DescribeFrameworks operation shall include the parameters listed in Table 41. 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.
