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

Agenda

* Main agenda items:

• Specification issues
  • Updates to spec based on Option 4 of AutoSynchAttributeOptions
  • Mailing list issue: should oslc_auto:state be required in Automation Results? what is value of explict oslc_auto:verdict of oslc_auto:incomplete
    • See: http://open-services.net/pipermail/oslc-automation_open-services.net/2012-June/000200.html
• Specification status and Implementation plans
  • update vocabulary to match spec
• Next meeting:
  • Thursday, 28 June at 10AM Eastern US

Minutes

Attending: Michael Fiedler, Paul Mcmahan, Jing Qian, Pramod Chandoria, Lucas Panjer, John Arwe, Steve Speicher

* Final discussion on synch scenario. Agreement that, subject to final reviews, language currently in the specification would go forward. * Remainder of the discussion was around state and verdict. Several issues were raised which highlighted the need for additional discussion and clarification.

• Likely need 2 verdict changes
  • add Error verdict (distinguish crashed execution from a failed build or test case)
  • change incomplete to notAvailable or unavailable
• Need additional guidance on how to interpret state in Automation Request vs in Automation Result and allow for service provider differences
  • what does state mean when I only have a Request? when I only have a Result? when I have both?
• TODO MichaelFiedler to take a pass at some wording and workgroup will review