The table below provides a convenient place to see the currently available OSLC specifications, their status, and links to the documents. Many of these specifications are still under development so you should consult the actual documents for the most up to date information.
All OSLC specifications are governed by OASIS Technical Committees including:
The titles below are abbreviated for convenience. The full titles a available from the linked documents. For multi-part specifications, typically only the main specification is listed. The other parts are available from that specification.
Status refers to the OASIS Standards Track Work Products in the OASIS Naming Directives
- Working Draft (WD) [not approved, no official status]
- Committee Specification Draft (CSD)
- Committee Specification Public Review Draft (CSPRD)
- Committee Specification (CS)
- Candidate OASIS Standard (COS)
- OASIS Standard (OS)
- Final Indicates an open-services.net OSLC specification that has not yet been migrated to OASIS.
Note: The open-services.net specifications that are being migrated to OASIS by the OSLC Domains TC are strictly a document maintenance exercise. That is, a Final open-service.net specification may appear as an OASIS CSD with different formatting, but will have the same specification normative content. Migration of these documents to OASIS will therefore have no impact on implementations. open-services.net specifications that do not yet have at least OASIS CSD status will reference the existing (PDF) open-services.net specification, and the status will be shown in italics.
|Title||Status||Governing OASIS TC||Description|
|Core 3.0||CS||OSLC Core TC||A collection of specifications that defines the basic patterns, protocols and capabilities of OSLC clients and servers.|
|Resource Shape 3.0||CS||OSLC Core TC||Describes constraints on OSLC vocabularies for different proposes, including for OSLC itself.|
|OSLC Query 2.0||Finalized||OSLC Core TC||Defines a simple, implementation independent selection and projection query capability.|
|Tracked Resource Set 2.0||Finalizing Draft||OSLC Core TC||Allows servers to expose a set of resources whose state can be tracked by clients.|
|Configuration Management 1.0||WD||OSLC Core TC||OSLC Configuration Management defines an RDF vocabulary and a set of REST APIs for managing versions and configurations of linked data resources from multiple domains.|
|Requirements Management 2.0||Finalized||OSLC Domains TC||Defines the OSLC services and vocabulary for the Requirements Management domain.|
|Change Management 3.0||CSPRD01||OSLC Domains TC||Defines the OSLC services and vocabulary for the Change Management domain.|
|Quality Management 2.0||Finalized||OSLC Domains TC||Defines the OSLC services and vocabulary for the Quality Management domain.|
|Architecture Management 2.0||Finalized||OSLC Domains TC||Defines the OSLC services and vocabulary for the Architecture Management domain.|
|Asset Management 2.0||Finalized||OSLC Domains TC||Defines the OSLC services and vocabulary for the Asset Management domain.|
|Automation 2.0||Finalized||OSLC Core TC||Defines the OSLC services and vocabulary for the domain that supports automation of sequences of actions on OSLC resources.|
|Performance Monitoring 2.0||Finalized||OSLC Domains TC||Defines the OSLC services and vocabulary for the Performance Monitoring domain.|
|PROMCODE 1.0||WD||OSLC PROMCODE TC||The PROMCODE (Project Management of Contracted Delivery for Software Supply Chains) defines OSLC services and vocabulary for exchanging project management information across organizational boundaries in support of Software Supply Chain (SSC) delivery.|
There are some additional OSLC documents that are currently inactive but could be sources of future specifications:
- Product Definition
- Estimation and Measurement
- Architecture Management 3.0
- Autiomation 2.1
- Actions 2.0
Anyone interested in contributing to these specifications should join the applicable TC and propose additional work to add to the TC charter.