ࡱ > ( bjbj 7 8 ' n
P P - - C/ 3 \ 3 3 3 3 8 34 \ 4 3 5 ( 5 j %6 %6 %7 8 8 4 8 d f f f f f f
Z f / @ 8 8 8 9 : X f - - %7 %7 { F `B `B `B ; - %7 / %7 d `B 8 d `B `B { H . h %7 `ʑ:@ 3 = } P H z~ ? $ | b 2 z p 8 8 `B 8 8 8 8 8 f f @ f 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 P Y, : Open Geospatial Consortium OGC Doc 09-137xx-xxx
CR-Form-v3CHANGE REQUEST(CSW-ebRIM Registry Service Part 1: ebRIM profile of CSWCR?( rev-( Current version:(For HYPERLINK "https://portal.opengeospatial.org/files/?artifact_id=10678" \n HELP on using this form, see bottom of this page or look at the pop-up text over the ( symbols.Proposed change affects: (AS Imp SpecXBest Practices Paper OtherTitle: (Improve elementSetName parameter definitionSource: (Frederic Houbie and Fabian SkiveeWork item code: (Date: (2009-09-22Category: (C
Use one of the following categories:F (Critical correction)A (corresponds to a correction in an earlier release)B (Addition of feature), C (Functional modification of feature)D (Editorial modification)
Detailed explanations of the above categories canbe found in the TC Policies and Procedures.
Reason for change: (Current specification does not allow retrieving the metadata in GetRecords response. When a client wants to retrieve all the metadata matching some criteria, he has to perform a GetRecords and then a GetRepositoryItem for each result. This leads to a large number of request/responses that could be avoided by piggybacking the metadata to the GetRecords response.Summary of change: (Improve the definition of the elementSetName parameter to return the metadata when elemementSetName has the value full. This change request is related to the CR-XX-XXX Encode the metadata in GetRecords response.Consequences if (not approved:To retrieve all the metadata matching some criteria, a client of a CSW-ebRIM service will perform a GetRepositoryItem request for each result of the GetRecordsResponse. Clauses affected: (Other specs ( Other core specifications (Affected: Abstract specifications Best Practices DocumentSupporting Doc. (Other comments: (Status (Disposition (Replace section 7.5 by the following text
The OGC Catalogue Services specification (OGC 07-006r1) distinguishes three abstract property setsor viewsthat provide differing levels of detail about a catalogue item: brief, summary, and full. These abstract views are mapped to the ebRIM schema as indicated in Table 5.
Table SEQ Table \* ARABIC 5 Registry object views
View nameebRIM information itemsbriefrim:RegistryObject/@id
rim:RegistryObject/@lida
rim:RegistryObject/@objectType
rim:RegistryObject/@status
rim:RegistryObject/rim:VersionInfosummaryComplete representationb with Name and Description (in preferred languages) cfullAs for summary view, plus the Repository Item encoded in a Mime-Multipart response. See section 10.3The brief view maps to reduced rim:RegistryObject representations for any object type. The summary and full views yield the element information item corresponding to the actual object type.
a The value of the @lid attribute implicitly identifies the "version history" resource for a registry object. Its value is set by the service to coincide with the @id value of the original registry object.
b The summary and full views of a container object (RegistryPackage, ClassificationScheme, ClassificationNode) shall include only child objects (if any), not all descendants.
c As specified by the value of the the Accept-Language request header field (if present).
Example 1 Brief view of ebRIM registry object.
Example 2 Summary view of ebRIM registry object.
2007-11-14T12:18:26-08:00
The full view allows to easily retrieving all the information about a set of records in one GetRecords request.
TITLE \* MERGEFORMAT OGC 08-089r2198
PAGE
PAGE 3
COMMENTS \* MERGEFORMAT Copyright 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
PAGE 1
COMMENTS \* MERGEFORMAT Copyright 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
PAGE \# "'Page: '#''" Enter the AS or Implementation Specification Name and Number in this box. For example, WMS 1.1.1 or GML 3.0. Do not prefix the number with anything, i.e. do not use "OGC", "GSM" or "OGC" etc.
PAGE \# "'Page: '#''" Enter the CR number here. This number is allocated by the OGC support team.
PAGE \# "'Page: '#''" Enter the revision number of the CR here. If it is the first version, use a "-".
PAGE \# "'Page: '#''" Enter the version of the specification here. This number is the version of the specification to which the CR will be applied if it is approved. Make sure that the more recent version of the specification (of the relevant release) is used when creating the CR. If unsure what the latest version is, go to http://www.opengeospatial.org.
PAGE \# "'Page: '#''" For help on how to fill out a field, place the mouse pointer over the special symbol closest to the field in question.
PAGE \# "'Page: '#''" Mark one or more of the boxes with an X. AS = Abstract Specification, IS = Implementation Specification, BPD Best Practices Document, Other = DIPR/IPR, etc.
PAGE \# "'Page: '#''" Enter a concise description of the subject matter of the CR. It should be no longer than one line.
PAGE \# "'Page: '#''" Enter the source of the CR. This is either (a) one or more OGC members or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source.
PAGE \# "'Page: '#''" IF there is one, enter the work item code or issue code that is applicable to the change. These codes will relate to Work Items identified in a WBS associated with a particular OGC initiative. If there is no code, leave blank.
PAGE \# "'Page: '#''" Enter the date on which the CR was last revised.
PAGE \# "'Page: '#''" Enter a single letter corresponding to the most appropriate category listed below.
PAGE \# "'Page: '#''" Enter text which explains why the change is necessary.
PAGE \# "'Page: '#''" Enter text which describes the most important components of the change. i.e. How the change is made.
PAGE \# "'Page: '#''" Enter here the consequences if this CR was to be rejected. It is necessary to complete this section only if the CR is of category "F" (i.e. essential correction).
PAGE \# "'Page: '#''" Enter each the number of each clause which contains changes.
PAGE \# "'Page: '#''" Enter an X in the box if any other specifications are affected by this change.
PAGE \# "'Page: '#''" If known, list here the specification or best practices documents that are affected or the CRs which are linked.
PAGE \# "'Page: '#''" Explanation of Field: If there is associated documentation, such as an lengthy change request or new text for consideration, please reference the OGC document number and document title.
PAGE \# "'Page: '#''" Enter any other information which may be needed by the group being requested to approve the CR. This could include special conditions for it's approval which are not listed anywhere else above.
PAGE \# "'Page: '#''" This is the status of the change request. For a new submission, please enter NEW. Other options as the change request is processed are: Assigned, Verified, Resolved, and Closed.
PAGE \# "'Page: '#''" This field is used to assign the RWG decision for this Change Request. Options include: Deferred, Accepted, and Rejected.
# ) / 0 1 ; < = K O P Q R tkU *j h/[ 56B*CJ OJ QJ Uph h/[ 5mHsHh/[ 5CJ mHsHh/[ mHsH
h/[ 5CJ h j h/[ 5CJ aJ j h/[ 0J <OJ QJ U j zh/[
h/[ 5CJ h/[ h/[ 6
h/[ 6CJ / h/[ hw 56CJ cH dh dh dh&H h&hw 56CJ h/[ 56CJ
h/[ 5CJ 0 1 < = L M N ] R $If gd- : kdk $$If * % % % 4
* a* yt- $ $If a$gd- : kd $$If * % % % 4
* a* yt- $ $If a$gd- gd/[
% gd/[ N O R z Ff#
! $If gd-
q $If gd- $If gd- $ $If a$gd- $ $If a$gd- : kd $$If * % % % 4
* a* yt- h i j k { p 5 : kdO $$If * % % % 4
* a* yt- $If gd- : kd $$If * % % % 4
* a* yt- $ $If a$gd- : kd $$If * % % % 4
* a* yt-
\ ] ^ _ g k տ{{ttlalXa{SL{tt h/[ 5; h/[ >*h/[ >*mHsHh/[ 5;mHsH h/[ mHsH h/[ 56 h/[ j h/[ 0J <OJ QJ U j zh/[ h/[ 6!h/[ 56B*CJ OJ QJ ph %h/[ 0J 56B*CJ OJ QJ ph *j h/[ 56B*CJ OJ QJ Uph 0j h/[ 56B*CJ OJ QJ Uph !h/[ 56B*CJ OJ QJ ph k z
$If gd- : kdA $$If * % % % 4
* a* yt- Ff $If gd- $ $If a$gd- $ $If a$gd-
$If gd-
} } / M kdp
$$If * 0 3% 3 u % 4
* a* yt- $If gd- h kd $$If * 0 3% 3 u % 4
* a* p yt- d $If ^d gd-
!
#
3
4
5
6
8
>
?
@
M
N
S
]
^
_
`
b
c
d
e
f
k
n
; "
#
%
8
9
:
;
( ) * 9 Һҵ h/[ 6
h/[ CJ h/[ 56CJ h/[ 6>*CJ
h/[ 6CJ h/[ 5j h/[ 0J <OJ QJ U j zh/[ h/[ 56 h/[ G
!
"
y n n $If gd- h kd
$$If * 0 3% 3 u % 4
* a* p yt- d $If ^d gd-
$If gd- "
#
6
7
8
A
L
v $ $If a$gd- d $If ]d gd- d $If ^d gd-
$If gd- M kd $$If * 0 3% 3 u % 4
* a* yt- L
M
N
O
P
Q
= 2 2 2 2 $If gd- kdR $$If * r 3Y% 3 O
2 % 4
* a* p2 yt- Q
R
S
`
b
c
d
m ^ O A $ $If a$gd- d $If ^d gd-
$If gd- kd $$If * r 3J
Y% 3
O % 4
* a* yt- $If gd- d
e
f
g
; q f S S J $If gd- $If ^`gd- $If gd- kdy $$If * \ 3Y 3 % O 4
* a* p yt- | | $If gd- ` kdi $$If * F 3y% 3 F / % 4
* a* yt-
$If ^ `gd- !
"
+ h kd $$If * 0 % % 4
* a* p yt- d $If ^d gd-
$If gd- M kd $$If * 0 3% 3 u % 4
* a* yt- "
#
$
%
;
d $If ^d gd/[
$If gd- M kda $$If * 0 % % 4
* a* yt- $If gd- 9 > /
$If gd- M kd $$If * 0 % % 4
* a* yt- $If gd- h kd $$If * 0 % % 4
* a* p yt- 9 } } / M kd $$If * 0 % % 4
* a* yt- $If gd- h kdC $$If * 0 % % 4
* a* p yt- d $If ^d gd- - . / 2 < = X Y Z u @ üޥ !H hFhSB hX
nHtHH hFhX
H hFhX
H hFhX
j zh/[ CJ OJ QJ h/[ 5] &j h/[ 0J <OJ QJ UmH sH h/[ 5; h/[ j h/[ 0J <OJ QJ U j zh/[ h/[ 562 y n n $If gd- h kd $$If * 0 % % 4
* a* p yt- d $If ^d gd-
$If gd- 0 1 v c $If ^c gd-
M $If gd- $ $If a$gd-
$If gd- M kdZ $$If * 0 % % 4
* a* yt- 1 2 < = V W [ P B P 3 c $If ^c gd- $ $If a$gd- $If gd- kd $$If * \ % ( % 4
* a* p( yt- W X Y Z s t [ P B P 3 c $If ^c gd- $ $If a$gd- $If gd- kd $$If * \ % ( % 4
* a* p( yt- t u [ P P $If gd- kd= $$If * \ % ( % 4
* a* p( yt- X I : d $If ^d gd-
$If gd- M kd $$If * 0 % % 4
* a* yt- $If gd- M kdg $$If * 0 % % 4
* a* yt- y d $If ^d gd-
$If gd- h kd $$If * 0 % % 4
* a* p yt- y d $If ^d gd-
$If gd- h kdI $$If * 0 % % 4
* a* p yt- * b l | p g $If gd- $$If a$gd- gdX
gdX
U
&