anchor.diff:  ----
   ====  
   
  -In this example separate Resources can be associated with the image and stream properties of the `Dvd` Entity.   
  -
  -When using JPA with a relational database these associations are typically (but not always) also Entity associations as well, as shown here.  However when using NoSQL databases like MongoDB that are capable of storing hierarchical data they are true property associations.
  -
  -As before Spring Data REST will expose an item resource under the URI `/dvds/{id}`.  However, this time Spring Content REST will expose content resources under the URIs `/dvds/{id}/image/{contentId}` and `/dvds/{id}/stream/{contentId}` managed by their respective stores.  A new image (or a new stream) can be created by POSTing to `/dvds/{id}/image` (or `/dvds/{id}/stream`) resource.
  -
  -NOTE: as these properties are both single values Spring Content REST content resources are also available under the simplified `/dvds/{id}/image` and `/dvds/{id}/stream` where the `{contentId}` can be omitted for convenience.
  -
  -=== Property Collection Associations
  -
  -The final type association is the Property Collection Association.  Unsurprisingly, closely related to Property Association, it allows a property of an Entity to be associated with many Resources.  Consider the following example:-
  +In this example separate Resources are associated with the `image` and `stream` properties of the `Dvd` Entity.
  +
  +When using JPA and its relational characteristics these associations are typically (but not always) also Entity
  +associations as well, as shown here.  However when using NoSQL databases like MongoDB that are capable of storing
  +hierarchical data they are true property associations.
  +
  +As before, Spring Data REST will export an item resource under the URI `/dvds/{id}`.  However, this time Spring Content
  +REST will export Property Resources to the URI `/dvds/{id}/image/{contentId}` and `/dvds/{id}/stream/{contentId}`
  +managed by the respective Store.  A property can be set by POSTing to `/dvds/{id}/image` (or `/dvds/{id}/stream`).
  +
  +NOTE: as these properties are both single values these Resources are also available under the simplified URI
  +`/dvds/{id}/image` and `/dvds/{id}/stream` where the `{contentId}` is omitted for convenience.
  +
  +=== Property Collection Resources
  +
  +Property Resources can also target Collections.
  +
  +Consider the following example:-
   
   ====
   [source, java]
  
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: 
  == Fundamentals
  
  The core functionality of Spring Content REST, enabled through `@Import(RestConfiguration.class)`, is to export resources
  for Spring Content stores.  This is often closely related to Spring Data repositories.
  
  The following describes typical store scenarios and how they are exported with Spring Content REST.
  
  === Resources
  
  Spring Resources, managed by a Spring Content Store, are standard Spring Resources that, when exported using Spring
  Content REST, are accessible by REST endpoint.
  
  Consider the following Store interface:
  
  ====
  [source, java]
  ----
    public interface DvdStore extends Store<String> {}
  ----
  ====
  
  In this example, the Store's Resources are exported to the URI `/dvds`.  The path is derived from the
  uncapitalized, pluralized, simple class name of the interface.  When interacting with this endpoint any additional path
  is deemed to be the Resource's location and will be used to fetch the Resource using the Store's `getResource` method.
  For example, a GET request to `/dvds/comedy/monty_pythons_flying_circus.mp4` assumes
  `/comedy/monty_pythons_flying_circus.mp4` is the location of the Resource.
  
  The HTTP methods are then mapped onto the relevant Resource methods; GET maps to `getInputStream`, PUT maps onto
  `getOutputStream` and so on.
  
  === Entity Resources
  
  Entity Resources are associated with Spring Data Entities.
  
  Assume the following `Entity` class with associated `Repository` and `Store` interfaces:
    
  ====
  [source, java]
  