Use of non-OASIS facility by Requirements Subcommittee

The OASIS Technical Committee Guidelines include the following policy on acceptable use of non-OASIS facilities by OASIS Technical Committees:

In some instances, a TC may need certain functionality that OASIS is not currently able to provide. For example, OASIS is not currently hosting a joint development environment such as CVS or SourceForge. A TC may use a non-OASIS facility only under the following conditions:

· The OASIS-provided web pages, email lists, etc. are the official and primary means used by the TC to discuss development, conduct TC business, publicize TC activities, etc.

· The TC chair first contacts OASIS Admin to ascertain that OASIS is not able to provide the needed functionality;

· The use of a non-OASIS facility will not in any way prevent or discourage equal access of all TC members to the functionality;

· The use of such a functionality will not impair the ability of the public to view the TC’s activities;

· Periodic drafts of the work are submitted to the document repository on the OASIS server; and

· The entire activity and its history can be moved to OASIS servers at whatever point OASIS is able to offer this functionality.

As co-chair I have concluded that the Requirements Subcommittee’s proposal for moving forward (as submitted by Scott Came) substantially complies with these requirements, provided the Secretary posts the address for the Wiki to the TC webpage to inform interested members of the public of the use of a non-OASIS facility and how they can access it.

Any member of the TC who feels that my decision is wrong may appeal the matter to Patrick Gannon, President and CEO of OASIS.

John M. Greacen

Greacen Associates, LLC

HCR 78, Box 23

Regina, New Mexico 87046

505-289-2164

505-289-2163 (fax)

505-780-1450 (cell)

legalxml-courtfiling message