anchor.diff:          + data (object) - The actual details about the entry
               + key (object) - The key and its separate parts
                   + full (string) - The full key (path) of the entry
  -                + scope (string) - The scope of the configuration snippet
                   + organization (string) - The organization of the application to which the snippet belongs to
                   + application (string) - The application to which the snippet belongs to
  -                + appscope (string) - The application internal scope for the configuration snippet
  +                + scope (string) - The application internal scope for the configuration snippet
                   + slug (string) - The unique identification slug of the entry
               + meta (object) - Additional information about the entry
                   + title (string) - The descriptive title of the entry
  
positive.code:             }
  
  
  ## Delete an entry [DELETE /database/{scope}/{organization}/{application}/{appscope}/{slug}]
  
  Deletes an entry from the database. This operation requires moderator permissions (rank 2).
  
  + Parameters
      + scope (string, required) - The `scope` for the configuration snippet of the entry
      + organization (string, required) - The `organization` who built the `application` for which the configuration of the entry is meant
      + application (string, required) - The `application` to which the configuration of the entry belongs to
      + appscope (string, required) - The `application` specific `scope` to which the configuration of the entry belongs to
      + slug (string, required) - The unique identifier of the requested entry
  
  + Response 200 (application/json)
  
negative.code:         + i18n (string) - A unique token representing above error description message; can be used for internationalization in frontends
  
              A comprehensive list of possible errors:
              - `ENTRY_DOES_ALREADY_EXIST` if an entry with the supplied four key parts (`organization`, `application`, `scope` and `slug`) does already exist.
          
      + Schema
  
              {
                  "type": "object",
                  "properties": {
                      "status": {
                          "description": "HTTP status code",
                          "type": "integer",
                          "minimum": 0
                      },
                      "error": {
                          "description": "Textual description of HTTP status code",
                          "type": "string"
                      },
                      "message": {
                          "description": "Detailed information about the error.",
                          "type": "string"
                      },
                      "i18n": {
                          "description": "Unique message token that can be used for localization in a frontend application.",
                          "type": "string"
                      }
                  },
                  "required": [
                      "status",
                      "message",
                      "i18n"
                  ],
                  "additionalProperties": false
              }
  
  
  ## Update an existing entry [PUT /database/{organization}/{application}/{scope}/{slug}]
  
  Updates the entry with the specified key (path). All fields will be overridden with the supplied data. If no or empty data is supplied, it will be used instead (especially important for `tags`).
  
  + Parameters
      + organization (string, required) - The `organization` who built the `application` for which the configuration of the entry is meant
      + application (string, required) - The `application` to which the configuration of the entry belongs to
      + scope (string, required) - The `application` specific `scope` to which the configuration of the entry belongs to
      + slug (string, required) - The unique identifier of the requested entry
  
  + Request (application/x-www-form-urlencoded)
  