[occi-wg] Query uniqueness

[Gary Mazz]

Ralf,

Leaving architectural components as simply "not implemented" may be 
considered 'inoperable' and defeats the purpose of interoperability, at 
least in some circles. :)

A provider may implement a protected feature making their occi mixin 
unique to their infrastructure enforcing vendor lock-in. Its probably 
not desirable to go down that path. We need to address that issue 
sometime soon.

cheers
gary

On 4/11/2011 9:59 AM, Ralf Nyren wrote:
> On Mon, 11 Apr 2011 18:51:04 +0300, Andre Merzky<andre at merzky.net>  wrote:
>
>>> This means that with user-defined Mixins an OCCI service must refuse to
>>> create a Mixin for which the specified location path already is taken.
>> which basically means that you need a registry of valid mixins?
> You need a registry of all Mixins visible to a particular user, yes. Not
> sure if that is what you meant.
>
> A simple registry could be a hash-map with "location" as the key and the
> Mixin object as value. When a user attempts to add a Mixin check the
> hash-map, if location is already there, return a Bad Request.
>
> Which Mixins are valid or not in terms of scheme + term is up to the
> provider to decide (afaik).
>
> /Ralf
>
>
>