the_core_mission_of_w3c.html 13.3 KB

Raw Blame History Permalink

<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <style type="text/css" media="all">
    @import "/QA/2006/01/blogstyle.css";
    </style>
    <meta name="keywords" content='Core Mission' />
    <meta name="description" content=" New July 9, 2010 I reported in The Mission of W3C that a major focus of W3C is to Strengthen our core mission. This blog entry elaborates. Broad and / or deep Since the Web is central to everything..." />
    <meta name="revision" content="$Id: the_core_mission_of_w3c.html,v 1.27 2011/12/15 23:20:59 mirror Exp $" />
   <link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
   <link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />
   <title>The Core Mission of W3C - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2010/07/making_w3c_the_place_for_new_s.html" title="Making W3C the Place for New Standards - The Survey!" />
   <link rel="next" href="http://www.w3.org/QA/2010/07/html5_in_w3c_cheatsheet.html" title="HTML5 in W3C Cheatsheet" />

   <!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
         xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
    rdf:about="http://www.w3.org/QA/2010/07/the_core_mission_of_w3c.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/343"
    dc:title="The Core Mission of W3C"
    dc:identifier="http://www.w3.org/QA/2010/07/the_core_mission_of_w3c.html"
    dc:subject="Technology"
    dc:description=" New July 9, 2010 I reported in The Mission of W3C that a major focus of W3C is to Strengthen our core mission. This blog entry elaborates. Broad and / or deep Since the Web is central to everything..."
    dc:creator="Jeff Jaffe"
    dc:date="2010-07-16T18:14:24+00:00" />
</rdf:RDF>
-->

    <!-- <script type="text/javascript" src="http://www.w3.org/QA/mt.js"></script>-->

</head>
<body class="layout-one-column">
      <div id="banner">
      <h1 id="title">
	<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog
</h1>
    </div>

    <ul class="navbar" id="menu">
        <li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
        <li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
        <li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
        <li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
    </ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>


    <div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->

                     <p class="content-nav">
                        <a href="http://www.w3.org/QA/2010/07/making_w3c_the_place_for_new_s.html">&laquo; Making W3C the Place for New Standards - The Survey!</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2010/07/html5_in_w3c_cheatsheet.html">HTML5 in W3C Cheatsheet &raquo;</a>
                     </p>

                        <h2 class="entry-header">The Core Mission of W3C</h2>
                           <div class="entry-body">
                              <?xml version="1.0" encoding="iso-8859-1"?>
<!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>
  <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
  <title>New</title>
  <meta name="generator" content="Amaya, see http://www.w3.org/Amaya/" />
</head>

<body>

<p></p>

<p>July 9, 2010</p>

<p></p>

<p>I reported in <a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html">The Mission of W3C</a> that a
major focus of W3C is to Strengthen our core mission. This blog entry
elaborates.</p>

<p></p>

<em><h2>Broad and / or deep</h2></em>

<p></p>

<p>Since the Web is central to everything (see also
<a href="http://www.w3.org/QA/2010/05/the_expanding_web_platform.html">The Expanding Web Platform</a>), it is not too
surprising that we get involved in standardizing numerous aspects of Web
infrastructure. Today we have over 70 groups that are providing standards in
diverse areas. Evidently, some of these groups have greater impact on the
utility of the Web than others. Also, some of them are more
advanced/complex/difficult than others. If we apply an equal amount of effort
to each working group, we will sub-optimize the Web by not applying sufficient
resource on those that are most crucial. So we prioritize.</p>

<p></p>

<p>Every time we make an incremental change in our effort &ndash; such as when
we start a new working group or expand the scope of requirements &ndash; we are
making an incremental prioritization decision. In our &ldquo;core mission task
force&rdquo; we are taking a step back and looking at the ensemble of our
activity. Do we know which small number of the 70 groups are the most
important? Are we applying sufficient resource and attention to them to
guarantee the greatest possible success?</p>

<p></p>

<em><h2>What does it mean if a Standards Working Group is Core (or not Core) to
W3C</h2></em>

<p></p>

<p>As our task force characterizes projects into core and non-core, one might
ask what difference it makes.</p>

<p></p>

<p>There are many reasons that a non-core standard might have migrated to W3C.
Some of them are:</p>

<p></p>

<ul>
	<li><p>The standard is a natural adjacency of a core standard</p></li>
	<li><p>W3C houses a team who are knowledgeable technologists who can best shepherd the standard</li>
	<li><p>The standard is a candidate to be core in the future</p></li>
</ul>
<p></p>

<p>&hellip; among other reasons. These are actually sensible reasons. So we
will absolutely continue to serve the industry and convene those standards
groups.</p>

<p></p>

<p>But for core standards we must have a higher target of quality. It is not
sufficient to work with the industry to create the standard. We must assure
quality of the standard, develop it on schedule, help make sure that it has the
right feature set, work on testing strategies, provide training, and help
people appreciate the value. Our core mission task force might not change the
list of working groups. But it will change emphasis. For items in core, we will
provide supreme effort to ensure quality, the right feature set, timeliness,
and market support.</p>

<p></p>

<em><h2>HTML5</h2></em>

<p></p>

<p>Last month I spent a week in Silicon Valley. The importance of giving top
attention to core was re-inforced.</p>

<p></p>

<p>Our largest working group is the HTML5 working group. Literally hundreds of
people participate in the W3C HTML5 working group.</p>

<p></p>

<p>Many of them work in Silicon Valley. So I met with many of them. They come
from a cross-section of companies: browser vendors, web publishers, tools
providers, application vendors, security firms.</p>

<p></p>

<p>Since HTML5 is core, it is important that we as a community get it
&ldquo;right&rdquo;. Since it is central to the next generation web, it evokes
strong opinions about what it means to &ldquo;get it right&rdquo;. And as I
listened to the opinions they are all well reasoned and based on knowledgeable
and sensible views of how the future web will evolve.</p>

<p></p>

<p>While they are all reasoned, knowledgeable, and sensible &ndash; that does
not mean that everyone agrees. Not at all! Nor should we expect agreement for
something so central &ndash; given that different organizations have different
priorities.</p>

<p></p>

<p>Therein, lies W3C's imperative to provide the right amount of attention to
strengthen our core. We bring diverse stakeholders to the table and create the
environment for the industry to agree on this critical standard. There is still
more work to be done. There are technical issues, testing issues, and
disagreements that need to be resolved. It is our commitment to work with all
stakeholders to drive this forward in a professional way, and ensure that we
have the right feature set, quality, timeliness, and market support.</p>
</body>
</html>
                           </div>
                           <div id="more" class="entry-more">

                           </div>
                       <p class="postinfo">Filed by <a href="">Jeff Jaffe</a> on July 16, 2010  6:14 PM in <a href="http://www.w3.org/QA/archive/w3cqa_news/ceo/">CEO</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/07/the_core_mission_of_w3c.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2010/07/the_core_mission_of_w3c.html#comments">Comments (0)</a>
                                 | <a href="http://www.w3.org/QA/2010/07/the_core_mission_of_w3c.html#trackback">TrackBacks (0)</a>
</p>


  <div class="comments-open" id="comments-open">
<h3 class="comments-open-header">Leave a comment</h3>

<div class="comments-open-moderated">
   <p>
   Note: this blog is intended to foster <strong>polite
   on-topic discussions</strong>. Comments failing these
   requirements and spam will not get published. Please,
   enter your real name and email address. Every
   individual comment is reviewed by the W3C staff.
   This may take some time, thank you for your patience.
   </p>
   <p>
   You can use the following HTML markup (a href, b, i,
   br/, p, strong, em, ul, ol, li, blockquote, pre)
   and/or <a href="http://daringfireball.net/projects/markdown/syntax">Markdown syntax</a>.</p>
</div>

<div id="comments-open-data">
<form method="post" action="http://www.w3.org/QA/sununga/beach.pl" id="comments-form">
<h4>Your comment</h4>
<div id="comments-open-text">
  <textarea id="comment-text" name="text" rows="20" cols="100"></textarea><br />
<label for="comment-text">Write your comment text here. Remember, keep the discussion on topic and courteous.</label>
</div>

<h4>About you</h4>
<div id="comment-form-name">
  <input type="hidden" name="static" value="1" />
<input type="hidden" name="entry_id" value="8857" />
<input type="hidden" name="__lang" value="en" />
<label for="comment-author">Your Name</label>
<input id="comment-author" name="author" size="30" value="" />
</div>
<div id="comment-form-email">
<label for="comment-email">Your Email Address</label>
<input id="comment-email" name="email" size="30" value="" />
</div>

<div id="comments-open-footer">
<input type="submit" accesskey="s" name="post" id="comment-submit" value="Submit" />

</div>
</form>
</div>
</div>


<p id="gentime">This page was last generated on $Date: 2011/12/15 23:20:59 $</p>

      </div><!-- End of "main" DIV. -->

<address>

This blog is written by W3C staff and working group participants,<br />
&nbsp;and maintained by <a href="/People/CMercier/">Coralie Mercier</a>.<br />
Authorized parties may <a href="/QA/new">log in</a> to create a new entry.<br/>
<span id="poweredby">Powered by Movable Type, magpierss and a lot of Web Technology</span>
    </address>


    <p class="copyright">
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 1994-2011
      <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>&reg;
      (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
      <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
      <a href="http://www.keio.ac.jp/">Keio</a>),
      All Rights Reserved.
      W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
      <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
      and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
      rules apply. Your interactions with this site are in accordance
      with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
      <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
      statements.
    </p>

  </body>
</html>