[conformance] OASIS process: How to become an OASIS Standard

[Lynne Rosenthal <lynne.rosenthal@nist.gov>]

Hello All
The following is a summary of
the steps needed to make a Committee Specification an OASIS
Standard.  After the ballot (approval of committee
specification),  we will pursue an email discussion, regarding the
following.

The process to pursue OASIS Standard is described in the
TC
Committee Process
and
Committee
Guidelines. 
To summarize:

1.      TC votes whether to submit the Committee Specification to OASIS membership for consideration as an OASIS Standard

2.

      

TC
chair prepares the submission:

a.      Reference to the specification

b.

      

Summary
of the specification
c.

      

Certification
by at least 3 member OASIS member organizations that they are
successfully using the specification (see NOTE below).  This
certification can be in the form of an email from a company
representative, e.g., I certify that XYZ company is successfully
using…”.
d.

      

OASIS
copyright statement is on the document 
e.

      

All
TC members have been provided with a copy of the OASIS IPR 
policy

3.      Document submitted to Karl Best  with the above information for a 90-day membership review, followed by a 30-day membership vote.  

4.

      

Approval
is as follows:  At least 10% of the membership must vote.  If
more than 10% of membership vote, but less than 10% are affirmative
votes  the Specification fails.  If there are 10% or more
negative votes  the Specification fails. 

NOTE:  Certification of successfully using.  
According to the Committee Guidelines, “The OASIS TC Administrator feels
it is not in the TC’s best interests to further define the meaning of
“successfully using”.  The implementation could really be anything
from prototypes or proof of concept all the way up to shrink-wrapped
software.  Defining this further would only restrict the definition
and make it harder for member organizations to say that they are
successfully using the specification.”