You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
259 lines
9.3 KiB
259 lines
9.3 KiB
<?xml version="1.0" encoding="UTF-8"?><!--*- nxml -*-->
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<head profile="http://www.w3.org/2003/g/data-view">
|
|
<title>W3C Process: A Means to an End</title>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
|
|
<meta name="copyright" content="Copyright © 2005 World Wide Web Consortium (W3C)" />
|
|
<link rel="transformation" href="http://www.w3.org/2002/12/cal/glean-hcal.xsl" />
|
|
<link rel="stylesheet" href="http://www.w3.org/2005/03/slideshow.css"
|
|
type="text/css" media="screen, projection" />
|
|
<script src="http://www.w3.org/2005/03/slideshow.js" type="text/javascript">
|
|
<!-- see http://www.w3.org/2005/03/Demos/ -->
|
|
</script>
|
|
</head>
|
|
<body>
|
|
|
|
<div class="slide"><h1>W3C Process: A Means to an End</h1>
|
|
|
|
<address class="vcard">
|
|
<a class="url fn n" href="http://www.w3.org/People/Connolly/">
|
|
<span class="given-name">Dan</span>
|
|
<span class="family-name">Connolly</span></a><br />
|
|
</address>
|
|
|
|
<div class="vevent">
|
|
<a class="url summary" href="http://www.w3.org/2004/12/rules-ws/">W3C Workshop on Rule Languages for Interoperability</a><br />
|
|
<span class="location">Washington, DC</span>
|
|
<abbr class="dtstart" title="2005-04-27">27-28 Apr 2005</abbr>
|
|
</div>
|
|
|
|
<p>See also:</p>
|
|
<ul>
|
|
<li><cite><a href="http://www.w3.org/Consortium/Process/">W3C Process Document</a></cite>, especially
|
|
<ul>
|
|
<li><a href="http://www.w3.org/2004/02/Process-20040205/intro.html#Intro">Introduction section</a> which is a good one-page summary</li>
|
|
</ul>
|
|
</li>
|
|
<li><a href="http://www.w3.org/2001/02pd/rec54-img">process diagram</a> (<a href="http://www.w3.org/2001/02pd/rec54-img.png">in PNG</a>, <a href="http://www.w3.org/2001/02pd/rec54-img.svg">in SVG</a>)</li>
|
|
|
|
</ul>
|
|
|
|
<div><small>$Revision: 1.12 $
|
|
of $Date: 2005/10/19 22:08:58 $</small></div>
|
|
|
|
</div>
|
|
|
|
|
|
<div class="slide"><h1>W3C Core Values</h1>
|
|
<ul>
|
|
<li>Consensus</li>
|
|
<li>Interoperability</li>
|
|
<li>Good Design</li>
|
|
<li>Quality</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="slide"><h1>The End: Technology Deployment</h1>
|
|
<ul>
|
|
<li>Technologies
|
|
<ul>
|
|
<li> XHTML, CSS, MathML, SVG, SMIL (Interaction Domain)</li>
|
|
<li> RDF, XML D-Sig (Technology and Society)</li>
|
|
<li> XML Schema, SOAP (Architecture Domain)</li>
|
|
</ul>
|
|
</li>
|
|
<li>Integrated approach
|
|
<ul>
|
|
<li>Internationalization</li>
|
|
<li>Web Accessibility</li>
|
|
<li>Web Architecture (TAG)</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
<div class="slide"><h1>Web Architecture</h1>
|
|
<p><cite><a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">Architecture of the World Wide Web, Volume One</a><br />
|
|
W3C Recommendation 15 December 2004</cite></p>
|
|
|
|
<ul>
|
|
<li> Identify with URIs</li>
|
|
<li> Safe retrieval</li>
|
|
<li> Generic URIs</li>
|
|
<li> QName Mapping</li>
|
|
</ul>
|
|
<p class="spkr">These are the <em>minimally constraining</em> design guidelines that allowed the Web to spread the way it did: a little a time, with each new bit benefitting from the rest of the Web.</p>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Observations about People and Technology</h1>
|
|
</div>
|
|
|
|
<div class="slide"><h1>The Evolutionary Cycle</h1>
|
|
<img align="right" src="http://www.w3.org/2005/Talks/0413-sb-w3cpsu/Globe.png" alt="cycle diagram" />
|
|
<!-- based on diagram from woods meeting: http://www.w3.org/Team/1999/10/04-w3m-photos http://www.w3.org/Team/1999/10/04-w3m950 -->
|
|
<ul>
|
|
<li> Research</li>
|
|
<li> Prototyping</li>
|
|
<li> Standardization</li>
|
|
<li> Deployment</li>
|
|
</ul>
|
|
|
|
</div>
|
|
|
|
<div class="slide"><h1>Community Scale</h1>
|
|
<ul>
|
|
<li> design by 1 or 2 or a few</li>
|
|
<li> development by a dozen or so</li>
|
|
<li> review by a few hundred</li>
|
|
<li> early adoption by communities of various sizes**</li>
|
|
<li> global consensus</li>
|
|
</ul>
|
|
<!-- obvious diagram: concentric circles -->
|
|
</div>
|
|
|
|
<div class="slide"><h1>Nuts and Bolts</h1>
|
|
<blockquote><q>I'm just a bill...</q></blockquote>
|
|
<ul>
|
|
<li> Semi-formal preparation</li>
|
|
<li> Activity Creation/Modification (W3C Decision)</li>
|
|
<li> Working Group, toward Last Call</li>
|
|
<li>Last Call</li>
|
|
<li> Candidate Recommendation</li>
|
|
<li> Proposed Recommendation</li>
|
|
<li> Recommendation</li>
|
|
</ul>
|
|
<p class="spkr">Process is based on experience. For each rule in the process, I could probably tell you a story of what happened before that rule was there. e.g. 8 week notice for meetings is based on 4 weeks to find the relevant people in an organization and 4 weeks to buy an advance ticket.</p>
|
|
<p><em>See also: <a href="http://www.w3.org/2001/02pd/rec54-img.png">process diagram</a>.</em></p>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Semi-formal preparation</h1>
|
|
<ul>
|
|
<li> Submissions</li>
|
|
<li> W3C Workshops (you are here)</li>
|
|
<li> Interest Groups</li>
|
|
<li> Mailing Lists</li>
|
|
<li> Academic, Industry Conferences</li>
|
|
</ul>
|
|
</div>
|
|
<div class="slide"><h1>Activity Creation/Modification (W3C Decision)</h1>
|
|
<ul>
|
|
<li> Activity Proposal from Director/Team to Membership</li>
|
|
<li> Membership responds with advice</li>
|
|
<li> Director announces Decision, allocating resources (or not)
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Activity Proposal from Director/Team to Membership</h1>
|
|
<ul>
|
|
<li> Context
|
|
<ul>
|
|
<li> research, industry, market status</li>
|
|
<li> existing W3C members? new members?</li>
|
|
<li> related efforts elsewhere?</li>
|
|
<li> why here at W3C? Why now?</li>
|
|
</ul>
|
|
</li>
|
|
<li> Proposal, Resources
|
|
<ul>
|
|
<li> structure: Working Groups, Interest Groups, scope </li>
|
|
<li> resources: team contacts, travel, communications, systems</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
<div class="slide"><h1>Membership responds with advice</h1>
|
|
<ul>
|
|
<li> each member responds thru its Advisory Committee Representative</li>
|
|
<li> advice may be shared with other members or sent only to The Director (and team)</li>
|
|
</ul>
|
|
</div>
|
|
<div class="slide"><h1>Director announces Decision, allocating resources (or not)</h1>
|
|
<ul>
|
|
<li> should be made by consensus; establishes mandate
|
|
<ul>
|
|
<li> may proceed despite objections, provided justification is given</li>
|
|
</ul>
|
|
</li>
|
|
<li> may incorporate suggested changes</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Working Group, toward Last Call</h1>
|
|
<ul>
|
|
<li> mechanics/infrustructure, norms
|
|
<ul>
|
|
<li> mailing lists</li>
|
|
<li> teleconferences</li>
|
|
<li> face-to-face meetings</li>
|
|
<li> IRC</li>
|
|
<li> shared web space
|
|
<ul>
|
|
<li> Internal Drafts</li>
|
|
<li> Issues list</li>
|
|
<li> Test suite</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li> regular publication</li>
|
|
<li> engage peer groups**
|
|
<ul>
|
|
<li> if you go into the scope of group X, you owe them the right of review</li>
|
|
<li> e.g. Web Architecture, XML</li>
|
|
<li> integrated Internationalization, Accessibility review</li>
|
|
</ul>
|
|
</li>
|
|
<li> best-effort response to community review</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Story Telling and Test Cases</h1>
|
|
|
|
<ul>
|
|
<li>Story telling (aka Use Cases, Requirements)
|
|
<p><em>goal: Stories that scope the problem and make sense to both users and developers</em></p>
|
|
</li>
|
|
<li>Test Cases, Examples</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Last Call</h1>
|
|
<ul>
|
|
<li> starts with WG decision that all issues are addressed</li>
|
|
<li> formally document that all dependencies are discharged</li>
|
|
<li> formally address all issues raised</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Candidate Recommendation</h1>
|
|
<ul>
|
|
<li> starts with Director's Decision that Last Call achieved sufficient review, consensus, etc.</li>
|
|
<li> formally document that all features are implemented</li>
|
|
<li> exit criteria, e.g.
|
|
<ul>
|
|
<li> each feature, issue should have a test</li>
|
|
<li> two implementations should pass all tests</li>
|
|
</ul>
|
|
</li>
|
|
<li> formally address all issues</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Proposed Recommendation</h1>
|
|
<ul>
|
|
<li> seek official endorsement from W3C membership</li>
|
|
<li> formally address all issues</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="slide"><h1>Recommendation</h1>
|
|
<ul>
|
|
<li> press release, party, ...</li>
|
|
<li> errata, maintenance</li>
|
|
<li> what comes next? start the cycle again...</li>
|
|
</ul>
|
|
</div>
|
|
|
|
</body>
|
|
</html>
|