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

 


Help: OASIS Mailing Lists Help | MarkMail Help

tgf message

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


Subject: STATEMENTS OF USE


On the TC call yesterday the question was asked of what constitutes an acceptable Statement of Use.  Below is the Definition from the TC Process manual and this answers all of the questions raised, particularly those points that I have high-lighted.  I hope this will enable one of you to provide the further SoU that we require to move TGF v2.0 on to a Candidate Standard.

If anyone wants any further guidance on this please get in touch.

"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.


John


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