Fixed inconsist schema of openEO error responses: Field is now consistently named message instead of description.

Author: m-mohr

CHANGELOG.md

@@ -32,6 +32,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Added missing required descriptions to process definitions.
 - Added missing error messages.
 - Fixed unclear specification for arrays used as process graph arguments.
+- Fixed inconsist schema of openEO error responses: Field is now consistently named `message` instead of `description`.
 
 ## [0.3.0] - 2018-09-21
 First version after proof of concept tackling many major issues. No changelog available.

openapi.json

@@ -3398,7 +3398,7 @@
             "description": "The code is either one of the standardized error codes or a custom error code with a number greater than 10000.",
             "example": 123
           },
-          "description": {
+          "message": {
             "type": "string",
             "description": "A message explaining what the client may need to change or what the server is struggling with. By default the message must be sent in English language. Content Negotiation is used to localize the error messages: If an Accept-Language header is sent by the client and a translation is available, the message should be translated accordingly and the Content-Language header must be present in the response.",
             "example": "A sample error message."