This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
Time: 1:00PM Eastern US (contact MichaelFiedler if you'd like to participate)

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


* 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
  • 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


Attending: Michael Fiedler, Paul McMahan? , Charles Rankin, Jing Qiang, Steve Speicher

  • Reviewed previous minutes
    • New wording for sub-types based on oslc:usage accepted without further comment. MichaelFiedler will update the spec.
  • Specification issues
    • First discussion was around oslc_auto:state being specified as read-only.
      • Mailing list discussion centered around read-only being correct for most client implementations - most workers not part of provider implementation and should not have control over state
      • Don't want to force read/write if it is not the common case
      • Implementations can deviate from read-only if it makes sense. Could make it unspecified, but that seems weaker.
      • Workgroup agreed to this description in principle.
    • Followup to mailing list discussion around oslc_auto:outputParameter in the Automation Result
      • name of the attribute: will raise this as an issue on the mailing list and solicit alternate suggestions
      • behavior of oslc_auto:outputParameter
        • Agreement to widen the scope of outputParameter to include the final list of all parameters used during execution, whether unmodified, modified or created during execution
          • Satisfies auditability needs
          • Provides all parameters used during execution
          • No guarantee of how "live" the values are. Depending on the service provider, values may change during execution or not. Once result reaches a completed state, the values must not change.
      • MichaelFiedler will update spec to reflect this discussion.
    • Implementations
      • PaulMcMahan gave some details on Rational Quality Manager plans
      • High level overview of other plans which are known.
Topic revision: r3 - 07 Aug 2012 - 17:51:46 - MichaelFiedler
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback