All Fields marked with
*
are mandatory.
Change Request
#:
119
Assigned OGC
Document #:
10-187
Name:
*
Panagiotis (Peter) Vretanos
Organization:
*
CubeWerx Inc.
Email:
*
pvretano@cubewerx.com
Document
Name/Version:
*
CSW-ebRIM Registry Service – Part 2: Basic extension package / 1.0.1
OGC Project
Document:
*
07-144r4
If this is a revision of a previous submission and you have a Change Request Number, then check here:
Enter the CR number here:
Enter the Revsion Number that you are revising here:
Title:
*
Extend basic package to describe actual OGC artifacts.
Source:
*
???
Work item code:
Category:
*
Reason for
change:
*
The basic package currently describe a very small subset of OGC artifacts and is missing what I believe most people would consider basic object types. For example there are no object type identifiers to distinguish between a wms layer and a wfs featute type. This makes the csw fairly useless without additional extension packages. I
believe that an ogc catalogue should be able to harvest ogc artifacts right out of the box without additional packages.
Summary of
change:
*
1) Figure out from the set of OGC artifacts which might need to be catalogued. Surely a wms layer is a basic ogc artifact that we would want to be catalogued.
2) Figure out what associations and classifications exist for and among the set of objects identified in (1).
3) Revise the basic package accordingly.
Consequences if
not approved:
1) Right out of the box a current CSW-ebRIM catalogue is not very useful at registering and cataloging OGC objects.
2) OGC catalogues will be even less interoperable than they are now if each implementation uses its own object/association/classification identifiers. This is even a problem if two extension packages define different identifiers for the same object types ... for example.
