[occi-wg] Its all about Location, location, location

[alexander.papaspyrou at tu-dortmund.de]

Hi Gary,

even for multi-tenant systems, this shouldn't be a problem: GETting the location path should only give back those resources that are supposed to be visible to the customer. Even more: from the specs perspective, noone prevents an implementor from giving back different locations, depending on the principal of the GET request (at least that's how I would interpret it).

-Alexander 

Am 07.04.2011 um 06:32 schrieb Gary Mazz:

> Hi,
> 
> The location is defined :
> 
> Location paths tell the client where all resource instance of one Kind 
> or Mixin (in case the Mixin is used as a tag) can be found regardless of 
> the hierarchy the service provider defines.
> 
> This language poses a problem in multi-tenant and where Kind/Mixins are 
> placed in hierarchically managed name spaces. Stating the location is 
> reference at the user's (consumer's) top level name space may be a 
> clearer way of defining its role.
> 
> cheers,
> gary
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/occi-wg