Open Services for Lifecycle Collaboration

From Wikipedia, the free encyclopedia
OSLC diagram.png

Open Services for Lifecycle Collaboration (OSLC) is an open community, originally proposed in 2008,[1] to define a set of specifications that enable integration of software development. It has evolved, and continues to evolve, to areas such as Application Lifecycle Management (ALM), Product Lifecycle Management (PLM), IT Operations and more. The intention is to make life easier for tools users and tools vendors, by making it easier for tools to work together.[2]


The OSLC initiative is divided up into various OASIS TC (Organization for the Advancement of Structured Information Standards Technical Committees), as well as previously defined working groups and user groups. Each OASIS TC develops specifications in context of a specific part of the lifecycle.[3] For example, there are OASIS TCs for Change and Configuration Management, Automation and Project Management for Contracted Delivery (Supply Chain). There is also a Core TC, which defines a common specification that is extended by each lifecycle TC.

As of June 2013, the OSLC initiative is a Member Section of the Open Standard Organization OASIS.[4]

Open specifications[edit]

OSLC is open in the sense that anybody can participate (e.g. in User Groups). To participate in the specification developing OASIS TCs, the participants have to sign the IPR policies to ensure irrevocability. The specifications are under Creative Commons licensing and can be freely implemented by anybody.[5] Supporting the OSLC initiative there are open source projects for building an OSLC reference implementation and test suites for various programming languages and framework. The Eclipse Lyo project is one of the open source project which provides consumer and provider SDKs (primarily for Java), reference implementations, samples and test suite.[6]


The effort was formalized in 2009 with the formation of the Change Management workgroup [7] and participation of individuals from Accenture, Eclipse Mylyn/Tasktop,[8] and IBM. Since then, new workgroups have formed around other lifecycle topics and individuals representing about 30 different organizations, including Oracle, Siemens, Northrop Grumman, Tieto, and General Motors. IBM's Cloud and Smarter Infrastructure brand is also starting to use OSLC as an integration technology.[9]


The OSLC specifications build on the W3C Resource Description Framework (RDF), Linked Data and REST, enabling integration at data level via links between related resources. OSLC resources are defined in terms of RDF properties. Operations on resources are performed using HTTP. OSLC also specifies user interface techniques to enable preview, creation and selection of links.[10]

See also[edit]


  1. ^ "IBM hails ALM standards participation". 2009-08-25. Archived from the original on 2012-10-14. Retrieved 2013-07-18.
  2. ^ "Open Services for Lifecycle Collaboration". Retrieved 2013-07-18.
  3. ^ "Specifications < Main < TWiki". Retrieved 2014-06-09.
  4. ^ "About". Open Services for Lifecycle Collaboration. Retrieved 2015-08-27.
  5. ^ Speicher, Steve (2011-02-23). "Open Services for Lifecycle Collaboration and More: The "O" in OSLC". Retrieved 2013-07-18.
  6. ^ "Eclipse Lyo". October 2013.
  7. ^ "IBM supports Open CM initiative in tools – SD Times: Software Development News". SD Times. Archived from the original on 2012-03-25. Retrieved 2013-07-18.
  8. ^ "OSLC Lifecycle Interoperability Makes Headway | Dr Dobb's". 2009-08-26. Retrieved 2013-07-18.
  9. ^ "IBM Pulse 2011 – The Tivoli with two minds – Trip Report – Coté's People Over Process". 2011-03-07. Retrieved 2013-07-18.
  10. ^ "OslcCoreSpecification < Main < TWiki". Retrieved 2013-07-18.

External links[edit]