anchor.diff:  [source,listing]
   -------------------------------------------------------------------------------
   # Metamodel information
  -_config-model.provider=ConfigModel Extension
  +_model.provider=ConfigModel Extension
   
   # org.mycompany.root (optional section)
  -_org.mycompany.root.model-type=Section
  -_org.mycompany.root.model-description=Root section defining my company configuration.
  +_org.mycompany.root.model.target=Section
  +_org.mycompany.root.model.description=Root section defining my company configuration.
   
   # org.mycompany.security (required section)
  -_org.mycompany.security.model-type=Section
  -_org.mycompany.security.model-required=true
  -_org.mycompany.security.model-description=Security related settings.\
  +_org.mycompany.security.model.target=Section
  +_org.mycompany.security.model.required=true
  +_org.mycompany.security.model.description=Security related settings.\
            refer for further details to XXX.
   
   # minmal section
  -_minimal.model-class=Section
  +_minimal.model.target=Section
   
   # custom validated section
  -_validated.model-type=Section
  -_validated.model-validator=org.apache.tamaya.model.TestValidator
  +_validated.model.target=Section
  +_validated.model.validator=org.apache.tamaya.model.TestValidator
   -------------------------------------------------------------------------------
   
   Above +org.mycompany.root+ transitively defines 3 sections:
  
positive.code: configuration:
  
  . the _configuration section:_ In our case this equals to +a.b.c+, which itself also includes the
   tranitive entries +a.b+ and +a+.
  . the _configuration parameter:_ Basically parameters are adressed using their fully qualified names,
   which equals to the containing section name and the relative parameter name, separated by the dor separator.
   In the above example +a.b.c.param1+ and +a.b.c.param2+ are the fully qualified parameter names.
  
negative.code:   descriptions, e.g. in a management console or generated configuration documentation site.
  * a set of sections.
  * a set of parameters.
  * Both, sections (+.model.target=Section+) as well as parameter models (+.model.target=Parameter+)
    ** can be modelled by a meta-data entry, by default +_my.config.key.model+.
    ** may be required, or optional (+.model.required=true|false+)
    ** may have an optional description
  * Parameters additionally have
    ** a _type_ (+.model.type=Classname+), described by the fully qualified class name, into which any configured (String)
       value must be convertable into. If no type is configured +java.lang.String+ is assumed as default.
    ** an optional regular expression that can be used to validate the +String+ values returned from a
       configuration (+.model.expression=regexpression+).
  
  Given these concepts a configuration can be fully described. Entries that are not contained in one of the given
  sections (or its children), or parameters not described or marked as valid (e.g. for dynamic configModels of
  