index / Automation Meetings / This page

Time: 11:00AM Eastern US (Currently 4pm UTC)

Agenda

Chair: Martin

• Main agenda items:
  • Review 19 Dec minutes
  • Specification issues
    • Automation Specification Version 2.0 Issues - Any new?
    • Automation Specification Version 2.1 Issues - Any new?
  • Automation 2.1
    • “Templates” - submitting templates as blank nodes? (Email thread)
    • “Action resources” update
  • “Availability” update
    • http://open-services.net/wiki/automation/Availability-Scenarios/
    • New Scenario: Obtain redundancy of workloads
  • AOB
    • Implementation updates
      • Open forum for implementers to provide updates
      • Summarize any new implementation reports
  • Workgroup business
    • This meeting now clashes with the OSLC Core TC bi-weekly meetings. Should we vote for a new time for our meetings?
• Items for later phases/meetings:
  • Action resources 2.0 - Best practice for inline/referenced resources (or a combination)?
  • Vocab document 2.1 update - New oslc:usage URI for template creation dialogs

Actions from previous meetings

Minutes

Attending: Martin, Tim, Umberto, (John A joined later)

• Minutes accepted
• Automation, Actions
  • Templates: blank nodes/parsing of templates
    • Tivoli implementation uses text manipulation, not full RDF parse/serialize. Then reuses received content-type.
    • TODO: Update spec to reflect that standard operation is to treat the template as text (or bytes). If the consumer changes anything they have to know what they are doing. (Also add a comment that we expect the template to be POSTed to a creation factory - this currently isn’t mentioned) - Umberto
  • Template dialogs: link from dialog to factory.
    • Umberto agrees good to have it, as an optional attribute. Actins spec can up that to a MUST in that context.
    • oslc:creationFactory vs oslc:binding
      • (John A joined)
      • Knowing it is a creation factory lets the consumer know what type of resource is being created.
      • Idea for now:
        • Auto spec defined CreationFactory as an Actions interaction pattern
        • template dialog links to creation factory or any other interaction pattern via oslc:binding
        • if in service catalogue context (not using an Actions profile - other uses of the dialog), dialog SHOULD have a CreationFactory binding.
        • motion passed
  • Template dialogs: identify using an rdf:type value oslc_auto:TemplateDialog rather than an oslc:usage value. (ActionDialogs too).
• Leave meetings at current time.