anchor.diff:  
   + Response 204
   
  -<!--
  -
  -## Attribute by Entity Type and ID [/v2/entities/type/{entityType}/id/{entityId}/attrs/{attrName}]
  -
  -### Get attribute data [GET /v2/entities/type/{entityType}/id/{entityId}/attrs/{attrName}]
  -
  -Returns a JSON object with the attribute data of the attribute. The object follows the JSON representation for attributes
  -(described in a section above).
  -
  -Response:
  -
  -* Successful operation uses 20O OK.
  -* Errors use a non-200 and (optionally) an error payload. See subsection on Error Responses for more details.
  -
  -+ Parameters
  -    + entityId: Bcn_Welt (required, string) - Entity ID
  -    + entityType: Room (required, string) - Entity Type
  -    + attrName: temperature (required, string) - Attribute to be retrieved.
  -
  -+ Response 200 (application/json)
  -
  -        {
  -            "value": 21.7
  -        }
  -
  -### Update attribute data [PUT /v2/entities/type/{entityType}/id/{entityId}/attrs/{attrName}]
  -
  -The request payload is an object representing the new attributes data. Previous attribute data is replaced
  -by the one in the request. The object follows the JSON representation for attributes
  -(described in a section above).
  -
  -Response:
  -
  -* Successful operation uses 204 No Content
  -* Errors use a non-200 and (optionally) an error payload. See subsection on Error Responses for more details.
  -
  -+ Parameters
  -    + entityId: Bcn_Welt (required, string) - Entity ID
  -    + entityType: Room (required, string) - Entity Type
  -    + attrName: temperature (required, string) - Attribute name
  -
  -+ Request (application/json)
  -
  -        {
  -            "value": 25.0,
  -            "unitCode": "CEL"
  -        }
  -
  -+ Response 200
  -
  -
  -### Remove a single attribute [DELETE /v2/entities/type/{entityType}/id/{entityId}/attrs/{attrName}]
  -
  -Removes the attribute from the entity.
  -
  -Response:
  -
  -* Successful operation uses 204 No Content
  -* Errors use a non-200 and (optionally) an error payload. See subsection on Error Responses for more details.
  -
  -+ Parameters
  -    + entityId: Bcn_Welt (required, string) - Entity ID
  -    + entityType: Room (required, string) - Entity Type
  -    + attrName: temperature (required, string) - Attribute name
  -
  -+ Response 204
  -
  --->
   
   ## Attribute Value by Entity ID [/v2/entities/{entityId}/attrs/{attrName}/value{?options}]
   
   ### Get attribute data [GET /v2/entities/{entityId}/attrs/{attrName}/value{?options}]
  -
  -<table style="width: 100%; margin: 12px 0 0 0;">
  -<tr><td colspan="2"><strong>Required Parameters</strong></td></tr>
  -<tr><td colspan="2">none</td></tr>
  -<tr><td colspan="2"><strong>Optional Parameters</strong></td></tr>
  -<tr>
  -  <td style="padding-right: 40px; width: 140px;">options</td>
  -  <td>Operation opations. Allowed values: <code>text</code>.</td>
  -</tr>
  -</table>
   
   It returns a JSON object with a `value` propierty with the value of the attribute. The `text` option
   indicates that the attribute value must be provided as plain text (text/plain).
  
positive.code: A query is composed by a list of statements separated by the ';' character. Each statement express a matching condition.
  The query will return all the entities which match all the matching conditions (AND logical operator). 
  
  There are two kind of statements: <em>unary statements</em> and <em>binary staments</em>.</p>
  
  <p>Binary statements are composed by an attribute name (e.g. "temperature"), operator and value (which format
  depends on the operator), e.g.:</p>
  
  <p><code>
  temperature==50<br/>
  temperature<=20
  </code></p>
  
  <p>The list of operators (and the format of the values they use) is as follows:</p>
  
  <ul>
    <li>Equal: <code>==</code>. It accepts the following values:
      <ul>
        <li>Single element, e.g. <code>temperature==40</code>. It matches entities whose attribute value
        that exact value.</li>
        <li>A list of comma-separated values, e.g. <code>color==black,red</code>. It matches entities whose
        attribute value is one of the values (OR clause). Eg. entities which <code>color</code> is set to
        <code>black</code> will match, while entities which <code>color</code> is set to <code>white</code>
        will not match.</li>
        <li>A range, specified as a minimum and maximum separated by <code>..</code>. It match if
        the value is in the interval between the minimum and the maximum (both included). It can only be used
        with attributes which contain dates or numbers. E.g. <code>temperature==10..20</code> matchs if the
        temperature is greater or equal than 10 and lower or equal than 20.</li>
      </ul>
    </li>
    <li>Unequal: <code>!=</code>. It accepts the following values:
      <ul>
        <li>The value is a single element, e.g. <code>temperature!=40</code>. It matches entities whose attribute
        value is not that exact value.</li>
        <li>A list of comma-separated values, e.g. <code>color!=black,red</code>. It matches entities whose
        attribute value is not any of the values (AND clause). Eg. entities whose <code>color</code> is set
        to <code>black</code> will not match, while entities whose <code>color</code> is set to
        <code>white</code> match.</li>
        <li>A range, specified as a minimum and maximum separated by <code>..</code>. It match
        if the value is not in the interval between the minimum and the maximum (both included). It can only
        be used with attributes which contain dates or numbers. E.g. <code>temperature!=10..20</code>matchs if
        the temperature is lower than 10 or greater than 20 (it will not match if the tempeature is 10 or the
        temperature is 20).</li>
      </ul>
    </li>
    <li>Greater than: <code>&gt;</code>. The value is a single element, e.g. <code>temperature&gt;40</code>. It
    matches entities which attribute value is strictly greater than that value. It only makes sense when
    used with attributes which contain dates or numbers (using with attributes of other type might lead to
    unexpected results).</li>
    <li>Lesser than: <code>&lt;</code>. The value is a single element, e.g. <code>temperature&lt;40</code>. It
    matches entities which attribute value is strictly lesser than that value. It only makes sense when
    used with attributes which contain dates or numbers (using with attributes of other type might lead to
    unexpected results).</li>
    <li>Greater or equal than: <code>&gt;=</code>. The value is a single element, e.g. <code>temperature&gt;=40</code>.
    It matches entities which attribute value is greater than or equal to that value. It only makes sense when
    used with attributes which contain dates or numbers (using with attributes of other type might lead to
    unexpected results).</li>
    <li>Lesser or equal than: <code>&lt;=</code>. The value is a single element, e.g. <code>temperature&lt;=40</code>. It
    matches entities which attribute value is lesser than or equal to that value. It only makes sense when
    used with attributes which contain dates or numbers (using with attributes of other type might lead to
    unexpected results).</li>
  </ul>
  
  <p>In the case of equal or inequal, if the value to match include a <code>,</code>, you can use simple quote
  (<code>'</code>), e.g: <code>color=='light,green','deep,blue'</code>.</p>
  
  <p>Unary statements are composed of a unary operator (either <code>+</code>or <code>-</code>) and are used in two situations:</p>
  
  + To check for attribute existence. E.g. <code>+temperature</code>matches entities which have
    a temperature attribute (no matter its value), while <code>-temperature</code>matches entities which don't have
    a temperature attribute.
  + To check for entity type existence, with the <code>type</code>keyword. E.g, <code>-type</code>
    matches entities which don't have a type.
    
   
  ## Geographical Queries
  
negative.code: 
  + Response 200
  
  
  ## Entity types [/v2/types{?limit,offset,options}]
  
  ### Retrieve entity types [GET /v2/types/{?limit,offset,options}]
  
  If `values` option is not in use, the operation returns a JSON object which properties are entity types. The properties
  value is a JSON object with information about the type: `attrs` (the union set of attribute names along all the entities
  of such type) and `count` (the number of entities belonging to that type).
  
  If `values` option is used, the operation returns a JSON array with the list of entity type names as strings.
  
  Response code:
  
  