[Oslc-Automation] executionEnvironment input parameter (was: Changes applied, specs almost ready for finalization - Re: Minor comments to OSLC Automation 2.1)

[Martin P Pain]

We need to decide how to word this.

I see two or three options:

1. We don't actually use 
oslc_auto:inputParameter/oslc_auto:ParameterInstance, we just add to the 
spec to say: include an oslc_auto:executionEnvironment property on the 
Request which specifies which execution environment to use (out of the 
ones on the Plan).

2. (Background - In the spec as it stands: on the AutomationPlan, the 
oslc_auto:parameterDefinition property points to an oslc:Property 
resource. This resource has a property called oslc:propertyDefinition 
whose description is "URI of the property whose usage is being 
described".) So we could add to the spec to say:
"If more than one execution environment is specified on the Automation 
Plan, then when the consumer is constructing an Automation Request, the 
consumer is expected to find a parameter definition from the Automation 
Plan with its oslc:propertyDefinition property set to 
http://open-services.net/ns/auto#executionEnvironment, and create an 
InputParameter on the Automation Request for that parameter definition, 
specifying the execution environment to use (choosing out of those 
specified on the Automation Plan). If that parameter definition's 
oslc:occurs property is exactly-one or one-or-more, then the consumer MUST 
specify an execution environment, Otherwise, the consumer MAY specify an 
execution environment."
(I'm not happy with the wording, so if you agree with this option please 
help me with the wording.)

3. Allow consumers to do either. If providers support choosing execution 
environments require them to allow consumers to use either method. If 
providers require consumers to specify their execution environments then 
they must expose a parameter definition on the plan with an oslc:occurs of 
exactly-one or one-or-more.

Option 1 seems more in-keeping with RDF.
Option 2 seems more in-keeping with OSLC Automation as it stands.
Option 3 seems more "open world" (to misuse the term), but I expect it 
will be harder to write up and harder to encourage compatibility between 
implementations.

I suggest we do NOT do option 3.
My suggestion is option 2, but was anyone expecting it to be option 1?

Umberto, Tim & Steve, would you all be able to provide your opinion on 
this please?

Thanks,
Martin


Umberto Caselli <umberto_caselli at it.ibm.com> wrote on 13/11/2014 14:54:21:

> From: Umberto Caselli <umberto_caselli at it.ibm.com>
> To: Martin P Pain/UK/IBM at IBMGB
> Cc: oslc-automation at open-services.net
> Date: 13/11/2014 14:54
> Subject: Re: [Oslc-Automation] Changes applied, specs almost ready 
> for finalization - Re: Minor comments to OSLC Automation 2.1
> 
> Hello, 
> 
> Regarding point 1, I agree the execution environment has to be 
> specified as an InputParameter. 
> 
> Regarding point 2, I agree with the proposed rephrasing (and you 
> already made the change, which is good). 
> 
> Thanks, Umberto
> ----------------------------------------
> Umberto Caselli
> IBM Tivoli Workload Automation  Development
> email:   umberto_caselli at it.ibm.com
> phone:  ++ 39.06.5966.4427
> Via Sciangai 53 - 00144 Roma
> ----------------------------------------
> Nihil est agricultura melius,  nihil uberius
> nihil dulcius, nihil homini libero dignius 
> 
> 
...
> 
> 
> "Oslc-Automation" <oslc-automation-bounces at open-services.net> wrote 
> on 23/10/2014 09:46:05:
> 
> > From: Martin P Pain/UK/IBM at IBMGB 
> > To: oslc-automation at open-services.net 
> > Date: 23/10/2014 09:46 
> > Subject: Re: [Oslc-Automation] Minor comments to OSLC Automation 2.1 
> > Sent by: "Oslc-Automation" <oslc-automation-bounces at open-services.net> 

> > 
> > My responses/proposals are below. Where I have proposed changes (2, 
> > 3 & 4) could any workgroup members +1 them or suggest improvements. 
> > If no objections or improvements have been heard within a week, I'll
> > consider them approved. 
> > 
> > > (1) Property "oslc_auto:usesExecutionEnvironment": Assuming an 
> Auto Plan as
> > > more than one execution environments. If such a plan is executed (-> 
Auto
> > > Request), how will the Service Provider know in which environment 
the Auto
> > > Plan should be executed? I assume
> > > one solution is to specify this as an InputParameter, but maybe 
> it would be
> > > good to mention this in this properties description?
> > 
> > I think Umberto will have to respond to this one 
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/20141113/332a17ad/attachment-0003.html>