[Oslc-Automation] OSLC Automation Minutes

[Martin P Pain]

Minutes from yesterday's meeting are here: 
http://open-services.net/wiki/automation/AutomationMeetings20140123/


Attending: Martin, Jurgen, John

- Actions, getting it finished:
        - Scenarios. Clearly document?
        - Examples and explanation of how to achieve each of those 
scenarios.
        - Specific spec things:
                - Automation teardown, inc execute-later action
                - Update the spec from 'template' discussions
        - Spec clean-up/editorial issues
        - Implementations
        - Core feedback
        - CM profile & use - SS
        - issues
                8. JA suggests "strongly recommended". "Otherwise, to be 
reassured of interop you would need something beyond the spec"
                9. Types will hopefully come out of writing examples.
                10. Is clean-up
                11. Hopefully resolved by 'templates' discussion changes
                12. Auto scenario
                13. Editorial/review - close?
- Interaction pattern slicing
        - "identification" suggests "URI".
        - "recognition" or "definition" rule
        - otherwise leave it as separate patterns for now.
- Template usage
        - Does anyone need local resources that are there to be used as 
templates?
                - No scenarios we're aware of
                - Need to check with Umberto
        - ContentAsRDF?
                - content:Content
                - oslc predicate 
 
<request>
        a http:Request;
        http:body [
                a oslc:ContentFromRepresentation, content:Content;
                rdf:value </resourceForTemplate>;
        ]
.
"We assign meaning X to this combination. The provider MUST be able to 
operate under this interpretation. The consumer MAY choose to use it. (But 
we can only help the consumer when they choose to use that 
interpretation.) IF the consumer uses the interpretation assigned by the 
spec, then the provider MUST provide the behaviour documented by the 
spec."

- Availability next week. Changes to existing scenarios made from 
discussion last week.
- JA to start write-up of template usage, and http body from 
representation, and issue-8, and "identification" -> "recognition". (No 
other core actions work comes to mind).
- MP to work on Auto Actions spec/changes


Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
Open Services for Lifecycle Collaboration - Automation WG joint 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:   23/01/2014 15:39
Subject:        [Oslc-Automation] OSLC Automation Agenda
Sent by:        "Oslc-Automation" 
<oslc-automation-bounces at open-services.net>



This week's agenda: 
http://open-services.net/wiki/automation/AutomationMeetings20140123/



Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
Open Services for Lifecycle Collaboration - Automation WG joint 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/20140124/82cb17a3/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/20140124/82cb17a3/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/20140124/82cb17a3/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/20140124/82cb17a3/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/20140124/82cb17a3/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/20140124/82cb17a3/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/20140124/82cb17a3/attachment-0001.gif>