Longdesc Transition Prep

Emails

• Reply to EOWG Chaals
• Reply to UAWG Chaals

Publication

Before going to the TF

• Write Document Status Section
• Write Exit Criteria (Mark is Drafting) But chaals wrote a draft and shared it w/ Mark.

In the Task Force

• Get TF then WG approval of the exit criteria
• Record Decision to request WG request the transition

When the TF has agreed

• Get WG to request the transition
• Schedule Meeting with Director, HTML chairs as needed

Needed for Director's meeting

• Report of important changes to the document
• Record Objections
• Patent disclosures
• Verify no open exclusion opportunities
• Evidence that the document satisfies group's requirements
• Evidence that dependencies with other groups are met
• Evidence that the document has- received wide review
• Evidence that issues have been formally addressed
• Implementation Report (Mark is Drafting)
• Prepare Spec to pass pubrules
• Verify that transition requirements have been met
• Send Transition Request
• Create Agenda (This should just be "step through the transition request" which has all the things that need to get checked)
• Reserve Teleconference Bridge
• Transition Meeting Prep/Practice (Don't bother with this. The "director" who sounds a lot like Ralph will check through the things required, which should be in the transition request, and if we're good, says "OK". If you are really concerned, ask PLH to have a quick look first).
• Transition Meeting

When we are approved for Proposed Rec

• Create a Publication Schedule
• The Team Contact reviews the (Team-only) pre-publication steps.
• Send a pub request
• install the document in its final location
• Meeting with Shawn to do WAI messaging
• Send DRAFT transition announcement to Comm Team
• Public Mailing List
• Team Only Mailing List
• The Facilitators fwd announcement to WG and TF-

DONE

• Reply to Matt Turvey Chaals
• Chaals will scribe transition call.