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

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

Agenda

* Reoccurring agenda items:

• Recap of previous meeting AutomationMeetings20120112

* New pages started to compliment the specification

• AutomationVocabulary
• AutoSpecificationV1Samples

* Main agenda items:

• Draft Spec discussion: AutoSpecificationV1
  • Continue discussion
  • More formal definition of parameters. See this e-mail to the mailing list.
  • Result Contribution attribute representation - does this need to be made more formal as well?
  • Review other resource attributes
  • Do the proposed V1 artifacts satisfy the V1 scenarios?
• Additional workgroup members interested in participating in spec authoring?
  • PramodChandoria - Vocabulary and Examples
• Next meetings:
  • 26 January

Minutes

Attending: Michael Fiedler, David Brauneis, Charles Rankin, Nathan Bak, Pete Steinfeld, Max Vohlken, Pramod Chandoria, Rich Rakich, Louis Paul, Srimanth Gunturi, John Arwe

* Primary topic was discussion around the "parameter definition" and "parameter instance" proposal which started on the mailing list during the week

• clarification of the scenarios driving the proposal
  • for simple execution where Automation Requests are being created with a delegated UI, formally defined parameter definitions and instances not required
  • for composition scenarios: having default values and knowledge of which parameters are required is needed.
• Is "required" an essential attribute of parameters? Agreement that it is.
• Agreement to not force the parameter type to string. Give guidance, but allow consumers/service providers flexibility
• Discussion on parameter ordering. Acknowledgement that consumers/service providers have flexibility to use additional predicates (e.g. foo:index) to achieve this
  • Confirmed a particular parameter name can appear multiple times in an Automation Request (or other artifacts)

* Discussion on Automation spec's requirements for RDF/XML, "plain" XML and JSON

• Agreement to make RDF/XML a MUST requirement. Plain XML and JSON will be MAY requirements

* Will request on mailing list for everyone to review the spec and be ready with comments next Thursday

• OslcCoreSpecification, CmSpecificationV2 and the OSLC primer given as examples for those wanting some more background

Next meeting: 26 January at 1PM Eastern US time