index / Automation Meetings / This page

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

Agenda

Chair: Martin

• Main agenda items:
  • Specification issues
    • Automation Specification Version 2.0 Issues
      • #5 Recommended attributes for contributions - mailing list thread - Are we changing this in the 2.0 spec?
      • #7 Is the definition of ParameterInstance wrt data types ill-defined? - mailing list thread - Michael
    • Automation Specification Version 2.1 Issues - Any new?
  • Implementation updates
    • Open forum for implementers to provide updates
    • Summarize any new implementation reports
  • Review 31 oct minutes
  • Automation 2.1
    • Automation Scenarios v2.1 status
      • Orchestration Scenarios.
        
        • MP proposes that we include the previously-discussed write-up of how 2.0 resources can be used for orchestration scenarios, despite the gap Charles identified. Also that we explicitly state that gap, and encourage implementers who have concrete orchestration scenarios to contact the WG/TC. Charles has agreed there is value in this, but does not have the time to do the write-up.
    • “Actions” work in Core:
      • http://open-services.net/wiki/core/Actions-2.0-Scenarios/
        • Minor updates from CM
      • http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/.
        • Updates from last week?
        • Identification of profile/compatibility - Martin
          • http://open-services.net/wiki/core/Actions-2.0-with-profile-rules/
          • http://open-services.net/wiki/core/Actions-2.0-with-nil-body-profile/
          • http://open-services.net/wiki/core/Actions-2.0-with-profile-rdftypes/
        • Delegated dialogs - Martin
  • Workgroup business
    • Wiki homepage reformat
    • Next meeting: 14th November at 11AM Eastern US, including initial Availability scenarios presentation (Availability Scenarios)
• Items for later phases/meetings:
  • Actions 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 last meeting not covered by agenda

All covered in agenda

Actions carried over/not yet due:

None

Minutes

Attending: Martin P, Tim, Steve S, John A

Apologies: Mike F, Umberto C, Jurgen

• Issue #5: Change dcterms:type to rdf:type as modification to 2.0 spec? Approved. TODO
• Issue #7: Approval for wording of “The value may be an RDF literal or a resource. If the value type is a RDF literal, then it Should be a RDF typed literal.”
• Approved minutes.
• Orchestration: Leaving with Charles until he has time. TODO
• Actions:
  • TODO remove requirements (on Actions from Automation) from auto page - duplicated in Core Actions scenarios page
  • MP described thoughts on profile identification rules
    • Problem: redundancy with provider restrictions. Better to just say “any actions that fulfills all the MUSTs”?
    • Do consumers need to know?
      • SS - CM consumers are very unlikely to need to know in advance if they support the action, as there are so many things that can go wrong at the time of execution.
      • MP - some things are implied from the profile in use (in particular - the interaction pattern). I would prefer that the condition of that implication be clear, and also not too wide to avoid implying it for future actions not from that profile.
    • TODO Generic consumer cases are not on scenarios page.
    • Always ask “Complexity for what reason?”
  • TODO MP to flesh out separation of interaction pattern from restrictions
  • TODO review dialogs scenarios email - all

Actions resulting from this meeting