|Version 20 (modified by erikvaningen, 4 years ago)|
Two specs are defining error reports for the CSW services:
(1) CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW: OGC 07-110r2
7.9.2 Fault handling In the event that an exception report is produced for any reason, a single SOAP Fault element information item shall be included as the only child element information item of the SOAP body element (see SOAP12, sec. 5.4). The elements of the SOAP Fault are constructed as follows: a) env:Code/env:Value = ―env:Sender‖ or ―env:Receiver‖, depending on the source of the error and the HTTP status code (i.e., 4xx, 5xx); OGC 07-110r2 Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved. 15 b) env:Code/env:Subcode/env:Value = value of ows:Exception/@exceptionCode (an OWS exception code value shall be prepended with ―ows:‖); c) env:Reason/env:Text = ows:Exception/ows:ExceptionText, where @xml:lang = ows:ExceptionReport/@language; d) env:Detail contains the original ows:ExceptionReport element NOTE The ―env‖ prefix maps to the namespace URI ― http://www.w3.org/2003/05/soap-envelope‖.
(2) OGC® Cataloguing of ISO Metadata (CIM) Using the ebRIM profile of CS-W Reference number of this OGC® document: OGC 07-038
8.2.4 Error handling The statements expressed in clause 7 of the OGC Catalogue Services – ebRIM (ISO/TS 15000-3) profile of CS-W [OGC 05-025] relatively to exception reports are applicable.
(3) OGC™ Catalogue Services — ebRIM (ISO/TS 15000-3) profile of CSW: OGC 05 025r3
7.3 Exception reports Various faults or error conditions may arise while processing a request message. Several of these are predefined in this profile; they are included within a general service exception report that has <ows:ExceptionReport> as the document element. The report may include one or more <ows:Exception> elements that describe some error condition. The exception codes are qualified names where the prefix must be mapped to the “ http://www.opengis.net/cat/wrs” namespace. The exception codes and the corresponding fault conditions are listed in Table 5. A generic exception code may be supplied if a more specific code does not apply. Table 5 — Exception codes Exception code Fault condition wrs:Sender Intended for cases in which the message sender seems to have erred in some manner (this corresponds to an HTTP status code of 4xx). wrs:Receiver Intended for cases in which an unexpected condition prevented the service from fulfilling the request (this corresponds to an HTTP status code of 5xx). wrs:InvalidRequest The request message is either invalid or is not well-formed. wrs:TransactionFailed The requested transaction could not be completed. wrs:NotImplemented The (abstract) operation has not been implemented. wrs:NotFound The requested resource does not exist or could not be found. wrs:NotSupported A service option, feature, or capability is not supported.
Every operation may produce exceptions containing the wrs:InvalidRequest code if the request message is invalid in any way. If the Request-URI contains any unrecognized query parameters, these shall be ignored—an exception must not