< Return to Calendar Previous | Next

* OSLC Domains TC Weekly Meeting (Conference Call)
Name * OSLC Domains TC Weekly Meeting (Conference Call)
Time Thursday, 13 September 2018, 09:30am to 10:00am EDT
(Thursday, 13 September 2018, 01:30pm to 02:00pm UTC)

Metting URl: https://ibm.webex.com/join/jamsden

Chat Room: http://webconf.soaphub.org/conf/room/oslc-domains


Jim Amsden: Previous Minutes: https://www.oasis-open.org/apps/org/workgroup/oslc-domains/event.php?event_id=45871

anonymous morphed into Jad El-khoury (KTH)

Jim Amsden: Scribe: Jim

Jim Amsden: https://github.com/oasis-tcs/oslc-domains/wiki/Actions-Specification-Strategy

Jim Amsden: https://github.com/oasis-tcs/oslc-domains/wiki/Automation-Specification-Notes

List of attendees: GrayBachelor (IBM), Jad El-khoury (KTH), Jim Amsden, Mark Schulte (Boeing), Nick Crossley (IBM), anonymous

GrayBachelor (IBM): Apologies for being late

Jim Amsden: Automation 2.1 was never finalized and the Automation TC was disbanded.

Jim Amsden: Automation 2.0 appears to have many, possible stable implementations. But there have been no requests for additional changes to this spec or new implementations.

Nick Crossley (IBM): For the benefit of Configuration Management 1.0, we should define the one new term oslc_autorogress in the OASIS version of Automation 2.1.

Nick Crossley (IBM): Adding a new term is of course upwards compatible.

Jim Amsden: Recommendation for Automation 2.0: examine the already migrated 2.1 specification for incompatibilities with 2.0. Include Nick's request for the new oslc_autorogress property. And progress the Automation 2.1 specification to OASIS Standard.

Nick Crossley (IBM): I concur.

Jim Amsden: Action: Jim and Nick to do the examination of Automation 2.0 and 2.1 to see what actual changes have been introduced and whether there are any incompatibilities

Jim Amsden: Automation was focused on a pretty limited set of use cases: build and test automation. It is not possible to do other things like create baselines.

Jim Amsden: OData has overlapping capabilitie3s

Jim Amsden: Automation was too big a spec for such limited audience/capabilities (high cost, low value).

Jim Amsden: Needs the ability to act on multiple resources (i.e., create multiple baselines in a single plan).

Jim Amsden: We still need to determine what to do with Actions. It appears Automation 2.1 could be completed without Actions. Change Management and Configuration Management no longer have any dependency on Actions. So we could decide to leave Actions as a Working Draft pending interest in further development.


Weekly meeting to facilitate migration of OSLC 2.x domain specifications from open-services.net to OASIS. This meeting follows the OSLC Core TC meeting.

Submitter Mr. James Amsden
GroupOASIS OSLC Lifecycle Integration for Domains (OSLC Domains) TC
Access This event is visible to OASIS OSLC Lifecycle Integration for Domains (OSLC Domains) TC and shared with
  • OASIS Open (General Membership)
  • General Public

Repeating Event Details
This event is one in a list of repeating events. All of these events are listed below.