anchor.diff:  [source]
   ----
   {
  -    "id" : "io.crnk.example.springboot.domain.model.Project",
  +    "id" : "resources.project",
       "type" : "meta/resource",
       "attributes" : {
         "name" : "Project",
  
positive.code:   }
  ----
  
  Of importance is the assignment of IDs to meta elements. For resources the resource type is used to compute the meta
  id and a `resources` prefix is added. In the example above, person gets a `resources.person` meta id.
  Related objects (DTOs, links/meta info) located in the same or a subpackage of a resource gets the same meta id prefix.
  
negative.code: 
  `ResourceMetaProvider.putIdMapping(String packageName, String idPrefix)`
  
  to override the default `resources` prefix and assign a specific prefix for a package.
  
  
  ### Extending the Meta Module
  
  There is a `MetaModuleExtension` extension that allows other Crnk modules contribute `MetaProvider`
  implementation. This allows to:
  
  - add `MetaFilter` implementations to intercept and modify meta elements upon initialization and request.
  - add `MetaPartition` implementations to introduce new, isolated areas in the meta model, like a JPA
    meta model next to the JSON API one (like for documentation purposes).
  
  For more detailed information have a look at the current `ResourceMetaProvider`.
  
  
  anchor:home_module[]
  
  
  ## Home Module
  
  