OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: A Template for Statements of Use

TC chairs, 

I recently provided guidance to a Technical Committee on the proper form for Statements of Use. I thought it would be useful to provide this to all other TCs as well. 

The definition of Statement of Use in the TC Process reads as follows: 

"Statement of Use", with respect to a Committee 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 specified in Section 2.18, 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 Committee 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 on the TC comment-list. A TC may require a Statement of Use to include hyperlinks to documents, files or demonstration transcripts that enable TC members to evaluate the implementation or usage. A Statement of Use submitted to the TC must be approved by TC resolution as an acceptable Statement of Use with respect to the Committee 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." 

Note in particular that it... 

* must name a specific version of the Committee Specification, 
* must include the approval date, 
* must make reference to its conformance clauses and 
* must state whether or not its use included interoperation of multiple independent implementations. 

Also note that the TC must pass a resolution to accept the SoUs it receives. 

Given the above, here is a template you can use that will meet the requirements: 

<SoU provider> has successfully implemented <title and version number of the CS> Committee Specification <##> approved <date CS was approved>,
in accordance with <some of / all of > the conformance clauses contained in Section ## of the specification. <if "some," a statement describing which clauses were covered> This implementation <did / did not>  include interoperation with multiple, independent implementations.

Here is an example: 

EMC has successfully implemented the XACML REST Profile Version 1.0 Committee Specification 01 approved 05 April 2013, in accordance with the conformance clauses in Section 4 including all the mandatory features. This did not include interoperation with independent implementations.

Regarding the endorsement by an OASIS Organizational Member's Primary Representative, if the Primary is not a member of the TC (and thus not able to send to the TC mailing list) it is acceptable for the Primary to send the endorsement to another Organizational Member employee who is and can send to the TC on the Primary's behalf. 

Please let me know if you have any questions on this. 


Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]