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

Agenda

* Main agenda items:

• Review minutes from AutomationMeetings201207119
  • oslc:usage for identifying automation "sub-types"
    • Suggestion: Add: Advertising what category of automation a provider/creation factory/query capability/dialog falls into. Recommend at least one, and fewer are better (just enough, and no more). Use the automation namespace uri as the "generic automation provider" URI, and say that is equivalent to omitting the value when the Service's oslc:domain predicate's value is Automation.
    • TODO: MichaelFiedler to update spec to reflect agreed-upon language
• Specification issues to resolve prior to entering convergence
  • Revisit oslc_auto:outputParameter attribute on the Request and Result
    • name of the attribute
    • behavior of the attribute in the Result
      • is oslc_auto:outputParameter a copy of ALL input parameters, changed input parameters or new parameters created during execution? We've discussed all in the past and the current spec language indicates new/changed and not unchanged oslc_auto:inputParamaters
    • See mailing list thread starting here: http://open-services.net/pipermail/oslc-automation_open-services.net/2012-July/000241.html
  • should oslc_auto:state be read-write or read/only to allow automation agents to update it.
    • Agents could be considered part of the provider implementation and allowed to update.
    • See mailing list thread starting here: http://open-services.net/pipermail/oslc-automation_open-services.net/2012-July/000248.html
• Suggestions for additional topics in the Guidance section of the specification
• Specification review comments or other issues
• Next meeting: should we have it, cancel, ...
  • Thursday, 9 August at 10AM Eastern US

Minutes

Attending: