Open Services
for Lifecycle Collaboration

(But you can call us “OSLC” )

An open community building practical specifications for integrating software

Working for easier integrations

We want software that easily integrates with other software, which will help you build your ideal development and operations environment, connect disjointed workflows, minimize frustration, and save time and money.

Our integrations are easy, like a puzzle with only two pieces
We design bulletproof integrations

Designing robust, flexible connections

Development and operations tools should be able to work freely with similar products. With our standardized methods to represent, access, and link to resources, you won’t have to suffer with any more fragile, fussy integrations.

Exposing more data

Software should be able to share and use linked data. With OSLC specifications, your tools can freely understand each others’ data and artifacts. That means you can better analyze, track, and explore that data to make better decisions.

See compatible software

OSLC lets you explore more data
We gather a variety of subject matter experts

Gathering industry experts

We bring together experts from a variety of industries to explore common issues in software development and operations such as change management, performance monitoring, or embedded systems.

See all our workgroups
See contributing companies and organizations

Writing minimalistic specifications

Life is complicated enough: we write just enough specification to address the most common scenarios. We do not address uncommon use cases, nor do we create specifications for their own sake. But you're free to extend our specifications as needed.

See a list of our specifications
Learn about the Core specification

We focus on only the most important scenarios
Our specs use many of the same core technologies of the World Wide Web

Inspired by the web

Why reinvent the wheel? We base our specifications on ubiquitous and established Internet and linked-data standards. We design RESTful services, and any resource must be accessible to multiple tools via a URL.

Learn about how OSLC uses linked data

Implemented & tested

Our specifications are not complete until we have a working implementation and a test suite. This makes sure our specifications are useful, achievable, and supportable.

See how to integrate products with OSLC
Walk through a working integration

We do not approve a specification unless it has been implemented
All of our specifications are free to use

Free (really)

We want OSLC to spread, so our specifications are freely available for anyone to adopt; we’ve even created software development kits to help you implement, extend, and test OSLC integrations.

See Eclipse Lyo and OSLC4Net


Although we work fast and deliver specifications in a relatively short time, later versions of a specification can address more scenarios and issues. Are we missing something? Join us to provide your input and ideas!

Join a workgroup
Help us grow

OSLC continues to evolve