Papers › Extending the OSLC standard for ECA-based automation in DevOps environments

Extending the OSLC standard for ECA-based automation in DevOps environments

15 Nov 2022arXiv:2211.08075links table onlyarchive 2025-07-28

Guillermo García-Grao, Álvaro Carrera

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

The DevOps paradigm is taking over software development systems, helping businesses increase efficiency, accelerate production, and adapt quickly to market changes. However, adopting these principles can be challenging. Practitioners often face an important issue known as vendor lock-in caused by the cost of tool replacement. In addition, automating the processes that involve these tools also requires investment. These issues could be addressed by standardizing service interfaces to facilitate their integration. Linked Data is an attractive choice for implementing such a standard without sacrificing versatility. An exciting and promising proposal in this direction is the OSLC standard specification. Its purpose is to build an environment where services can interoperate using standard Linked Data models. However, the current specification version still lacks standard definitions for concepts that are critical to automating the execution of actions in fast-changing environments. Therefore, this paper proposes a new specification to extend OSLC, based on the ECA model, for event-based interoperable automation, especially for DevOps environments, which are our motivational scenario. A simple DevOps architecture is built as a prototype to validate the proposed model. Using that architecture, the proposed model is validated in a real-world workflow to prove its contribution to the OSLC standard and the DevOps field.

PaperPDFCode

Code

gsi-upm/oslc-eca_environment officialmentioned in paper report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections