[occi-wg] OCCI JSON data format

[Jamie Marshall]

I like that idea Ralf, it embodies the fact that it is an invocation message with eventual invocation parameter values.SincerelyJamie
> To: florian.feldhaus at gwdg.de
> Date: Tue, 25 Sep 2012 19:48:13 +0200
> From: ralf at nyren.net
> CC: occi-wg at ogf.org
> Subject: Re: [occi-wg] OCCI JSON data format
> 
> On Mon, 24 Sep 2012 16:02:37 +0000, "Feldhaus, Florian"
> <florian.feldhaus at gwdg.de> wrote:
> 
> > * changed name of OCCI Action to OCCI Action Instance. The Action
> instance
> > format is now closer to the text rendering of action instantiations
> 
> With the Core errata changes OCCI Action is only an identifier of the
> invocable operation. It does not represent the operation itself.
> 
> An OCCI Action instance is basically just a Category with a different
> class name. And being a type identifier it cannot contain e.g. attribute
> values.
> 
> I would therefore propose to call this "Action _invocation_ format"
> instead. I have uploaded a commit implementing this change to the json
> branch. The commit only touches this issue and should be easy to back out
> if not desired.
> 
> regards, Ralf
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/occi-wg
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/occi-wg/attachments/20120925/ae278248/attachment.html>