The OSLC Open Project (OSLC-OP) has recently published Project Specification  OSLC Configuration Management Version 1.0,  revision 01. The OSLC-OP believes the specification is stable, and covers the features required to meet it’s intended objectives. Therefore, the OSLC-OP is considering promoting this PS01 to Candidate OASIS Standard.

To do so, we need three or more Statements of Use. These statements of use will provide insight gained from many implementations, integrations with other lifecycle management tools, and user experience, while maintaining compatibility with OSLC specifications.

The OSLC Open Project is ready to accept Statements of Use from implementers. This is an essential part of the OASIS standardization process and will enable us to progress to OASIS Standard. Please see Section 14 of the OASIS Open Project Rules for more information. In summary:

“Statement of Use“, with respect to a Committee Specification or Project Specification, is a written statement that a party has successfully used or implemented that specification in accordance with all or some of its conformance clauses, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations. The Statement of Use must be made to a specific version of the Specification and must include the Specification’s approval date. The party may be an OASIS Member or a non-member. In case of a non-member, the Statement of Use must be submitted via the Technical Committee’s or Project Governing Board’s comment facility. A TC or PGB may require a Statement of Use to include hyperlinks to documents, files or demonstration transcripts that enable the committee’s members to evaluate the implementation or usage. A Statement of Use submitted to the TC or PGB must be approved by TC Resolution or PGB action as an acceptable Statement of Use with respect to the Specification. A party can only issue one Statement of Use for a given specification. When issued by an OASIS Organizational Member, a Statement of Use must be endorsed by the Organizational Member’s Primary Representative

Statements of Use must be endorsed by the OASIS Organizational Member's Primary Representative. Submitters just need to notify the OSLC-OP PGB, by submitting their 'Statement of Use' to the oslc-op@... oslc-op@... mailing list. A typical statement of use could be:

<insert name / org here> has successfully implemented Specification  OSLC Configuration Management Version 1.0,  revision 01, dated 30 May 2022, in accordance with the conformance clauses defined in Section 4 "Conformance" of the specification and its related multi-part specification. This use of the specification includes interoperation with other similar independent implementations, as well as integration with tools supporting other OSLC domain specifications.