anchor.diff:  ====
     
   In this example a single Spring Resource (the DVD's video stream) is associated with a Dvd Entity by annotating additional
  -fields on the Entity using the `@ContentId`, `@ContentLength` and `@MimeType` annotations.   In this example Spring Data
  -REST exports a collection  resource to `/dvds`.  The path is derived from the uncapitalized, pluralized, simple class
  -name of the domain class.  Item resources are also exported to the URI `/dvds/{id}`.  The HTTP methods used to request
  -this endpoint map onto the methods of `CrudRepository`.
  -
  -Similarly, Spring Content REST also exports any associated Spring Resources to the URI `/dvds/{id}`.  In this case the
  -HTTP methods map onto the methods of `ContentStore` as follows:-
  -
  +fields on the Entity using the `@ContentId`, `@ContentLength` and `@MimeType` annotations.   
  +
  +In this example Spring Data REST exports a collection  resource to `/dvds`.  The path is derived from the uncapitalized, pluralized, simple class name of the domain class.  Item resources are also exported to the URI `/dvds {id}`.  The HTTP methods used to request this endpoint map onto the methods of `CrudRepository`.
  +
  +Similarly, Spring Content REST also exports any associated Spring Resources to the URI `/dvds/{id}/[contentProperty}`.  In this case `/dvds/{id}/content` because the Spring Content metadata is correlated using the prefix `content`. 
  +
  +For an `AssociativeStore` the HTTP methods are mapped as follows:-
  +- GET -> getResource -> getInputStream
  +- POST/PUT -> getResource -> getOutputStream, associate 
  +- DELETE -> unassociate
  +
  +For a `ContentStore` the HTTP methods are mapped as follows:-
   - GET -> getContent
   - POST/PUT -> setContent
   - DELETE -> unsetContent
  
positive.code: For example, a GET request to `/dvds/comedy/monty_pythons_flying_circus.mp4` will fetch from the `DvdStore` (`/dvds`),
  the Resource `/comedy/monty_pythons_flying_circus.mp4`.
  
  === Entity Resources
  
  Entity Resources are Spring Resource associated with Spring Data Entities.
  
  Assume the following `Entity` class, `Repository` and `Store` interfaces:
    
  
negative.code: 
  The following describes typical store scenarios and how they are exported with Spring Content REST.
  
  === Store Resources
  
  Spring Content `Store` manages Spring Resources that, when exported using Spring Content REST, are accessible by REST
  endpoint.
  
  Consider the following Store interface:
  