anchor.diff:  ----
   QUERY
   id: e11a27d3-4b86-4191-a310-12847fa79d48
  -destination: /user/2
  -
  -^@
  -----
  -
  -After sending a `QUERY` frame we should expect an `RESPONSE` frame from the server
  -unless the `id` header is ommited. The `destination` header is mandatory and it is
  -represented as URI path.
  +dest: users
  +
  +{:id 2}^@
  +----
  +
  +
  +After sending a `QUERY` frame we should expect an `RESPONSE` frame to be sent back.
  +The `dest` header is mandatory and its format is explicitly not specified.
   
   
   === NOVELTY
   
  -This is a frame that serves for submit data to be processed to a specified resource. It
  -has versy similar semantics that HTTP POST requests.
  +This is a frame that serves for submit data to be processed to a specified resource.
  +It has versy similar semantics that HTTP POST requests.
   
   This is the aspect of the `NOVELTY` frame:
   
  
positive.code: 
  === QUERY
  
  This is a frame that should be used for request data from specified resource. It has very
  similar semantics to the HTTP GET request.
  
  This is the aspect of the `QUERY` frame:
  
  
negative.code: 
  === Size Limits
  
  To prevent malicious clients from exploiting memory allocation in a server, servers
  MAY place maximum limits on:
  
  * the number of frame headers allowed in a single frame
  * the maximum length of header lines
  