| | 27 | OGC™ Catalogue Services — ebRIM (ISO/TS 15000-3) profile of CSW: OGC 05 025r3 |
| | 28 | |
| | 29 | 7.3 Exception reports |
| | 30 | 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. |
| | 31 | Table 5 — Exception codes |
| | 32 | Exception code Fault condition |
| | 33 | 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). |
| | 34 | 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). |
| | 35 | wrs:InvalidRequest The request message is either invalid or is not well-formed. |
| | 36 | wrs:TransactionFailed The requested transaction could not be completed. |
| | 37 | wrs:NotImplemented The (abstract) operation has not been implemented. |
| | 38 | wrs:NotFound The requested resource does not exist or could not be found. |
| | 39 | wrs:NotSupported A service option, feature, or capability is not supported. |
| | 40 | |
| | 41 | 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 |
