[Oslc-Automation] changes discussed in thursday's meeting are live

[John Arwe]

As usual, this turned out to be a bit more complicated than expected, so 
it could use a proof-read.  I'd recommend using the wiki history.

Summary of changes
- There was no :executes in the Automation vocabulary documents, so the 
one now in Core is a net add.
- :futureAction was a simple move, as expected.
- both specs updated, including the 2.1 Future Actions picture ... 
including net removal of text in 2.0 Future Actions section, a sure win 
for Ian
- the worked deployment tear-down and re-use example was updated

I also made these changes
- added a 10/9 "convergence change" to one of the specs, since Martin had 
been in there.
- added (a link) from the 2.1 Samples page to the deployment tear-down and 
re-use example (in the scenarios "section" of the wiki), otherwise there 
was nothing for future actions at all in 2.1 Samples
- added oslc:executes 0:1 any/any property row to the Resource:Action 
section of 2.0

I was getting tripped up at first by confusing oslc:executes and 
oslc_auto:executesAutomationPlan, but I think I backed out those changes 
correctly.


Best Regards, John

Voice US 845-435-9470  BluePages
Cloud and Smarter Infrastructure OSLC Lead
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20141010/0850239b/attachment-0003.html>