W3C Recommendation 2 May 2001: XML Schema Part 0: Primer, http:www.w3.orgTR2001REC-xmlschema-0-20010502
W3C Recommendation 2 May 2001: XML Schema Part 1: Structures, http:www.w3.orgTR2001REC-xmlschema-1-20010502
W3C Recommendation 2 May 2001: XML Schema Part 2: Datatypes, http:www.w3.orgTR2001REC-xmlschema-2-20010502
In addition to this document, this specification includes a number of normative XML Schema Document files. Following approval of this document, these files will be posted
online at the URL http:schemas.opengis.netows1.1.0
. These files are also bundled with the present document. In the event of a discrepancy between the bundled and online
versions of the XML Schema Document files, the online files shall be considered authoritative.
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
4.2
4.3
4.4
4.5 bounding box
portion of a coordinate space that lies between a lower bound and an upper bound in each dimension of a coordinate reference system
NOTE A bounding box can be used to express spatial-temporal query constraints, or to describe the
approximate location and extent of geospatial data. A bounding box is often called the minimum bounding rectangle of a geospatial data item when its lower and upper bounds in each dimension are those
of the data item.
EXAMPLES Rectangle in two spatial dimensions, rectangular solid in three spatial dimensions
capabilities XML service metadata encoded in XML
client software component that can invoke an operation from a server
geographic information information concerning phenomena implicitly or explicitly associated with a location
relative to the Earth [ISO 19128 draft]
interface named set of operations that characterize the behaviour of an entity [ISO 19119]
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
3
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13 operation
specification of a transformation or query that an object may be called to execute [ISO 19119]
parameter variable whose name and value are included in an operation request or response
platform the underlying infrastructure in a distributed system Adapted from ISO 19119
NOTE A platform describes the hardware and software components used in a distributed system. To
achieve interoperability, an infrastructure that allows the components of a distributed system to interoperate is needed. This infrastructure, which may be provided by a Distributed Computing Platform DCP, allows
objects to interoperate across computer networks, hardware platforms, operating systems and programming languages. Adapted from Subclause 10.1 of ISO 19119
platform-neutral specification independent of a specific platform Adapted from ISO 19119
NOTE It is assumed that one platform-neutral service specification will be the basis for multiple
platform-specific service specifications. Multiple platform-specific specifications are necessary because of the variety of DCPs and the differences in the way in which they support the functional requirements. One
platform-neutral service specification is needed to support interoperability of multiple platform-specific specifications. Adapted from Subclause 10.2 of ISO 19119
platform-specific specification dependent on a specific platform Adapted from ISO 19119
request invocation of an operation by a client
response result of an operation, returned from a server to a client
resource any addressable unit of information or service [IETF RFC 2396]
EXAMPLES Examples include files, images, documents, programs, and query results.
NOTE The means used for addressing a resource is a URI Uniform Resource Identifier reference
4
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
4.14
4.15
4.16
4.17 server
