PAC: Final draft (unofficial)

[Jon Bosak <Jon.Bosak@eng.sun.com>]

This is my copy of the draft of Core Structural Decision CS 1
(formerly known as Basic Structural Decision BS 0) that was
formally adopted by the PAC at its meeting in San Jose this
afternoon.  This is not the official copy; that will be posted
when the minutes are made available.  I am providing this to the
PAC so that the PAC Secretary has another copy to check against.

Jon

==================================================================

CS 1. Filtering and interTC coordination

Background

OASIS cannot make or enforce policy regarding TC initiation and
coordination and still remain scalable over an unlimited number of
technical specification activities.

Action

1. OASIS shall provide administrative oversight (chiefly so that
   procedural irregularities can be appealed) but not coordination.

   Situations in which OASIS shall not attempt to coordinate TCs
   include:

    - Creation of a TC in direct competition with an existing TC
      in the same problem space

    - Creation of a TC to solve a problem generally regarded as
      unsolvable

    - Creation of a TC that addresses problems generally regarded
      as already solved.

2. Approval of a new TC shall be conditioned on formal criteria,
   but not on its intent or its actual or potential overlap with
   other TCs or existing industry efforts outside of OASIS.

3. Among the approval criteria for TCs is that the proposal shall
   contain at least the following items, written in English and
   provided in electronic form as plain text:

    - name of TC

    - statement of purpose

    - list of deliverables, with projected dates

    - proposed meeting schedule for the year following the
      formation of the TC, or until the projected date of the
      final deliverable, whichever comes first

    - names of at least three individual OASIS members or
      employees of OASIS member organizations committed to the
      meeting schedule

    - name of chair

    - names of phone meeting sponsors, if any

    - names of face-to-face meeting sponsors, if any

   The stated purpose of the TC must be germane to the mission of
   OASIS.

   The TC must meet at least once before the projected date of its
   first deliverable and must in any case meet at least once a
   year.  Phone meetings count as meetings.

4. A formal mechanism (the Motion to Connect, or form a joint
   subcommittee) shall be provided whereby multiple TCs can
   coordinate their efforts if they mutually agree to do so; but
   failure to coordinate shall not be subject to appeal.

5. A formal mechanism shall be provided whereby a certain number
   of individual OASIS members or members of OASIS organizations
   can notify one or more TCs of the existence of an issue needing
   resolution among TCs and request that the TCs coordinate to
   resolve the issue.

6. OASIS shall create a publicly subscribable electronic mailing
   list for public announcements from designated persons.  The
   list shall be notified of the following phase transitions: list
   formation, TC proposal, charter publication, TC formation,
   working draft publication, final committee specification
   publication, call for implementation, call for approval as an
   OASIS standard, approval or rejection of a proposed standard,
   and change of status of the TC.  [This list is to be revised
   before completion of the process description.]

7. OASIS TC mailing list archives shall be visible to the general
   public.

8. OASIS shall provide a publicly readable comments archive for
   each TC.  This archive can be posted to by any individual OASIS
   member or employee of an OASIS member organization.  The
   archive may also be enabled to accept comments from other
   groups or from the public at large by resolution of the TC.
   The TC does not have to respond to comments.