Time:
10:00AM Eastern US (contact
MichaelFiedler if you'd like to participate)
The Automation meetings alternate times each meeting to accommodate the global team.
Agenda
* Main agenda items:
- Review minutes from AutomationMeetings20120802
- oslc:usage for identifying automation "sub-types"
- Specification issues to resolve prior to entering convergence
- Revisit
oslc_auto:outputParameter
attribute on the Request and Result
- name of the attribute - proposed new name on the mailing list:
oslc_auto:executionVariable
- behavior of the attribute in the Result
- Suggestions for additional topics in the Guidance section of the specification
- Implementation updates
- Next meeting:
- Thursday, 16 August at 1PM Eastern US
Minutes
Attending: Michael Fiedler, David Liu, Jing Qian, Dan Berg, Paul
McMahan?
- oslc:usage update to AutoSpecificationV2#Automation_Provider_Sub_Domains
- No comments from workgroup - will solicit further review on the mailing list
- oslc_auto:outputParameter discussion
- updates to the specification (AutoSpecificationV2#Resource_AutomationResult) looked good to the members in the meeting - will solicit further review on the mailing list
- agreement that the current name (
oslc_auto:outputParameter
) was as good as any other - no need to change it.
- Discussion of how providers could advertise added parameters beyond what creators of an Automation Request can provide
- Scenario:
- consumer creates an automation request and provides
olsc_auto:inputParameter
attributes based on the automation plan's oslc_auto:parameterDefinitions
- during execution, the automaton service provider adds some additional parameters. How does the consumer discover these?
- The
oslc:Property
resource, on which oslc_auto:parameterDefinition
is based, has an attribute oslc:readOnly
. Providers can advertise that a parameterDefinition will or may be added by setting oslc:readOnly
to true and setting oslc:occurs
to the appropriate value based on whether the parameter is guaranteed to be added to the result (Exactly-one, One-or-Many) or may be added to the result (Zero-or-one, Zero-or-many).
- The guidance section of the specification will be updated to reflect this and comments solicited on the mailing list
- Need for meeting on 16 August.
- This meeting may be cancelled if there are no hot topics.