a CSW-discovery.xsd b CSW-publication.xsd
c records.xsd d rec-dcmes.xsd
e rec-dcterms.xsd
NOTE These XML Schema Documents use a new namespace identifier URI instead of the previous namespace
identifier URI, namely http:www.opengis.netcatcsw2.0.2 instead of http:www.opengis.netcatcsw. This change was made based on the TC decision described in Clause 11 in OGC Best Practices Paper 06-135r1. That decision was
based on the discussion in document 05-065r3 “Change Request for Namespaces for versions and profiles of XML Schemas”. A new namespace identifier URI is used for this Catalogue version 2.0.2 because these reasons apply to this
version 2.0.2. However, using this new namespace identifier URI could produce problems for the GetCapabilities operation request and response, which have not yet been resolved.
After this document is approved, these new XML Schema files will be posted at the URL http:schemas.opengis.netcatcsw2.0.2
for electronic access. In the event of a discrepancy between the attached and online versions of the XML Schema files, the
online files shall be considered authoritative. These new XML Schemas build on the XML Schemas defined in the Filter Encoding
Implementation Specification [OGC 04-095], and the OWS Common Implementation Specification [OGC 05-008c1], and described in those documents.
11 Specializing general model through protocol bindings and profiles
11.1 Introduction
This subclause provides an overview of the core elements of the General Catalogue Model and how these may be used in protocol bindings and application profiles.
The General Catalogue Model consists of an abstract model and a General Interface Model. The abstract query model specifies a BNF grammar for a minimal query syntax
and a set of core search attributes names, definitions, conceptual datatypes.The General Interface Model specifies a set of service interfaces that support the discovery, access,
maintenance and organization of catalogues of geospatial information and related resources; these interfaces may be bound to multiple application protocols, including the
HTTP protocol that underlies the World Wide Web. This specification also specifies bindings to CORBAIIOP and Z39.50. Furthermore, all behaviour requiring sessions is
expressed by a dynamic model of conversation state and state transitions. The model expresses the states and messages that trigger the changes in state.
Implementations are constrained by the protocol binding clauses of this specification. Each protocol binding includes a mapping from the general interfaces, operations, and
parameters specified in this clause to the constructs available in a chosen protocol. Application profiles are intended to further document implementation choices.
An Application Profile is based on one of the protocol bindings in the base specification. In the case of the Catalogue Services Specification, a profile could reference
176
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
CORBAIIOP, Z39.50, or the HTTP1.1 protocol bindings. In most, but not all, protocol bindings, there may be restrictions or refinements on implementation agreed within an
implementation community. A graphic model of the relationships is shown in Figure 31.
mapsTo General
model 1
Protocol binding
Application profile
Interop agreement
uses
Figure 31 — Relationship of general model, protocol binding, and application profile
11.2 Interface definitions
