Catalogue (CSW) Query results default ordering inconsistency
All Fields marked with * are mandatory.
Change Request 50
#:
Assigned OGC 10-015
Document #:
Name: *Lorenzo Bigagli
Organization: *IMAA-CNR
Email: *lorenzo.bigagli@cnr.it
Document
Name/Version:
*Catalogue Service Implementation Specification / 2.0.2
OGC Project
Document:
*07-006r1
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:
Source:
*Query results default ordering inconsistency
*CAT 3.0 SWG
Work item code:
Category:
*
Reason for *
change:
The default ordering of query results in inconsistently defined in the document:
- Table 10 (UML attributes and roles in “query” operation request):
sortSpec default is sorted on ID in descending order
- §10.8.4.12 SortBy parameter:
no default defined
- Table 65 (KVP encoding for GetRecords operation request):
default action is to present the records in the order in which they are retrieved
Summary of *
change:
The UML model should not define a default ordering. Individual
Application Profiles may define a default, if considered useful.
In general, requirements on ordering may negatively impact the
implementation of distributed queries, so the issue should be
carefully considered
Consequences if Inconsistency in the specification
not approved:
1 of 2
Clauses affected: *
Table 10, 11, 65 and §10.8.4.12
Additional 06-131r6_EO_EP_0.2.5 (note 10 should be deleted); possibly other Application Profiles
Documents
affected:
Supporting
Documentation:
Comments:
Status:
Disposition:
2 of 2
Change Request 50
#:
Assigned OGC 10-015
Document #:
Name: *Lorenzo Bigagli
Organization: *IMAA-CNR
Email: *lorenzo.bigagli@cnr.it
Document
Name/Version:
*Catalogue Service Implementation Specification / 2.0.2
OGC Project
Document:
*07-006r1
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:
Source:
*Query results default ordering inconsistency
*CAT 3.0 SWG
Work item code:
Category:
*
Reason for *
change:
The default ordering of query results in inconsistently defined in the document:
- Table 10 (UML attributes and roles in “query” operation request):
sortSpec default is sorted on ID in descending order
- §10.8.4.12 SortBy parameter:
no default defined
- Table 65 (KVP encoding for GetRecords operation request):
default action is to present the records in the order in which they are retrieved
Summary of *
change:
The UML model should not define a default ordering. Individual
Application Profiles may define a default, if considered useful.
In general, requirements on ordering may negatively impact the
implementation of distributed queries, so the issue should be
carefully considered
Consequences if Inconsistency in the specification
not approved:
1 of 2
Clauses affected: *
Table 10, 11, 65 and §10.8.4.12
Additional 06-131r6_EO_EP_0.2.5 (note 10 should be deleted); possibly other Application Profiles
Documents
affected:
Supporting
Documentation:
Comments:
Status:
Disposition:
2 of 2