anchor.diff:  ----
   ====
   
  -In this example many Resources can be associated with the chapters property of the `Dvd` Entity.
  -
  -As with Property Association the content resources are exposed under the URI `/dvds/{id}/chapters/{contentId}`.  In this case POSTing to `/dvds/{id}/chapters` a new content resource to be *appended* to the 'Chapters' collection.  This resource supports both POST and PUT HTTP methods.
  +In this example many Resources can be associated with the `chapters` property of the `Dvd` Entity.
  +
  +As with Property Resources, Property Collection Resources are also exported to the URI `/dvds/{id}/chapters`.
  +However, in this case, POSTing to `/dvds/{id}/chapters` always *appends* a new Resource to the 'Chapters' Collection.
  +This Resource supports both POST and PUT HTTP methods.
   
   === Search
   
  
positive.code: 
  All content types except `application/json`
  
  == The Content Collection Resource
  
  Spring Content REST exposes a content collection resource named after the uncapitalized, pluralized version of the domain class the exported store is handling.  The resource path can be customized using the `@StoreRestResource` on the store interface.
   
  === Supported HTTP Methods
  
  
negative.code: 
  === Resource Discoverability
  
  A core principle of HATEOAS is that Resources should be discoverable through the publication of links that point to the
  available resources.  There are a few competing de-facto standards specifying how to represent links in JSON.  By default,
  Spring Data REST uses HAL to render responses.  HAL defines links to be contained in a property of the returned document.
  
  Resource discovery starts at the top level of the application.  By issuing a request to the root URL under which the
  Spring Data REST application is deployed, the client can extract a set of links from the returned JSON object that
  represent the next level of resources that are available to the client.
  
  When enabled through `@Import(HypermediaConfiguration.class)` Spring Content REST will inject Store, Entity and Property
  Resources links for both into the HAL responses created by Spring Data REST.
  
  == The Store Resource
  
  Spring Content REST exports Store Resources to `/{store}/**`.  The resource path can be customized using the
  `@StoreRestResource` annotation on the Store interface.
  
  === Supported HTTP Methods
  
  Store Resources support `GET`, `PUT`, `POST`, and `DELETE`.  All other HTTP methods will cause a `405 Method Not
  Allowed`.
  
  ==== GET
  
  Returns the Resource's content
  
  ===== Supported media types
  
  All content types except `application/json`
  
  ==== PUT/POST
  
  Sets the Resources's content
  
  ===== Supported media types
  
  All content types except `application/json`
  
  ==== DELETE
  
  Removes the Resource's content
  
  ===== Supported media types
  
  All content types except `application/json`
  
  == The Entity Resource
  
  Spring Content REST exports Entity Resources to `/{store}/{id}`.  The resource path can be customized using the
  `@StoreRestResource` annotation on the Store interface.
   
  === Supported HTTP Methods
  
  Entity Resources support `GET`, `PUT`, `POST`, and `DELETE`.  All other HTTP methods will cause a `405 Method Not
  Allowed`.
  
  ==== GET
  
  