PAC: Process issues (2000.05.01)

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

To: workprocess@lists.oasis-open.org
Subject: PAC: Process issues (2000.05.01)

Here is where our issues list stands at present.  I have added MT
16 and MT 17 to the miscellaneous catchall at the end.

Note to lurkers: This is an unofficial document that the PAC uses
to keep track of its work.  We have finished with issues RQ 1-4,
CS 1-2, and CM 4-6; we are considering final language for issues
CS 3-6; we are considering draft language for CM 1; and we have
reorganized and rethought issues CT 1-7.

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

A. REQUIREMENTS AND DESIGN PRINCIPLES

   RQ 1. Use cases

   RQ 2. Resource/funding model

   RQ 3. Process modules/phases

   RQ 4. Outcomes (specifications, standards, ...)

B. CORE STRUCTURAL DECISIONS

   CS 1. Filtering and interTC coordination

   CS 2. Automatic vs. manual committee membership maintenance
         (see D below)

   CS 3. Individuals vs. organizations

   CS 4. Voters vs. observers
 
   CS 5. Public vs. private

   CS 6. Language communities

C. TECHNICAL COMMITTEE TAXONOMY

   CT 1. Technical specification committees

   CT 2. Maintenance committees

   CT 3. Joint subcommittees

   CT 4. Charter committees

   CT 5. Industry harmonization committees

   CT 6. Coordination committees 

   CT 7. Translation committees

D. COMMITTEE MAINTENANCE

   CM 1. Creating committees

   CM 2. Disbanding committees

   CM 3. Term limits

   CM 4. Adding and removing voting members

   CM 5. Adding and removing observers

   CM 6. Leaves of absence

   CM 7. Appeal

   CM 8. Requirements for administrative support

E. RULES OF ORDER

   RO 1. Authority of last resort

   RO 2. Committee manual

   RO 3. Committee manual translation

F. MISCELLANEOUS QUESTIONS

   MI 1. Shall agendas be required in advance of committee meetings?

   MI 2. Shall proxies be allowed?

   MI 3. To what extent shall committees be allowed to revisit
         their charters and/or requirements?

   MI 4. Does a transferred associate membership automatically confer
         committee membership upon the transferee?

   MI 5. Can a request for action by OASIS come directly from an
         outside organization, or must it always be submitted on
         behalf of that organization by one or more OASIS members?

   MI 6. Does OASIS standardization of a collaborative effort require
         a formal vote of all the collaborating organizations?

   MI 7. What is the vote in a committee required for the approval of
         a technical specification?

   MT 8. Shall co-chairs be provided for in the process?  If so,
         shall their number be limited?

   MT 9. What kind of contact information shall be required for
         the members named in a TC charter?

   MT 10. [how to conduct an email vote]

   MT 11. [revisit participation by phone]

   MT 12. [specification editors]

   MT 13. Removing an obnoxious or obstructive
          member (Review Robert's to see if we need to change/amend)

   MT 14. The board appoints a TC, but when the board expires, the
	  TCs continue; i.e., TCs do not need to be reinitialized by
	  the board.  Although TCs exist year to year, their
	  subcommittees do not. Subcommittees must be reconstituted
	  annually by their committee.  If a committee dies, its
	  subcommittees die with it.

   MT 15. Leave of absence by chair, length of term, chair pro
          tem, related issues.

   MT 16. Must minutes of TC meetings be published to the TC
	  mailing list?  (The answer is yes, but I don't think
	  we've captured this anywhere yet.)

   MT 17. Revisit the question of what constitutes a
	  session.  (From RROR: "When a committee adjourns without
	  appointing a time for the next meeting, it is considered
	  as having adjourned at the call of the chair, so that all
	  the meetings of a special committee constitute one
	  session.")