The Art of Consensus: A Guidebook for W3C Group Chairs, Team Contact and Participants

<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="utf-8"> <title>The Art of Consensus: A Guidebook for W3C Group Chairs, Team Contact and Participants</title> <link rel="stylesheet" type="text/css" href="assets/main.css"> <link rel="shortcut icon" href="/Icons/WWW/Literature.gif"> </head> <body> <div id="header"> <span class="logo"><a href="https://www.w3.org/"><img src="https://www.w3.org/Icons/WWW/w3c_home_nb" alt="W3C"></a> </span> <div class="breadcrumb"> <a href="https://www.w3.org/get-involved/">Get involved</a> → <h1>The Art of Consensus</h1> </div> <p class="baseline">This <strong>Guidebook</strong> is the collected wisdom of the W3C Group Chairs, team contacts and other contributors.</p> </div> <div class="toc"> <h4>Also On This Page → </h4> <ul> <li style="display: none"><a href="#start">Start</a> • </li> <li><a href="#start">Starting a Group</a> • </li> <li><a href="#run">Running a Group</a> • </li> <li><a href="#Deliverables">Deliverables</a> • </li> <li><a href="#speaking">Speaking About Your Work</a> • </li> <li><a href="#ref">Reference</a> • </li> <li><a href="#sa34">Advice</a> • </li> <li><a href="#care-and-feeding">About the Guidebook</a></li> </ul> </div> <div class="events box"> <h4 id="training">Chair Training Modules</h4> <ul> <li>none upcoming at this time</li> <li>Previous: <ul> <li><a href="https://www.w3.org/2015/Talks/1217-github-w3c/">Using GitHub for W3C Specifications</a>, Philippe Le Hégaret, 17 December 2015 (<a href="https://www.w3.org/2015/12/17-git-minutes">Minutes</a>).</li> <li><a href="https://lists.w3.org/Archives/Member/chairs/2015OctDec/0020.html">Horizontal Review</a> (Member-only), Virginie Galindo, 13 October 2015 (<a href="https://www.w3.org/2015/10/13-chairing-minutes.html">Minutes</a>, <a href="https://media.w3.org/2015/10/chair-training-horizontal-review.ogg">recording</a>) and 20 October 2015(<a href="https://www.w3.org/2015/10/20-chairing-minutes.html">Minutes</a>) <a href="https://www.w3.org/2015/10/W3C-transversal-review-101_13OCT2015.pptx">slides in PPT</a>, <a href="https://www.w3.org/2015/10/W3C-transversal-review-101_13OCT2015.pdf">slides in PDF</a>] - See also <a href="https://www.w3.org/blog/2015/11/better-specifications-for-the-sake-of-the-web/">Blog post</a> for keeping your reviewer on track.</li> <li><a href="https://lists.w3.org/Archives/Member/chairs/2015JanMar/0009.html">Focus and Productivity</a> (Member-only), Arnaud Le Hors, 29 January 2015 (<a href="https://www.w3.org/2015/01/29-chairing-minutes.html">minutes</a>, <a href="https://media.w3.org/2015/01/chair-training-session-4.ogg">recording</a>)</li> <li><a href="https://lists.w3.org/Archives/Member/chairs/2014OctDec/att-0093/Chair_Training_-_Productivity_20141021.pdf">Focus and Productivity</a> (Member-only), by Arnaud Le Hors, 23 October 2014 (<a href="https://www.w3.org/2014/10/23-chairing-minutes">minutes</a>)</li> <li><a href="https://lists.w3.org/Archives/Member/chairs/2014AprJun/0136.html">The Human Dimension</a> (Member-only), Charles McCathie Nevile, 17 June 2014 (<a href="https://www.w3.org/2014/06/17-chairing-minutes.html">minutes</a>)</li> <li><a href="https://www.w3.org/2014/Talks/0423-tools-rrs/">Tools</a>, Ralph Swick, Thursday, 24 April 2014, 10-noon ET (<a href="https://www.w3.org/2014/04/24-chairing-minutes">minutes</a>)</li> <li><a href="https://www.w3.org/2014/Talks/chairs-part4/">The ABCs of W3C</a>, Philippe Le Hégaret, January 2014 (<a href="https://www.w3.org/2014/01/23-chairing-minutes.html">minutes</a>, <a href="https://media.w3.org/2014/01/chair-training-session-1.m4a">audio</a>)</li> </ul> </li> </ul> </div> <div class="events box"> <h4 id="current">Current and Upcoming</h4> <ul> <li><a href="https://lists.w3.org/Archives/Member/chairs/2024AprJun/0067.html">Upcoming publication moratorium for 2nd half of 2024</a> (add to your <a href="https://calendar.google.com/calendar/ical/c_90300da0c4eb1854f4d81481952279a15c2e4755d84f942ebc711c66127ec3cd%40group.calendar.google.com/public/basic.ics">calendar</a>) <ul> <li>End of Year: December 20 - January 1</li> </ul> </li> <li>Planning a group meeting? Ask your Team Contact to update the <a href="https://www.w3.org/participate/eventscal.html">W3C calendar</a> using the <a href="https://www.w3.org/Web/Tools/Events/">Events tool (Team and Offices-only)</a></li> </ul> </div> <div class="toolbox box" style="margin-bottom: 1em"> <h4>Nearby</h4> <ul> <li><a href="https://www.w3.org/Guide/chair/buddy.html">W3C Chair Buddy System</a></li> <li><a href="/groups/">List of groups</a></li> <li><a href="https://lists.w3.org/">Mailing list archive search</a></li> <li>Databases: <a href="https://www.w3.org/groups">Groups</a></li> <li>Calendars: <a href="https://www.w3.org/participate/eventscal.html">Face-to-Face Meetings</a></li> <li>Mailing list archives: <a href="https://www.w3.org/Archives/Member/chairs/">chairs</a> (Member-only), <a href="https://lists.w3.org/Archives/Member/w3c-tools/">w3c-tools</a> (Member-only)</li> <li>Got a question? Join #general in <a href="https://irc.w3.org/?channels=general">irc</a> or <a href="https://w3ccommunity.slack.com/">slack</a> (<a href="https://www.w3.org/slack-w3ccommunity-invite">invite</a>). </ul> </div> <div class="left" style="margin-top: 1em">  <h3 id="start" style="margin-top: 2em">Starting a Group</h3> <ul> <li><a href="https://www.w3.org/Guide/standards-track/">Recommendation Track Readiness Best Practices</a></li> <li><a id="Charters" href="process/charter.html">Create a Charter</a>;  </li> <li><a href="https://www.w3.org/Guide/incubation.html">How to incubate</a> <ul> <li><a href="https://www.w3.org/community/">W3C Community & Business Groups</a></li> <li><a href="https://www.w3.org/2016/04/cg-support/">W3C Team support for W3C Community Groups</a></li> <li><a href="https://www.w3.org/Guide/meetings/workshops.html">W3C Workshops</a> for starting incubation</li> </ul> </li> <li><a href="process/cg-transition.html">How to transition work from a Community Group to a Working Group</a></li> <li><a href="https://www.w3.org/participate/faq.html#join">Join a group</a> (see also <a href="https://www.w3.org/2004/08/invexp.html">Invited Expert Policy</a>)</li> <li>If you need a blog, wiki, GitHub repository, or mailing list, ask your team contact.</li> <li>...more <a href="#roles">advice on roles in a group</a></li> </ul> <h3 id="run">Running a Group</h3> <ul> <li><a href="https://www.w3.org/Guide/chair/buddy.html">W3C Chair Buddy System</a> (volunteer experienced Chairs can mentor other Chairs)</li> <li>Check out our <a href="https://www.w3.org/PM/Groups/chairboards.html?gtype=working">Working Groups</a> and <a href="https://www.w3.org/PM/Groups/chairboards.html?gtype=interest">Interest Groups</a> dashboards to navigate through what we know about them. The Project Management team only maintains a <a href="https://www.w3.org/PM/">collection of links and tools</a> to keep track. </li> <li><a href="https://www.w3.org/wiki/Moderating_Meetings">Moderating (Facilitating) Meetings</a></li> <li><a href="https://www.w3.org/wiki/Speaker_Resources">Creating and delivering effective presentations</a></li> <li id="meetingbots">Running a Meeting (especially a teleconference) on <a href="https://www.w3.org/Project/IRC/">IRC</a> (<a href="https://irc.w3.org/">Web client</a>): <ul> <li>See <a href="tools/new-group.html">how to setup a new group</a> for general tooling advises</li> <li><a href="https://w3c.github.io/scribe2/scribedoc.html">Quick start guide</a> on setting up tools for managing an agenda, generating minutes, and updating issues lists</li> <li><a href="https://www.w3.org/Guide/meetings/zoom">Scheduling teleconferences</a></li> <li><a href="https://www.w3.org/Guide/meetings/organize.html#calendars">Group calendars</a></li> <li><a href="https://www.w3.org/wiki/Holidays">Holidays wiki</a> to help planning WG work around recurring holidays</li> <li>Individual IRC tools ("bots"): <ul> <li><a href="https://www.w3.org/2001/12/zakim-irc-bot.html">Zakim</a> for queue management, start and end meeting</li> <li><a href="https://www.w3.org/2002/03/RRSAgent">RRSAgent</a> for minutes management</li> <li>Hints for <a href="https://w3c.github.io/scribe2/rescue.html" >rescuing minutes when RRSAgent is absent</a></li> </ul> </li> </ul> </li> <li><a id="predicting" href="process/predicting-milestones.html">Predicting milestones</a>, use our <a href='https://w3c.github.io/spec-releases/milestones/'>milestones calculator</a> to help with dates.</li> <li id="Meetings">Face-to-face meetings <ul> <li><strong><a href="meetings/continuity">Continuity of Operations under Travel Restrictions</a></strong></li> <li><a href="meetings/hosting.html">Host a face-to-face meeting</a> and <a href="https://www.w3.org/2011/06/WorkshopHost.html">Standard Venue Arrangements for W3C Events: Conferences, Workshops, and Meetings</a></li> <li><a href="https://www.w3.org/2004/06/NoNDAPolicy.html">Policy Regarding Non-Disclosure Agreements and W3C Meetings</a></li> <li><a href="https://lists.w3.org/Archives/Member/chairs/2017JanMar/0141.html">W3C Travel Policy affecting Staff Contacts</a></li> </ul> </li> <li>Issue tracking: <ul> <li>Use <a href="https://github.com/w3c/">GitHub</a> to track issues through mail and the Web</li> </ul> </li> <li><a href="https://www.w3.org/2002/09/wbs/">WBS</a> for questionnaires</li> <li>People management <ul> <li><a href="https://www.w3.org/wiki/Guide/HumanDimension">HumanDimension</a> (a Chair training module)</li> <li><a href="/policies/code-of-conduct/">Code of Conduct</a> and <a href="/about/positive-work-environment/#Procedures">Procedures</a> to assist all parties when issues arise. We have <a href="process/suspension.html">guidelines to suspend or remove participants from groups</a>. See more on the <a href="https://www.w3.org/Consortium/pwe">Positive Work Environment Home Page</a></li> </ul> </li> <li><a href="/policies/antitrust/">Antitrust and competition policy</a></li> <li><a href="/copyright/">Copyrights for documents, software, tests</a></li> <li>...more <a href="#mtg-advice">advice on meetings, decisions, issue tracking</a></li> </ul> <h3 id="close">Closing a Group</h3> <ul> <li><a href="./process/closing-wg">How to Close a Working Group</a></li> </ul> <h3 id="Deliverables">Specification Development</h3> <ul> <li><a href="editor/">W3C Editors home page</a> and specifically the <a href="editor/editors-draft">Style for Group-internal Drafts</a> </li> <li>Advancement on the Recommendation Track: <ul> <li><a href="https://github.com/w3c/wg-effectiveness/blob/master/process.md">W3C Process for Busy People</a></li> <li><a href="/policies/process/#rec-advance">Section 6.3 Technical Reports</a> of the W3C Process</li> <li>Considerations for <a href="process/joint-deliverables.html">joint deliverables</a></li> <li><a href="https://www.w3.org/Guide/transitions/">Transition requirements</a> for all W3C maturity levels (First Public Draft, Last Call, CR, PR, REC, etc.). Try also our <a href="https://w3c.github.io/transitions/nextstep.html">step finder</a> and look at <a href="https://w3c.github.io/spec-releases/milestones/">milestones calculator</a>.</li> <li><a href="https://www.w3.org/Guide/documentreview/">Request Wide Review</a> at least <em>2-3 months before CR</em>, to allow time for discussion and rework. This includes requesting <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal reviews</a>. </li> <li><a href="https://www.w3.org/pubrules/">Pubrules</a> (<a href="https://www.w3.org/pubrules/doc">publication requirements</a>) and links to related policies (e.g., <a href="https://www.w3.org/2005/07/13-nsuri">namespaces</a>, <a href="https://www.w3.org/2020/01/registering-mediatypes">MIME type registration</a>, <a href="https://www.w3.org/2005/05/tr-versions">version management</a>, and <a href="https://www.w3.org/2003/01/republishing/">in-place modifications</a>)<br> See also <a href="https://github.com/w3c/specberus/issues">Pubrules issue management</a></li> <li><strong>March 2017</strong>: <a href="https://www.w3.org/2016/11/obsoleting-rescinding/">Obsoleting and Rescinding W3C Specifications</a></li> </ul> </li> <li><a href="process/tilt/normative-references.html">Normative References</a>; considerations the Team takes into account when evaluating normative references</li> <li>Addressing formal objections: <a href='./council/council'>best practices to resolve and decide Formal Objections</a> (aka council guide)</li> <li>Publications can only happen on Tuesdays and Thursdays (<a href="https://lists.w3.org/Archives/Member/chairs/2009JanMar/0192.html">Member-only archive of announcement</a>), unless you use the <a href="https://github.com/w3c/echidna/wiki">automated publication system</a></li> <li><strong>September 2015</strong>: W3C Comm Team no longer post Homepage News stories for regular WDs publications, unless explicitly requested at publication request.</li> <li><a href="process/binding-license">W3C Documents and license related to API definitions, code samples, or examples</a></li> <li>Discussion about specifications tooling and versioning on <a href="https://lists.w3.org/Archives/Public/spec-prod/">spec-prod@w3.org</a></li> <li>...more <a href="#spec-advice">advice on specification development</a></li> </ul> <h3 id="speaking">Speaking About Your Work</h3> <ul> <li>Blogs, articles, Press interviews: Working Group participants, TAG Members, W3C Staff are among the world's experts in Web technologies and their impacts. Give heads-up, share relevant work, things you author, or press enquiries, by writing to the W3C Comm team (<a href="mailto:w3t-pr@w3.org">w3t-pr@w3.org</a>) about how you may attribute your work (or not) to W3C.</li> <li>Use the <a href="https://www.w3.org/blog/talks/how-to-add-a-new-talk/">Upcoming Talks form</a> (W3C Group participants, members of the W3C Team, and Office Staff); talks publicized on <a href="https://www.w3.org/">W3C home page</a>, <a href="https://lists.w3.org/Archives/Public/w3c-announce/">Public Weekly Newsletter</a>, W3C Social Media.</li> <li><a href="https://www.w3.org/2004/12/testimonial_pr-guidelines.html">Press release testimonial guidelines</a></li> <li><a href="https://www.w3.org/wiki/Speaker_Resources">Creating and delivering effective presentations</a></li> <li><a href="https://www.w3.org/WAI/training/accessible">How to Make Presentations Accessible to All</a></li> </ul> </div> <h2 id="ref">Reference</h2> <p><em>Tools in this section and the previous are in wide use and are supported by the systems team (ask for help on <a href="mailto:sysreq@w3.org">sysreq@w3.org</a>) and comm team. For service enhancements or new systems projects, please contact <a href="mailto:w3t-sys@w3.org">w3t-sys@w3.org</a> with a detailed description of your needs. Outages and scheduled operations appear on the <a href="https://status.w3.org">W3C System Status page</a>. See <a href="#sa34">collected wisdom</a> below for less mature tools. </em></p> <div class="rightcol"> <h4 id="patents">Patent Policy</h4> <ul> <li><a href="/policies/patent-policy/">W3C Patent Policy</a></li> <li>Commentary: <a href="https://www.w3.org/2003/12/22-pp-faq.html">FAQ</a>, <a href="https://www.w3.org/2004/02/05-patentsummary.html">Summary</a>, and <a href="https://www.w3.org/2004/03/pp-points-20040210.html">Business Benefits</a> </li> <li>Patent Policy Information about Groups and Disclosures can be found from the <a href="https://www.w3.org/groups/">Group pages</a></li> <li>...more questions? Contact the <a href="https://www.w3.org/2004/pp/psig/"><abbr title="W3C Patents and Standards Interest Group">PSIG</abbr></a></li> </ul> <h4 id="testsuites">Test Suites</h4> <ul> <li>Start with <a href="http://web-platform-tests.org/">web-platform-tests</a>, home for the Open Web test suites (including W3C ones).</li> <li>All WPT contributions are licensed under the terms of the <a href='https://github.com/web-platform-tests/wpt/blob/master/LICENSE.md'>3-Clause BSD License</a>. For non-WPT test suites, see <a href="/copyright/test-suites-licenses/">Test suites licenses</a> for Contribution of Test Cases</li> <li>...more questions about the testing infrastructure? Contact <a href="https://lists.w3.org/Archives/Public/public-test-infra/">public-test-infra@w3.org</a></li> </ul> <h4 id="processdoc">Process</h4> <ul> <li><a href="/policies/process/">Operative W3C Process Document</a></li> <li> <span id='banning'></span>  <a id="suspension" href="process/suspension.html">Guidelines to suspend or remove participants from groups</a></li> <li><a href="process/suspension.html">Guidelines for disciplinary action</a></li> <li><a href="/policies/antitrust/">Antitrust and Competition Guidance</a></li> <li><a href="https://github.com/w3c/process/issues">Ongoing process issues</a>. Discussion happens in the context of the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.</li> <li>...more questions? Contact the <a href="https://www.w3.org/groups/other/ab/">Advisory Board</a></li> </ul> </div> <div class="left" style="width: 48%"> <h4 id="systems">Systems and Tools</h4> <ul> <li><a href="https://validator.w3.org/">Markup Validators</a>, <a href="https://validator.w3.org/checklink">Link checker</a>, <a href="https://www.w3.org/2002/01/spellchecker">Spell checker</a>, <a href="https://services.w3.org/htmldiff">HTML diff tool</a>, <a href="https://www.specref.org/">SpecRef</a>, <a href="https://labs.w3.org/normative-references/">normative references checker</a>, <a href="https://www.w3.org/2002/01/tr-automation/tr-biblio-ui">bibliography generator</a>, and <a href="https://www.w3.org/2004/12/wg-tools.html">more tools</a></li> <li>See also: <a href="https://www.w3.org/2006/tools/">Tools Wiki</a> and <a href="editor/">W3C Editors home page</a></li> <li><a href="https://lists.w3.org/Archives/Member/w3c-tools/">Mailing list archive</a> of tools announcements (Member-only)</li> <li><a href="https://www.w3.org/2002/02/auto-acl">Predefined ACLs</a></li> <li><a href="https://www.w3.org/users/myprofile">Edit your contact information or affiliation</a></li> <li>Start with <a href="https://github.com/w3c/modern-tooling/issues">modern tooling</a> for ongoing tooling issues.</li> </ul> <h4 id="mlistools">Mailing Lists</h4> <ul> <li><a href="https://www.w3.org/Member/Mail/AuditForm">Mailing List Audit</a> (who is subscribed, information about lists) (Member-only)</li> <li><a href="teamcontact/RemoteMaintainers.html">SmartList Remote Maintainers Guide</a></li> <li><a href="https://www.w3.org/2002/11/spam-filtering">Spam filtering options</a></li> <li><a href="https://www.w3.org/Search/Mail/">Mailing Lists Search service</a></li> </ul> <h4 id="policies">Guidelines and Policies</h4> <ul> <li><a href="/policies/antitrust/">Antitrust and Competition Guidance</a></li> <li><a href="https://www.w3.org/2015/04/charter-extensions.html">Charter Extensions</a></li> <li><a href="https://www.w3.org/2017/05/external-funding.html">External Funding</a></li> <li><a href="https://www.w3.org/participate/invited-experts/">Invited Experts policy</a></li> <li><a href="https://www.w3.org/policies/">IPR policies</a></li> <li><a href="https://www.w3.org/2004/06/NoNDAPolicy.html">NDAs and W3C Meetings</a></li> <li><a href="process/tilt/normative-references.html">Normative References guidelines</a></li> <li><a href="council/council">Processing of Formal Objections</a></li> <li><a href="https://www.w3.org/Guide/meetings/continuity.html">Continuity of Operations under Travel Restrictions</a></li> </ul> </div> <p style="clear: both"><strong>Note on Member Submissions: </strong> Per <a href="/policies/process/#SubmissionScope">section "Scope of Member Submissions" of the Process Document</a>, "when a technology overlaps in scope with the work of a chartered Working Group, Members SHOULD participate in the Working Group and contribute the technology to the group's process rather than seek publication through the Member Submission process." Read more about <a href="https://www.w3.org/submissions/guide/">how to send a Member Submission request</a>.</p> <h2 id="sa34">Collected Wisdom, Advice</h2> <p><em>Many of these resources were contributed by your colleagues; we invite you to write down and share your experiences as well. Discussion of issues that groups face take place on the chairs mailing list (Member-only <a href="https://www.w3.org/Archives/Member/chairs">archive</a>). You may also find <a href="chair/meetings">chairs meetings back to 1997</a> an interesting source of wisdom.</em></p> <div class="rightcol"> <h4 id="spec-advice">Advice on Specification Development</h4> <ul> <li>Most popular editing tools: <a href="https://speced.github.io/bikeshed/">Bikeshed</a>, <a href="https://github.com/speced/respec/wiki">respec</a></li> <li><a href="manual-of-style/">W3C Manual of Style</a></li> <li><a href="https://www.w3.org/2002/05/rec-tips">Tips for getting to Recommendation faster</a></li> </ul> <h4 id="GitHub">GitHub</h4> <ul> <li><a href="https://w3c.github.io/">W3C on GitHub</a></li> <li><a href="https://www.w3.org/2015/Talks/1217-github-w3c/">Using GitHub for W3C specifications (slides)</a></li> <li><a href="https://tobie.github.io/specs-on-github/">Using GitHub for Spec Work (documentation)</a></li> <li><a href="https://labs.w3.org/hatchery/repo-manager/">GitHub Repository Manager</a>: One interface to find all group github contributors and the IPR status</li> <li><a href="https://lists.w3.org/Archives/Member/chairs/2016OctDec/0100.html">Github repo activity digest</a> (Member-only)</li> <li><a href="https://lists.w3.org/Archives/Public/spec-prod/2017JanMar/0047.html">Adds preview and diff links to pull requests</a> (<a href="https://tobie.github.io/pr-preview/config.html">Config Helper</a>)</li> </ul> </div> <div class="left" style="width: 48%"> <h4 id="roles">Roles</h4> <ul> <li><a href="chair/role.html">Chair's role</a>; <a href="https://www.w3.org/wiki/MultipleChairs">Guidance for Multiple Chairs</a></li> <li><a href="editor/role.html">Editor's role</a>, <a href="https://www.w3.org/Signature/Contributor.html">Editor, Author, Contributor Policies</a></li> <li><a href="teamcontact/role.html">team contact's role</a></li> <li><a href="teamcontact/liaison-role.html">Liaison's role</a>. <strong>Note:</strong> Per <a href="/policies/process/#Liaisons">section "Liaisons"</a> of the Process Document, liaisons MUST be coordinated by the Team due to requirements for public communication; patent, copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements. </li> <li><a href="https://www.w3.org/Member/faq.html">Advisory Committee Representative</a> (Member-only)</li> <li><a href="other/elected-body-communication-guidelines.html">Guidelines for communicating as a member of a W3C elected body</a></li> </ul> <h4 id="mtg-advice">Advice on Meetings, Decisions, Issue Tracking</h4> <ul> <li><a href="https://www.w3.org/wiki/FrontPage">ESW Wiki</a> patterns: <a href="https://www.w3.org/wiki/MidwestWeeklyAgenda">MidwestWeeklyAgenda</a>, <a href="https://www.w3.org/wiki/MeetingRecords">MeetingRecords</a>, <a href="https://www.w3.org/wiki/TrackingIssues">TrackingIssues</a> </li> <li>Doing a <a href="meetings/hybrid-meeting">Hybrid Group Meeting</a></li> <li><a href="https://www.fastcompany.com/26726/seven-sins-deadly-meetings">The Seven Sins of Deadly Meetings</a></li> </ul> <h4 id="historical">Historical</h4> <ul> <li><a id="xmlspec" href="https://www.w3.org/2002/xmlspec/">W3C XML Specification DTD (XMLspec)</a>, by Norman Walsh.</li> <li><a href="https://www.w3.org/2008/05/xmlspec-diff-generation/">XMLSpec diff generation</a></li> <li>QA resources: <a href="https://www.w3.org/TR/qaframe-spec/">Specification Guidelines</a>, <a href="https://www.w3.org/TR/qa-handbook/">Handbook for QA in groups</a>, and <a href="https://www.w3.org/QA/WG/qaframe-primer">QA Framework primer</a></li> <li><a href="https://www.w3.org/Talks/Tools/Slidy2/">HTML Slidy</a> for slide presentations</li> </ul> </div> <h2 style="clear: right" id="care-and-feeding">About the Guidebook</h2> <p>This Guidebook is intended to complement the <a href="https://www.w3.org/Consortium/Agreement/Appendix">W3C Membership Agreement</a> and the <a href="/policies/process/">W3C Process</a>. This index page is <strong>Public</strong>, although a small number of resources linked from this page may be visible only to the W3C Membership or Team.</p> <p>You are expected to be familiar with the parts of this Guidebook that affect your work. Working Group chairs should get a "tour" from their team contact. Then take a look again, for example, if you're going to hold a face-to-face meeting; read the <a href="#Meetings">section on meetings</a> to be sure you understand what's written there, and to record any valuable knowledge you pick up along the way.</p> <p>As editor of the guidebook, <a href="https://github.com/orgs/w3c/teams/guidebook">@w3c/guidebook</a> will do its best to see that it gets better over time. This does <i>not</i> mean that we do all the editing ourselves!</p> <p><strong>Note:</strong> Not all pages are maintained with the same frequency. Some may be quite outdated. Please add your issues to the <a href="https://github.com/w3c/Guide/issues">GitHub repository of this Guidebook</a> if you have any specific comments and/or proposals to improve this Guidebook.</p> <hr> <p>Feedback is to <a href="https://github.com/orgs/w3c/teams/guidebook">@w3c/guidebook</a> and is welcome on <a href="https://github.com/w3c/Guide/issues">GitHub</a></p> </body> </html>

CINXE.COM

The Art of Consensus: A Guidebook for W3C Group Chairs, Team Contact and Participants