[Oslc-Automation] OSLC Automation meeting this week - minutes

[Martin P Pain]

http://open-services.net/wiki/automation/AutomationMeetings20140626/

To keep meeting short, will only cover the “Availablility” point from the 
agenda:
Availability 
Use of OSLC Actions’ profiles/patterns: best if we have one pattern that 
providers MUST provide to be compliant, to reduce burden on consumers. 
This should probably be the AutomationRequest pattern. The fact that this 
is asynchronous shouldn’t be a problem, as consumers who want to be 
loosely-coupled cannot assume providers’ actions will be synchronous.
How does the consumer know which property will be changed, and to what 
value? Tim’s current plan (for his prototype) is to have a single 
Availability action that takes the target state as a parameter. Question 
was raised about how the consumer knows what the parameter is and what the 
values will be - will they be specified in the spec?
Is it correct to define a new action type like this? Defining a new action 
type is good to identify a particular type or class of actions. However, 
whether this particular definition is correct, and how abstract it should 
be, will be more evident when we see a definition of it in the spec or 
vocab.



Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
OASIS Open Services for Lifecycle Collaboration - Automation technical 
committee chair

E-mail: martinpain at uk.ibm.com
Find me on:  and within IBM on:  




IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140627/0ed943a6/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 518 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140627/0ed943a6/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1208 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140627/0ed943a6/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 360 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140627/0ed943a6/attachment.gif>