anchor.diff:      [Media][]
   
   
  -## Media collection [/media{?offset,count,filter,sort}]
  +## Media collection [/media{?offset,count,filter,sort,annotations}]
   Given the role of Media as mainly internal raw material means that it often makes more sense to use
   the Work Media collection instead of this one (see below).
   
  
positive.code:     + count (number, optional) ... Return this many records. Default and max values are system-dependent.
      + filter (string, optional) ... Filter responses (see above). Default: no filter.
      + sort (string, optional) ... Sort response (see above). Default: "natural" sort.
  
  + Response 200 (application/json)
      + Headers
  
negative.code: When adding another Work's Media to this Work, add the Work Media endpoint for that other
  work to the `media` list.  It will be rewritten to the Media endpoint for the target Work.
  
  To make the annotations easier to use in web pages the parameter `annotations` can be set
  to a list of property names, e.g. `title,locator`.  This will change the response from a plain list to a map, only
  including the listed properties.  (`all` means that all properties are included in the map.)
  The keys in this map are the `propertyName`, and the value a list of the Annotations for
  that property.  This allows easy access like `annotations.title[0].property.value` to show
  e.g. a title without having to dig through the list.
  
  + Parameters
      + id (string) ... Work record ID
      + include (string, optional) ... Which sublists to include in the response objects. 
          If omitted or empty, all lists are returned in full.  If `none`, all are omitted.
          Otherwise acomma-separated names: `collaborators`, `annotations`, `sources`, `media`.
      + annotations (string, optional) ... Select properties to get or update.
  
  + Model
      + Headers
  