[Oslc-Automation] Reusing Cm's Actions for teardown/operations

[Charles Rankin]

> From: Martin P Pain <martinpain at uk.ibm.com>

Sorry for taking so long to respond.
 
> > <Charles suggests doing a naked POST to an AutomationRequest
> > to "invoke" it>
> 
> Also, I don't know if this was your intention, but I'm not sure we 
> would want to make a naked POST on an AutoRequest execute it. 

So, I wasn't thinking clearly (on multiple levels).  What I was trying to 
convey was that all of the information for the AutomationRequest could be 
encoded in the URL itself, such that naked POSTing to it would create the 
AutomationRequest correctly.  But, as I said, I wasn't thinking clearly, 
and this is wrong in several (major) ways.

Now, if, as part of the Automation Template discussion that was going 
around, we had a way to have the provider provide us the data for the 
AutomationRequest, then this same information could be provided in the 
Action Resource I described.  Then, the consumer would just turn around 
and provide this content (essentially the AutomationRequest 
document/resource) on the POST to the URL provided.  But, I may still not 
be thinking clearly, so this may have large holes in it as well.

Charles Rankin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20130911/96f2708c/attachment-0003.html>