Defining stored queries Change Requests | OGC
30
Copyright © 2009 Open Geospatial Consortium, Inc. All Rights Reserved.
For example, a ‘Portrayal’ package might include elements for working with the style descriptors and symbol collections used in map production. A ‘Geodesy’ package can include elements for
defining coordinate reference systems and related components such as a datum and a prime meridian.
ebRIM 3.0 Basic Package
objectTypes, associationTypes, Slots, ClassificationSchemes Remote
Sensing Geodesy
Portrayal
?
Figure 6 -- Extension packages
An extension package is essentially a container for metadata resources used to describe or characterize other registry objects. It is represented as a rim:RegistryPackage instance. Package
members are registry objects that are subject to the following deletion constraint: a member object may only be deleted if the package as a whole is deleted—this effectively treats an
extension package as a composition. A supplementary specification document shall also be included; it provides general guidance about using the package, defines slots, and stipulates
additional constraints that must be satisfied.
Each extension package is itself the member of a ‘root’ package that contains all packages supported by the service. The identifier of this root package is: “urn:ogc:def:ebRIM-
RegistryPackage:OGC:Root”.
The Basic extension package specification OGC 07-144r3 constitutes the second part of the CSW-ebRIM catalogue profile—all conforming implementations shall support it. Additional
packages may be defined by other parties as needed; these may employ elements of ebRIM and the Basic package as suggested in Figure 6. A package dependency shall be indicated using an
association of the following type: “urn:oasis:names:tc:ebxml-regrep:AssociationType:Uses”.