[Oslc-Automation] This week's meeting

Martin P Pain martinpain at uk.ibm.com
Fri May 16 09:04:12 EDT 2014


http://open-services.net/wiki/automation/AutomationMeetings20140515/#Minutes

# Minutes #

## Attendance

Martin, Tim, Juergen, John (Partial)


## Resolutions passed

- Approved minutes of meeting on 2014-04-17
- For Availability spec, we agreed to do scenario-driven bottom-up design, 
only adding terms that are needed by scenarios.

## Minutes

* Looked at minutes from previous meeting:
   * Still to do:?
      * Would be good to emphasis in the ActionDialog pattern why it is 
different though:
         * Normative sentence saying provider SHOULD wait for action to 
complete
         * Non-normative note saying intended for short-running actions.
         * Non-normative note (or clarification of final sentence) saying 
that instead of returning a URI like a creation or selection dialog does, 
this dialog returns a verdict (or status) of the action's execution.
   * Minutes approved
* Availability
   * Discussed dcterms:contributor vs oslc:action.
      * JH & Tim sounded convinced, but need to read more.
      * (Good point to start reading: 
http://open-services.net/wiki/automation/OSLC-Automation-Primer/#OSLC-Actions
)
      * Would that make it incompatible with 2.0 consumers? MP - no.
   * Joined: John
   * Discussed: oslc_avail:AEC. What value types? 
      * Are there any scenarios that need it? JH/Tim - No.
      * JH/Tim: What's our position on defining terms that aren't used by 
specs.
      * JA: Vocab definition and spec definition can happen separately. We 
can put them in a vocab without putting them in the spec. But it's likely 
to need re-work anyway, why not just wait? The only reason not to wait 
would be if it's difficult to add it later, but it should be very quick to 
add it later, as long as the WG is available to reach consensus.
   * We agreed to do scenario-driven bottom-up design, only adding terms 
that are needed by scenarios.
* Progress vocab terms:
   * Submitting to OASIS: Can non-members contribute via comments list?
   * Can they comment on something not "public"/committe draft etc.
   * Ask 2.0 providers - are they interested?
   * When would Rupert look to implement?
   * Doing it could provide goodwill among community/implementors.



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



From:   Martin P Pain/UK/IBM at IBMGB
To:     oslc-automation at open-services.net, 
Date:   15/05/2014 13:52
Subject:        [Oslc-Automation] This week's meeting
Sent by:        "Oslc-Automation" 
<oslc-automation-bounces at open-services.net>



Agenda: 
http://open-services.net/wiki/automation/AutomationMeetings20140515/

* Issues 
   * [[Automation Specification Version 2.0 Issues]] 
      * None open 
   * Automation Specification 2.1 Feedback 
      * "From "outside" the 2.1 draft looks very good, but gets 
increasingly harder to grasp. I'm a bit concerned that both the automation 
specification and OSLC as a whole is growing at a speed and in a form, 
where the original goal of simplicity and sticking to what is necessary 
for or needed by most applications, is not fulfilled anymore." - [Email 
9th May](
http://open-services.net/pipermail/oslc-automation_open-services.net/2014-May/000745.html
). [Response 14th May](
http://open-services.net/pipermail/oslc-automation_open-services.net/2014-May/000746.html
). 

* Main agenda items: 
    - Review [17 April minutes](
http://open-services.net/wiki/automation/AutomationMeetings20140417/) 
    - Automation 2.1 & Actions 
        + OASIS OSLC Core TC assigned reviewers. No feedback yet. 
    - "Availability" 
        + First draft available. Please read and review. 
        + Feedback has been discussed on [mailing list](
http://open-services.net/pipermail/oslc-automation_open-services.net/2014-May/thread.html
) 
        + Juergen & Tim - any points from the feedback which are worth 
discussing on the call 
        + Issue tracking. The OASIS OSLC Automation TC has a JIRA 
instance, but presumably we would need to move spec development over there 
if we wanted to use it. 
    - Suggestion on mailing list: [progress indication](
http://open-services.net/pipermail/oslc-automation_open-services.net/2014-May/000745.html
) 
    - Workgroup business 
        + Next meeting 22nd May 
    - AOB

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
_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net



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/20140516/54c75631/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/20140516/54c75631/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/20140516/54c75631/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/20140516/54c75631/attachment.gif>
-------------- 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/20140516/54c75631/attachment-0002.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/20140516/54c75631/attachment-0003.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/20140516/54c75631/attachment-0001.gif>


More information about the Oslc-Automation mailing list