Hi Thijs, Thanks for the pointer to the guidelines.. I think we need to be a little more rigid than generic web technologies. We just need to identify issues and develop practices to resolve them. Once technology and practices are defined they can be made testable for certification by independent services or govt agencies. -gary On 4/11/2011 10:45 AM, Thijs Metsch wrote:
BTW: HTTP spec also says on user-defined mix-in creation:
The service might reject this request if it does not allow user-defined \hl{Mixin}s to be created. Also on name collisions of the defined location path the service provider MAY reject this operation.
-Thijs
-----Original Message----- From: occi-wg-bounces@ogf.org on behalf of Ralf Nyren Sent: Mon 11.04.2011 17:59 To: Andre Merzky Cc: occi-wg@ogf.org Subject: Re: [occi-wg] Query uniqueness
On Mon, 11 Apr 2011 18:51:04 +0300, Andre Merzky <andre@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
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg