Formal Objections: From Objection to W3C Council

This Guidebook documents the possible steps from Formal Objection to the creation of a W3C Council.

This document describes the different steps to resolve a Formal Objection. It should be kept synchronized with the W3C Process Document which is the authoritative source.

Note that at any step, the whole process might end by the originator by withdrawing the Formal Objection. This is the best outcome and should always be sought

1. Formal Objection received
2. The Staff Contact tries to resolve the Formal Objection before starting the process.
3. The FO stands: The Team assigns a “FO Assignee” to handle the Formal Objection. Note that is is not always the Staff Contact, but someone having knowledge of the issue raised in the FO.
4. The FO Assignee produces a Team Report:
   • The Team Report is circulated to the Team for review (one week review time)
   • The Team Report is circulated (at the same time or after Team review) to both parties.
5. The FO Assignee updates the Formal Objection dashboard.
6. The Council Staff Contact drafts an announcement and call for dismissal reasons with a minimum deadline of two weeks (See this example, and the Council composition).
   • Announcement is sent to the AC members list
7. The Council Staff Contact creates a new Group (name should be Council-YYYY-MM-<readable shortname>) in the db, filled with all the potential members of this Potential Council
8. The Council Staff Contact creates a new Mailing List (name should be group-council-YYYY-MM-<readable shortname>)
9. The Council Staff Contact tries to find a Chair for the Potential Council
10. The Council Staff Contact circulates the collected dismissal reasons to the Potential Council (1 week to amend or answer)
11. The Council Staff Contact circulates the Team Report while point above is discussed, if available
12. The Council Staff Contact create a WBS for dismissal, with the option to self-recuse, and accept the Chair, if found; if not ask for chairs.
13. If the Team Report contains a Team Recommendation that can resolve the FO:
    • The Council Staff Contact create a WBS for an Unanimous Short Ciruit
    • TAG and AB Staff Contact to ensure that everyone is voting
    • If the USC succeed, the Council is not formed and the resolution is accepted
14. If the chair is not found, the Potential Council elects one chair
15. If the chair is found:
    • The Council Staff Contact announce with Comm the composition of the Council to the AC
    • The Council Staff Contact announce to the Council that the Council started
    • The Council Staff Contact update the FO Dashboard to indicate that the Council started and the date
    • The Council Staff Contact adds to the FO Dashboard the 45 days dealine for this Council
16. The Council chair[s] (and Council Staff Contact) may start an Extraordinary Delegation WBS
17. The Council takes a decision
18. The Council writes a report
19. The Council Staff Contact ensures that the W3C Council as well as the FO Dashboard are updated
20. The decision is announced to the different parties and the AC
21. After the deadline for filing an appeal has passed, archive the Council Mailing List