anchor.diff:  by just defining some rules in XML configuration or Java DSL. Let's start with this chapter by introducing some basic
   concepts of the schema validation.
   
  +[[managing-schemas]]
   === Managing schemas
   Most complex applications have a lot of schemas that are relevant for different use cases. To organize these schemas
   in your test cases, Citrus brings you some structuring capabilities.
   
  +[[schema-definitions]]
   ==== Schema definitions
   [source,xml]
   ----
  
positive.code: Citrus allows you to reuse your schema definition within your context by referencing them. For a valid reference,
  the id of the schema and the value of the schema Attribute within the reference Element have to match.
  
  ==== Schema location definitions
  [source,xml]
  ----
  
negative.code: This xml snippet allows you to define a schema identified by its id, located at the given classpath.
  Please keep in mind, that the id of the schema has to be unique within the context.
  
  [[schema-references]]
  ==== Schema references
  [source,xml]
  ----
  