anchor.diff:                  "hydra:expects":
                   {
                       "@type": "hydra:Class",
  -                    "hydra:subClassOf": "Review",
  +                    "rdfs:subClassOf": "Review",
                       "hydra:supportedProperty": [
                       {
                           "@type": ["hydra:SupportedProperty", "PropertyValueSpecification"],
  
positive.code: <dependency>
    <groupId>de.escalon.hypermedia</groupId>
    <artifactId>hydra-spring</artifactId>
    <version>0.2.0-alpha3</version>
  </dependency>
  ----
  
  
negative.code: * renders a templated link as `hydra:IriTemplate`. Method parameters can be annotated with `@Expose` to assign them a property URI, otherwise the variable name will be shown as a term in the current vocab. If you create a link with AffordanceBuilder's linkTo-method facilities and you pass `null` for arguments annotated with `@PathVariable` or `@RequestParam`, it will automatically become a templated link with variables for the `null` arguments.
  * renders a link to method handlers for any *combination* of GET, POST, PUT, PATCH and DELETE as `hydra:operation`. In order to express that multiple HTTP methods can be invoked on the same resource, use the `and()` method of AffordanceBuilder. See below for an example.
  * renders a single, manually created, non-templated Link or Affordance in json-ld style.
  * renders a POJO method parameter annotated with `@RequestBody` as expected rdfs:subClassOf. Use `@Expose` on the POJO class for a custom identifier. The setter methods on the bean appear as `hydra:supportedProperty`, and you can annotate them with `@Expose` to give them a semantic identifier. Again see below for an example.
  * uses certain schema.org facilities to describe expected request bodies. For this we need schema.org either as `@vocab` or as a `schema:` term. If you do not use schema.org as `@vocab`, make sure you have a `@Term(define = "schema", as = "http://schema.org/")` in the context.
  ** expresses default value and value constraints by means of http://schema.org/PropertyValueSpecification. To specify such constraints, use the @Input annotation. Available constraints are min, max, step, minLength,  maxLength and pattern.
  ** expresses supported properties whose value is an object by nesting them via http://schema.org/rangeIncludes.
  