[Requests] ebRIM profile of CSW (RFPC 29) Response

Jason Cupp jcupp at esri.com
Fri Feb 17 11:12:00 EST 2006


PART A
------

1. Evaluator: Jason Cupp <jcupp at esri.com>


2. Submission: OGC Request 29, OpenGIS Catalogue Services - ebRIM
profile of CSW (ebRIM)

PART B
------

1. Specification Section number: 7.2 - Use of common message header
fields


2. Criticality: EDITORIAL


3. Comments/justifications for changes:
If using various HTTP headers is recommended and should be honored, then
it would be convenient if Table 4 had an additional column that stated
either "Request" or "Response" according to the HTTP header.

1. Specification Section number: 7.2 - Use of common message header
fields


2. Criticality: MAJOR


3. Comments/justifications for changes:
If using various HTTP headers is recommended and should be honored, then
the document should specify the behavior of combinations of the Accept
header and the outputFormat parameter of the DescribeRecord and
GetRecords requests.

Suggest the following behavior:

Accept      / output
HTTP header / Format  / resulting behavior
=================================================
NO          / NO      / use the default: application/xml
YES         / NO      / use the value of the Accept header
YES         / YES     / if values are different then raise exception
NO          / YES     / use the value of outputFormat


1. Specification Section number: 8.1.2 - GetCapabilities request


2. Criticality: EDITORIAL


3. Comments/justifications for changes:
The value of the service type identifier is too long and isn't like
other W*S services. Suggest "csw-ebrim" instead of the URN value so it
conforms to the other W*S service type values: "wms", "wfs", "csw",
etc...

1. Specification Section number: 8.1.3 - GetCapabilities response


2. Criticality: EDITORIAL


3. Comments/justifications for changes:
The paragraph that starts "All the top-level elements..." uses an odd
tense. Suggest: "All of the top-level elements (sections) must be
included if the sections request parameter is absent; otherwise only the
specified top-level elements are included in the response."

1. Specification Section number: 9.1.4 - csw:Query statements


2. Criticality: EDITORIAL


3. Comments/justifications for changes:
In the second paragraph, delete the word "type" from the second sentence
starting with "Each value in the list...". A qualified name (QName) is
what each value must be, not "qualified type name". We know that a
"value" must have the syntax of a "qualified name" and that, from the
first sentence, the values represent object types that constitute the
scope of the query.



More information about the Requests mailing list