anchor.diff:              Authorization: Bearer <token>
   
       + Attributes (object)
  -        + organization: `org.apache` (string, required)
  +        + organization: `apache` (string, required)
   
               The organization which built the software for which the configuration is meant.
   
               Regex: ^[a-zA-Z0-9\.\-]+$
   
  -        + application: `hive` (string, required)
  +        + application: `tomcat` (string, required)
   
               The application for which the configuration is meant.
   
               Regex: ^[a-zA-Z0-9\.\-]+$
   
  -        + scope: `database` (string, required)
  +        + scope: `server.xml` (string, required)
   
               Often different parts of an application have different configurations. Here the application specific scope can be defined.
   
               Regex: ^[a-zA-Z0-9\.\-]+$
   
  -        + slug: `sample-snippet-for-devs` (string, required)
  +        + slug: `tomcat9-serverxml-example` (string, required)
   
               A unique slug that identifies the entry and configuration snippet further. It only needs to be unique within the namespace created by `organization`, `application` and `scope`.
   
               Regex: ^[a-zA-Z0-9\.\-]+$
   
  -        + title: `Sample snippet for developers` (string, required)
  +        + title: `Tomcat 9 configuration for server.xml` (string, required)
   
               A title for the entry that ideally explains already what the snippet is about.
   
               Regex: ^[^\n\r]{3,}$
   
  -        + description: `This is a sample conf snippet for Apaches Hive database module.` (string, required)
  +        + description: `The server.xml is Tomcats main configuration file and therefore very important. ...` (string, required)
   
               An extended description for the entry that explains in detail what the snippet is about. It can also contain instructions on how to use the snippet.
   
               Regex: ^[\S\s]{3,}$
   
  -        + tags: `dev`, `developer`, `db-dev` (array[string], optional)
  +        + tags: `tomcat9`, `tomcat` (array[string], optional)
   
               A list of tags that shall be added to the entry. Tags may be used for search, so they ideally add additional information that is not already available by the other inputs.
   
               Regex: ^[a-z0-9\-\.]{3,20}$
   
           + configuration (object)
  -            + value: `sampleKey = sampleValue` (string, required)
  -
  -                The configuration for which a new database entry should be created. It can be of any supported format, in this example **ini** is used.
  -
  -            + format: `ini` (string, required)
  +            + value: `<?xml version="1.0" encoding="UTF-8"?><Server>...</Server>` (string, required)
  +
  +                The configuration snippet for which a new database entry should be created. It can be of any supported format.
  +
  +            + format: `xml` (string, required)
   
                   The format of the supplied configuration snippet. It has to be in the list of supported formats, see `/conversion/formats`.
   
  
positive.code: + Response 200 (application/json)
      + Attributes (object)
          + elektra (object) - Detailed version information about the used Elektra library
              + version (string) - The currently used version in its complete format
              + major (number) - The currently used major version
              + minor (number) - The currently used minor version
              + micro (number) - The currently used micro version
          + api (number) - The version of the API itself
  
  
  
  
negative.code: This operation can only be executed by the owner of an entry as well as moderators (rank 50) or higher.
  
  + Parameters
      + organization: `apache` (string, required) - The `organization` who built the `application` for which the configuration of the entry is meant
      + application: `tomcat` (string, required) - The `application` to which the configuration of the entry belongs to
      + scope: `server.xml` (string, required) - The `application` specific `scope` to which the configuration of the entry belongs to
      + slug: `tomcat9-serverxml-example` (string, required) - The identifier of the entry that is unique within the namespace created by `organization`, `application` and `scope`
  
  + Request (application/json)
      + Headers
  