HistoryViewLinks to this page 2014 March 31 | 11:10 am

This document provides high-level scenario descriptions and links to elaborated scenarios that have been identified by the working group as possible scenarios to be used in driving V3 Automation scenarios

Some scenarios are carry-overs from the Automation V2 scenarios and Automation Scenarios v2.1 for consideration for V3


Core Scenarios


Determined Out of Scope for 2.1

Automation Agent or Worker Scenarios

Automation Worker scenarios deal with the interactions between an OSLC Automation provider and other entities which perform the actual execution of the automation. Examples are build engines, test automation agents or the worker nodes in a queueing or job scheduling system. Possible goals of specifying these interactions in OSLC would be:

  • provider/worker interactions based on open specification or standard instead of private API
  • provider/worker interchangeability (perhaps, but not necessarily, across automation sub-domains)
  • common patterns for initiating and tracking automation and creating/retrieving results.

Automation Orchestration\Lifecycle Workflow Scenarios

This set of scenarios concerns creation, configuration and execution of multiple automation workflows. An application might be automations which provide ene-to-end coverage of an application lifecycle; orchestrating the execution of builds, multiple types of test and deployment to various test and production environments. Concepts from the Configuration Data scenarios above, the OSLC Configuration Management workgroup and the W3C Linked Data Platform workgroup are likely relevant. Possible goals of specifying these interactions in OSLC would be:

  • Automation provider-to-provider interactions
  • Enable cross-provider workflow composition
  • Apply appropriate automations to environments based on configuration/topology

Related: Scenario of usage by orchestration - an attempt to pull together a scenario of different areas of the spec (v2 and proposed v3) that cmight be used by an orchestrator (whether OSLC-based or any other technology, as long as it can consume OSLC).

OSLC Core V3 Alignment

  • Owner: Michael Fiedler

Automation V3 will need to be aligned with the OSLC Core v3 Specifications. The details of the exact impact are not yet known. W3C LDP workgroup representations of resources and containers, V2 compatibility, linking guidance and authentication guidance are among the topics of interest.


This scenario centers around the ability to receive event-based triggers based on changes to (probably a subset of) OSLC Automation resources, primarily Automation Requests and Automation Results. This is in contrast to the current model of querying (polling) for changes.