© OGC 2003
– All rights reserved
9.5 Persistence and Statefulness
TBD
10 Service Definitions
UML diagrams for each service definition in the proposed model are presented in Annex C. The following subclauses discuss classes of service types in terms of the interface –
content combinations which define them. Each service implements in addition to the interfaces described a basic registry interface and service information content.
10.1 Mapping
This class of services concentrate upon the presentation of composed and rendered maps, implementing at a minimum a rendering interface. They may in addition implement a
query interface GetFeatureInfo for providing more information about the map layers which are being served. Additional processing interfaces may also be supported e.g. map
re-projection.
10.2 Object Handling
These services implement repository data access at a minimum and may also support query, update, and transaction interfaces where appropriate. As a class of services, they
focus upon the storage and retrieval of resources without too much regard to the content or type of those resources.
10.3 Registry_Catalog
Registries or catalogs are services focused upon the management of metadata, either building on or working from metadata repositories to provide query, update, translation,
tasking, or other operations on metadata resources. Although functionally similar to both object and feature handling services, registry or catalog services are really distinguished
by the metadata content which they serve.
10.4 Feature Handling
Feature handling services implement object handling interfaces specialized for feature data.
10.5 Image Handling
Image handling services implement object handling interfaces specialized for image data, which may be treated as image objects, as imagery data, as coverages, or as rendered map
layers. Given the variety of ways in which images may be accessed, there is a large number of interfaces which may potentially be involved in such services.
© OGC 2003
– All rights reserved
10.6 Sensor Web Enablement
Although sensor web enablement services focus on measurements and observations, which may be characterized as features, such content is also characterized by particularly
intricate relationships between those observations and the metadata documenting its validity, such as sensor descriptions, measurand dictionaries, mission tasks, and
processing algorithms. A combination of feature, object, and registry interfaces is appropriate for such services, but they may also involve other interfaces such as tasks and
transformations.
10.7 Client
Kategori