anchor.diff:     
   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:
  +For example, consider an Orion-based application using the following scopes (shown in the figure):
   
   + 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:   
  +![Authentication flow](http://forge.fiware.org/plugins/mediawiki/wiki/fiware/images/c/ce/ServicePathExample.png)
  +
  +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
   
  
positive.code:             }
          }
          ],
              "id": Car1",
              "isPattern": "false",
              "type": Car"
          }
          
  The entity Car has been created with the specific attribute speed.
  
negative.code: 
  The result of the query would be Madrid, Leganes and Alcobendas.As shown in the picture:
  
  ![Authentication flow](http://forge.fiware.org/plugins/mediawiki/wiki/fiware/images/9/97/Orion-geo-circle-14-in.png)
  
  <center>
  
  