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

Agenda

* Reoccurring agenda items:

• Recap of previous meeting AutomationMeetings20120126
• Update on action items
  • LucasPanjer provided more details for the Mylyn build request scenario .
  • Followup on need for automation instructions in automation plan to satisfy scenarios (PaulMcMahan, CharlesRankin, PramodChandoria).
  • Investigate use of instance resource shape to type parameter definitons (MichaelFiedler)
    • See AutoParmDefProposal

• Specification Version Number
• Draft Spec discussion: AutoSpecificationV1
  • Discussion of updates based on comments received so far
    • Compliance table
    • HTTP method table
    • Delegated UI table
    • Open issues discussion
  • General comments on the spec
• Next meetings:
  • 16 February

Minutes

Attending: Michael Fiedler, John Arwe, Paul McMahan? , Lucas Panjer, Pramod Chandoria, Vaibhav Srivastava, Charles Rankin, Max Vohlken

* LucasPanjer talked through the Mylyn "Build Request" scenario

• Need to construct UI in Eclipse via SWT - not likely to use delegated UI
• Feels the new parameter definition proposal meets the scenario requirements

• General agreement that oslc:Property is a good fit
• Some concerns that it adds complexity for service providers and consumers beyond exposing simple name/value pairs
  • Additional concern on Resource Shape of the Automation Plan. TODO: Create sample resource shape and make sure there are no recursion issues
• Concerns around extensibility
  • Service providers can extend as they see fit - use their own namespace for new attributes and expose them in shape documents
• Concerns around parameter dependencies
  • Example: At first level user selects Windows, second level they select XP
  • Service provider logic or delegated UIs needed in V1 to handle these types of dependencies.
• TODO: Update draft specification to adopt this proposal

• Core guidance is to number the spec after the Core spec it is based on. Automation would be V2 under this guidance
• Several workgroup members felt this was confusing and might cause problems if Automation needed a new specification before the next Core spec - i.e. need "dot" releases
• TODO: MichaelFiedler will send an e-mail to the workgroup list to solicit opinions.

Next meeting: 16 February at 10AM Eastern US Time