Interface definitions Change Requests | OGC

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

The various elements of the General Catalogue Interface Model provide functional behaviours and capabilities to address particular areas of concern. A protocol binding may realise specific configurations of these components to serve different purposes e.g. a read-only catalogue for discovery, a transactional catalogue for discovery and publication, or a ‘stateful’ catalogue that also supports session management. A compliant protocol binding of the catalogue service is required to implement the OGC_Service, Catalogue Service, and Discovery classes. A protocol binding may also include any of the optional classes associated with the Catalogue Service class. A compliant implementation of a protocol binding shall recognise all operations defined within each class included in the protocol binding, and shall generate a service exception report indicating when a particular operation is not implemented in such cases the operation is abstract—an implementation is not required. The protocol binding clauses of this specification provides more detail on the implementation of the general interfaces. In effect, each binding maps these interfaces to a particular application protocol. For example, the names of the classes and operations in this general UML model are changed in some of the protocol bindings. The names of some operation parameters are also changed in some protocol bindings. However, the interfaces and operations specified in all Protocol Bindings shall be consistent with the semantics and granularity of interaction specified in the General Interface Model. Application profiles, which will appear as separate documents may further specialise the implementation of these interfaces and their operations, including adding classes and parameters. However, the application profile is a specialization of the parent protocol binding, in that the names of the operations and the parameters cannot be changed. Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. 177

11.3 Query model components