[Oslc-Automation] Oslc-Automation Digest, Vol 44, Issue 11
Tim Friessinger
TFRIESS at de.ibm.com
Thu Oct 30 08:50:11 EDT 2014
+1
Mit freundlichen Grüßen / Kind regards
Tim Friessinger
System Automation for z/OS Development
IBM Software Group, Tivoli
IBM Lab Boeblingen, Germany
Phone: 49-7031-16-2535 IBM Deutschland (Embedded
image moved
to file:
pic42389.gif)
E-Mail: tfriess at de.ibm.com Schoenaicher Str. 220
71032 Boeblingen
Germany
IBM Deutschland
Research &
Development
GmbH /
Vorsitzende des
Aufsichtsrats:
Martina Koederitz
Geschäftsführung:
Dirk Wittkopp
Sitz der
Gesellschaft:
Böblingen /
Registergericht:
Amtsgericht
Stuttgart, HRB
243294
oslc-automation-r
equest at open-servi
ces.net To
Sent by: oslc-automation at open-services.net
"Oslc-Automation" cc
<oslc-automation-
bounces at open-serv Subject
ices.net> Oslc-Automation Digest, Vol 44,
Issue 11
23.10.2014 18:00
Please respond to
oslc-automation at o
pen-services.net
Send Oslc-Automation mailing list submissions to
oslc-automation at open-services.net
To subscribe or unsubscribe via the World Wide Web, visit
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
or, via email, send a message with subject or body 'help' to
oslc-automation-request at open-services.net
You can reach the person managing the list at
oslc-automation-owner at open-services.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Oslc-Automation digest..."
Today's Topics:
1. Re: Minor comments to OSLC Automation 2.1 (Martin P Pain)
2. OSLC Automation WG agenda 23rd October (Martin P Pain)
----------------------------------------------------------------------
Message: 1
Date: Thu, 23 Oct 2014 09:46:05 +0100
From: Martin P Pain <martinpain at uk.ibm.com>
To: oslc-automation at open-services.net
Subject: Re: [Oslc-Automation] Minor comments to OSLC Automation 2.1
Message-ID:
<OF861EFCF5.5ED7EB30-ON80257D7A.002ED179-80257D7A.00302B55 at uk.ibm.com>
Content-Type: text/plain; charset="us-ascii"
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
> (2) Property "oslc:futureAction": In the description it says "..will
become
> available on Auto Results that execute this Plan...". Is this correct?
> Doesn't an Auto Request execute the Auto Plan and the Auto Result only
> represents the state (and final results) of this execution?
I propose changing "Auto Results that execute this Plan" to "Auto Results
that result from execution of this Plan", to make it a bit clearer.
> (3) "Resource: Dialog": I think this part is new in Auto 2.1, and I
don't
> understand why this resource is only for deferred-execution. As far as I
> understood the immediate-execution should be also available via a
dialog,
> so why isn't this described here at this point as well or split up into
> "Resource: Deferred Exec Dialog" and "Resource: Immediate Exec Dialog"?
That is a bit confusing, you're right. Only the last property in the table
is specific to deferred execution dialogs - I believe the rest apply to
all of them.
I propose changing the introduction to that resource shape to from:
"A deferred-execution creation dialog describes a delegated user interface
(UI) which can be used to allow a user to interactively create a new
Automation Request that is not immediately available for execution.
Dialogs in general are defined by OSLC Core 2.0, and re-used here."
to say:
"Dialogs in general are defined by OSLC Core 2.0, and this specification
defines two specific types of dialogs: the _immediate-execution creation
dialog_, which can be used to allow a user to interactively create a new
Automation request which is immediately available for execution, and the
_deferred-execution creation dialog_, which create a new Automation
Request that is not immediately available for execution, but which
requires further work on the part of the consumer. "
Also for the description for the "oslc:usage" property in that shape to be
changed from:
"An identifier URI for the domain specified usage of this dialog, for
example a deferred execution creation dialog. It is likely that the target
resource will be an oslc_auto:DeferredExecution but that is not
necessarily the case"
to say:
"An identifier URI for the domain specified usage of this dialog. For
example, for a deferred execution creation dialog this will be
oslc_auto:DeferredExecution."
And change this line in the table:
"Core 2.0 Actions-defined Properties added to Dialog by Automation"
to say:
"Core 2.0 Actions-defined Properties added to Dialog by Automation - only
used by the _deferred-execution creation dialog_."
And also append this text to the end of the "oslc:binding" property's
description on that shape:
"This property is only used by the _deferred-execution creation dialog_."
> (4) Section "OSLC Actions and Automation / Discovering actions that will
be
> executable after an Auto Requ completes": Text says "...If the Auto
Request
> resulted in a new resource being created". -> Wouldn't be a "If the
> execution of an Auto Plan through/ by and Auto Request resulted in a new
> resource..."?
The terminology's a little loose here. In a sense the Request does get
"executed", which consists of "executing" the [automated process
represented by the] Plan, with the parameters which were specified on the
Request. If we were sticking with the terminology exactly as it is on the
diagram, your suggestion would be right. However, for the sake of fewer
words, I think changing it to be "If the execution of the Auto Request
resulted in a new resource being created" would suffice.
So I propose changing "If the Auto Request resulted in a new resource
being created" to "If the execution of the Auto Request resulted in a new
resource being created".
Please +1 or suggest improvements,
Thanks,
Martin
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/20141023/2d719dcb/attachment-0001.html
>
------------------------------
Message: 2
Date: Thu, 23 Oct 2014 09:59:07 +0100
From: Martin P Pain <martinpain at uk.ibm.com>
To: oslc-automation at open-services.net
Subject: [Oslc-Automation] OSLC Automation WG agenda 23rd October
Message-ID:
<OFC035A498.A70AFB04-ON80257D7A.00313F71-80257D7A.00315CD6 at uk.ibm.com>
Content-Type: text/plain; charset="utf-8"
I intend to open the call today, but hopefuly the discussion will not take
long. If you can't attend, please respond to Tim's & my emails on the
mailing list.
Agenda:
http://open-services.net/wiki/automation/AutomationMeetings20141023/
Review 28 August minutes
Automation 2.1:
Tim?s comments & Martin?s proposals
Steve?s review?
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/20141023/10923f52/attachment-0001.html
>
------------------------------
Subject: Digest Footer
_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
------------------------------
End of Oslc-Automation Digest, Vol 44, Issue 11
***********************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic42389.gif
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20141030/17f790c0/attachment.gif>
More information about the Oslc-Automation
mailing list