1. Why Proposed TC Procedures? Define how TC reaches “completion” of what OASIS calls “Committee Specifications” TC procedures lead up to the OASIS process: Approval of a Committee Specification: Upon completion of a specification the TC may approve the work as a Committee Specification. The approval of a Committee Specification shall require at least 2/3 of the total membership of a TC voting to approve and no more than 1/4 voting to disapprove. Procedures ensure logical development Help keep work products on track

2. Specification Development 1.Statement of Work 2.Requirements Document 3.Candidate Specification a 4.Proposed Specification b 5.Recommended Specification b 6.On to OASIS or others to consider (optional) a = OASIS “Committee Draft” b = OASIS “Committee Specification”

3. Statement of Work Proposer(s) (from TC) initiate this –TC can appoint proposer(s) to do it State what is to be done, why, & when –Identify needs, constraints, deadlines, schedule Identify proposed authors & resource needs Published to Web site for TC review Approval = consent to apply resources to it

4. Requirements Document Drafted by assigned authors –…uniquely [identify] each requirement for purposes of traceability in subsequent stages… [including compliance criteria] Published on TC Web site for review Review: obtain / consider / report input at a face-to-face TC meeting and on TC Listserv on Public Comment List Approval = proceed with specification draft

5. Candidate Specification Draft prepared by assigned authors Published on TC Web site for review Review: obtain / consider / report input at a face-to-face TC meeting and on TC Listserv on Public Comment List Approval = TC’s “Proposed Specification” Formally edited, published to Web site / repository

6. Proposed Specification Can result in implementation by OASIS members –Criteria for testing & evaluation –Certification requirements, compliance criteria Revisions to be based on lessons learned Review: obtain / consider / report input Approval = TC’s “Recommended Specification” c Approval = an “OASIS Committee Specification” Formally edited, published to Web site / repository c The highest level for a specification (“standard”)

7. OASIS Standard TC may elect to submit its Committee Specification (AKA, “Recommended Specification”) to the OASIS Process –see www.oasis- open.org/committees/process.shtml#approval_spec www.oasis- open.org/committees/process.shtml#approval_spec OASIS approval = “OASIS Standard”

8. Other Groups The TC may elect to submit its specification (“Proposed” or “Recommended”) to other groups for review and approval as standards –Example: The Court Filing TC submitted Court Filing 1.1 to the Joint Technology Committee of COSCA/NACM (Conference of State Court Administrators/National Association for Court Management) for review and adoption

9. Roles Proposer(s), author(s) Draft, take input, rewrite, take the heat TC Chairs d TC Secretary d TC Editor d Provide templates, consult on writing, final editing TC Web master d Publish, design for clarity, version control Ombudsman to Public Comment List d Committee to maintain official TC documents