I have these comments to Tim's comments:
1+2. I think a user can be involved
in an automatic process in two ways: 1) Manual involvement in which the
process is not fully automated and some user actions are required in the
process, where the user may change the course of actions in the process,
and 2) Monitoring the process in which the user can inquire through active
and passive actions into the state of the process. This second involvement
of the user may lead to doing also the first type of involvement.
3. I think this is a matter of semantics
and conventions whether to point the arrow from cause to effect, using
active verb name, or in reverse, using passive verb name as Martin chose
to do. I personally like the active language.
Regards,
Uri Shani, PhD
Research Staff Member
SPRINT(lead), DANSE (lead) Projects
Phone:
972-4-829-6282 | Phone:
972-4-8296282 | Mobile:
972-54-697-6282
E-mail:
Find me on:
IBM Research Lab
Haifa University, Mount Carmel
Haifa, HA 31905
Israel
From:
Tim Friessinger <>
To:
Martin P Pain <>
Cc:
Date:
03/12/2014 06:57 PM
Subject:
Re: [oslc-automation]
OSLC Automation v3 spec drafting
Sent by:
<>
Hello,
I like the introduction section, because it explains the basic idea behind
OSLC Automation and hopefully makes it easier, to understand the details
later on.
I have three comments:
(1) Introduction: "If the user is present, the primary way to achieve
this
is using an [...] Dialog. If the user is not present, ..."
I'm not sure if "user is present" is the right way to express,
what you
mean. The context of "is present" is not clear at this point:
A reader
could ask himself: "Present in front of the computer?" "Present
before the
client application?" etc.
I think its more clear if you talk about if a user is involved that likes
to use a GUI. In this case an OSLC Auto Service Provider can present a
dialog to the user, to support him with his task.
And if in return no (human) user, but another piece of software consumes
the OSLC Auto Service Provider, it can use the query capcability/ creation
factory.
(2) Introduction: "All uses of OSLC Automation will involve
an Automation
Request / Result"
That might be nitpicking, but I think that's not true. A valid scenario
in
my eyes is also to just see/ read, what Auto Plans are available on a
service provider (a scenario like "I want to see the (auto) 'configuration'
on this system...").
So I think an "almost all uses..." is better at this point.
(3) Basic concepts: In the diagram the arrow "ProducedBy" points
from the
Auto Result to the Auto Request. I think it should point into the other
direction, because the Auto Result is produced by the execution of an Auto
Request, and not vice versa.
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:
pic39146.gif)
E-Mail:
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
Martin P Pain
<
m.com>
To
Sent by:
<oslc-automation@
g
lists.oasis-open.
cc
org>
Subject
[oslc-automation]
OSLC Automation
12/02/2014 11:08
v3 spec drafting
AM
I have started drafting the OSLC Automation v3 spec.
The main changes I want to put in are concerned with making it easier to
read (for client implementors, server implementors, and for those wanting
to apply OSLC Automation to other domains).
The work I've done so far is here:
https://tools.oasis-open.org/version-control/browse/wsvn/oslc-automation/specs/oslc-automation-basics-v3.html
Please have a look, particularly at:
1. The introduction section (this is what I want people to understand about
OSLC Automation as soon as they come to the spec).
2. How I'm breaking the "capabilities" section up. (I don't expect
the Auto
Plan Selection Dialog section to contain much more that it does right now,
but other sections that are more Automation-specific will do).
3. The fact that the resource shapes are all at the end, not with the
individual sections in "capabilities".
Even if you don't have time to help draft it, it would be very helpful
to
have your feedback on whether it is communicating to you what you would
need to know.
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[attachment "pic39146.gif" deleted by Uri Shani/Haifa/IBM]
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
