[Oslc-Automation] Bi-direction Actions/Auto spec dependencies, & action metadata at resource type (shape) level

[John Arwe]

I don't object to any of the potential changes discussed here in Martin's 
email.

(1) I do want to be clear on motivating scenarios though.

It's fair to say Anamitra does [would] need it *if his scenario requires 
the ability to select and configure an action "to be executed once it [the 
action]has been instantiated [actually becomes available]").  All I'm 
saying is that Anamitra should be the one to say if he needs that now, or 
forsees that need as a likely consequence even though he's not going to 
tackle it now.  Maximo does not use Automation today, so it's not 
completely obvious to me that they'd ever have this need.

(2) I do want to be clear on the resulting schedule.  Remember I'm out for 
3 weeks, starting later this week.
Any change carries non-zero risk.  I would say to some degree that when 
Anamitra's feedback on future actions arrived, we (certainly, I did this) 
intentionally *avoided* moving future actions down into Core, in part to 
mange the risk of the larger change.  Would, for example, moving a 
function entirely between specs require us to restart the review process 
with Core?  Not obvious to me.
If we believe that "Actions 3.0" is going to be needed "soon enough", we 
might choose to do move the 'function' in 3.0 not 2.0.  Core's guidance 
has been to lock down in-flight specs and move to OASIS.  If the spec 
change doesn't affect implementations (which it should not, I believe is 
the commonly held assumption), what's leading us to "jam" it in now versus 
enter OASIS with a change that we'd really like to see on its work queue? 
Is it needed now, or is doing it now polishing the nose cone?


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/20140915/6e34033a/attachment-0003.html>