anchor.diff:  
   The result of the query would be A and B:
   
  -+ http://forge.fiware.org/plugins/mediawiki/wiki/fiware/images/b/b3/Orion-geo-square.png
  +
  +![Authentication flow](http://forge.fiware.org/plugins/mediawiki/wiki/fiware/images/b/b3/Orion-geo-square.png)
   
   o define a polygon, we use the polygon element which, in sequence, include a vertexList. A vertexList is composed by a list of vertex elements, each one containing a couple of elements (latitude and longitude) that provide the coordinates of the vertex. The result of the query would be A and B.
   
  
positive.code:    
  Orion Context Broker supports hierarchical scopes, so entities can be assigned to a scope at creation time with updateContext (or related convenience operation). Then, queryContext (and related convenience operations)can be also scoped to locate entities in the corresponding scopes.
  
  For example, consider an Orion-based application using the following scopes:
  
  + Madrid, as first level scope
  + Gardens and Districts, as second-level scope (children of Madrid)
  + ParqueNorte, ParqueOeste and ParqueSur (children of Gardens) and Fuencarral and Latina (children of Districts)
  Parterre1 and Parterre2 (children of ParqueNorte)
  
  The scope to use is specified using the Fiware-ServicePath HTTP in update/query request. For example, to create the entity Tree1 of type "Tree" in Parterre1 the following Fiware-ServicePath will be used:   
     
      Fiware-ServicePath:/Madrid/Gardens/ParqueNorte/Parterre1
  
  
negative.code:             }
          }
          ],
              "id": “Car1",
              "isPattern": "false",
              "type": “Car"
          }
          
  The entity Car has been created with the specific attribute speed.
  