Re: [oslc-automation] OSLC Automation v3 spec drafting

[Martin P Pain <martinpain@uk.ibm.com>]

Tim 1. I'm happy to change that. Perhaps
saying "If a GUI is in use..." and "If a GUI is not in use..."
- so that the latter case can cover both users not using a GUI (e.g. command-line
interface) or fully automated tasks (with no human users involved). Do
you think that wording's ok?
Uri 1 Does this cover both of your types?

Tim 2. "Almost all" seems
like a good change. I've committed that change into Subversion.

Tim/Uri 3. That diagram was lifted directly
from v2, so the decision was to copy what we had in v2, rather than it
being an explicit decision to use the passive verb name. The arrow on the
diagram relates to the oslc_auto:producedByAutomationRequest triple/link
from an the oslc_auto:AutomationResult to the oslc_auto:AutomationRequest.
So the question is not just what arrow to put on the diagram, but what
relationship to have between the resources. I don't think there's enough
reason to change this from what we had at v2. While having the link in
this direction does cause the need for the optimisation that Sam proposed
recently (see other thread), it does have advantages: as the Result may
be created at a later time than the Request, the creation of that Result
doesn't require anynew triples on the Request. Also it allows multiple
Results for each Request (although doing that would be confusing... and
I guess you could have a multi-valued triple on the Request anyway). And
it allows the Result to be created on a different server (e.g. on the servers
"agents" or "workers" themselves) pointing back to
the original server's Request (when those other servers might not have
write-access to the Request) - although, again, we don't have any "best
practice" guidance on how to do this.

Now these questions are coming up we
need to make sure we're scenario-driven. So we need to list the scenarios
written up for v2, and decide if we continue to support them all (I expect
we do), and also see if we want to write any new scenarios that use the
flexibility allowed by v2, to decide whether we want to protect that flexibility
or not.

If anyone could put some time in looking
at the v2 scenarios, an din particular listing what spec features enable
them, then that would be useful: http://open-services.net/wiki/automation/Automation-Scenarios/

Thanks,
Martin


Uri Shani <SHANI@il.ibm.com> wrote on 04/12/2014
09:23:19:

> From: Uri Shani <SHANI@il.ibm.com>
> To: Tim Friessinger <TFRIESS@de.ibm.com>
> Cc: Martin P Pain/UK/IBM@IBMGB, oslc-automation@lists.oasis-open.org
> Date: 04/12/2014 09:23
> Subject: Re: [oslc-automation] OSLC Automation
v3 spec drafting
> 
> 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: SHANI@il.ibm.com
> Find me on: [image removed]  [image removed]  
> 
> [image removed] 
> 
> IBM Research Lab
> Haifa University, Mount Carmel
> Haifa, HA 31905
> Israel
> 
> 
> 
> 
> 
> 
> From:        Tim Friessinger <TFRIESS@de.ibm.com>
> To:        Martin P Pain <martinpain@uk.ibm.com>
> Cc:        oslc-automation@lists.oasis-open.org
> Date:        03/12/2014 06:57 PM 
> Subject:        Re: [oslc-automation] OSLC Automation
v3 spec drafting 
> Sent by:        <oslc-automation@lists.oasis-open.org>
> 
> 
> 
> 
> 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:           tfriess@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                  
                     
                     
        
>                    
                     
                     
             
> 
> 
> 
> 
>                    
                     
                     
          
>             Martin P Pain    
                     
                     
>             <martinpain@uk.ib  
                     
                    
>             m.com>    
                     
                     
    To 
>             Sent by:      
           oslc-automation@lists.oasis-open.or
>             <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
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