Time: 10:00AM Eastern US (Daylight Savings) (contact MichaelFiedler if you'd like to participate)

The Automation meetings alternate times each meeting to accommodate the global team.

Agenda

* Reoccurring agenda items:

• Recap of previous meeting AutomationMeetings20120322
• Update on action items

* Main agenda items:

• Draft Spec discussion: AutoSpecificationV2
  • Specification Issues
  • Resource samples
  • Spec completeness issues/Readiness for reviews
• Implementation plans
• Next meeting:
  • 5 April, 10AM Eastern US

Minutes

Michael Fiedler, Max Vohlken, Eric Bordeau, David Liu, John Arwe, Vaibhav Srivastava, Jing Qian, Paul McMahan? , Charles Rankin, John Arwe

* Discussed Spec issues

• MUST vs. SHOULD wording on service provider use of the the oslc_auto:state and oslc_auto:verdict values defined in the spec.
  • Agreement that the wording should be "MUST use at least one value defined in the automation vocabulary". Spec updated.
  • Additionally, need to add additional verdict of "Incomplete" to satisfy the cardinality constraint of at least 1 verdict per result.
• DELETE
  • strengthen DELETE from MAY to SHOULD in the table
  • add a statement that a service provider SHOULD support DELETE of any resources for which it supports creation.
• Extended discussion on what the minimum requirements for an automation service provider are
  • proposed scenario of synchronous automation
    • request, execution and result happen in a short period of time - possibly a short-lived, single-threaded operation on the provider
    • no persistence of requests or results
    • no requirement for Query Capability or for update of results
  • Does relaxing MUST on Query Capability and Automation Result PUT make sense? What are the implications for consumers not expecting this behavior
  • no conclusions
  • TODO: MichaelFiedler to discuss with some folks on Core
  • TODO: Continue conversation in workgroup

* Next Meeting: April 19th at 1PM Eastern US