[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Process issues (2000.03.03)
This is my current copy of our issues list. Section B has been relabeled and some things have been moved around. In particular, the former BS 1 (Web vs. hierarchy) has disappeared. We now consider all of the committees listed in section C to be technical committees (TCs) as described in the decisions we've made under CS 1 (see separate message for an unofficial copy of CS 1). Note to lurkers: This is an unofficial document that the PAC uses to keep track of its work. We have just finished CS 1 and will next be considering CS 2. ================================================================== 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]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC