w3c-open-web-standards.html 12.2 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='open web, social platform, specification, standard, w3c, web standards, working group' />
    <meta name="description" content="Last week in Tokyo, there was the wonderful Web Directions East 2008. It was yet another opportunity to hear and discuss how people feel about W3C open Web standards. Two patterns often arise in these discussions: implementation first and specification first. Both lead to reproaches. What is the role of W3C?" />
    <meta name="revision" content="$Id: w3c-open-web-standards.html,v 1.44 2011/12/16 03:03:09 gerald 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>W3C Open Web Standards - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2008/11/meet-w3c-staff.html" title="Meet W3C Staff version 2008" />
   <link rel="next" href="http://www.w3.org/QA/2008/11/dreamimg_a_new_css_validator.html" title="What would a new CSS validator look like?" />

   <!--
<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/2008/11/w3c-open-web-standards.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/234"
    dc:title="W3C Open Web Standards"
    dc:identifier="http://www.w3.org/QA/2008/11/w3c-open-web-standards.html"
    dc:subject="W3C Life"
    dc:description="Last week in Tokyo, there was the wonderful Web Directions East 2008. It was yet another opportunity to hear and discuss how people feel about W3C open Web standards. Two patterns often arise in these discussions: implementation first and specification first. Both lead to reproaches. What is the role of W3C?"
    dc:creator="Karl Dubost"
    dc:date="2008-11-10T02:32:58+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/2008/11/meet-w3c-staff.html">&laquo; Meet W3C Staff version 2008</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2008/11/dreamimg_a_new_css_validator.html">What would a new CSS validator look like? &raquo;</a>
                     </p>

                        <h2 class="entry-header">W3C Open Web Standards</h2>
                           <div class="entry-body">
                              <p>Last week in Tokyo, there was the wonderful <a href="http://east08.webdirections.org/">Web Directions East 2008</a>. It was yet another opportunity to hear and discuss how people feel about W3C open Web standards. Two patterns often arise in these discussions: implementation first and specification first. Both lead to reproaches.</p>

<h3>Implementations first</h3>

<p>Most of the software companies deploy all kind of technologies in theirs products. They do it to get more market shares. Sometimes the technology is getting traction in the development world. Other companies have a few choices:</p>

<ul>
<li>Implement a competitive technology based on the same principles.</li>
<li>Implement the original vendor specification (against fees or freely depending of the license).</li>
<li>Implement the same set of features by reverse engineering when the vendor specification is not available.</li>
</ul>

<p>All of these solutions have issues ranging to patents, licenses, implementations bugs, interoperability, collective consensus. But fortunately some of them after a while will reach the W3C and get into a Working Draft at least, and hopefully a Recommendation. Canvas (Apple) and XMLHttpRequest (Microsoft) are following this pattern.</p>

<p>In this case, W3C is often perceived (mostly by software implementers) as a slow organization, not being on the edge and not creating innovation. Another part of the community thinks that it is good that W3C has his head on his shoulders and standardized only market proof technologies. Standards mean here stability of the market.</p>

<h3>Specifications first</h3>

<p>A group of companies have an interest in technology. They feel there is a need to develop a market or they have an issue which needs an interoperable technology to bring stability in the market. The W3C Activity and related Working Groups are created. Sometimes they will use the deliverables of an incubator group, of a workshop or even from W3C Member submissions. In the best case, the Working Draft documents are published at a regular pace with the relevant implementers in the Working Group. </p>

<p>It is a long process to reach agreement, to solve the issues. Each working draft is published openly under the patent policy. The public sees all the evolution of the technology, phase that they could not see in the first case. They often draw high expectations, followed by sometimes disappointement to see things being stalled, not going fast enough or not evenly implemented. CSS, XML, SVG are examples of this pattern.</p>

<p>W3C is often perceived not realistic by some Web communities which can't use the technology right away. Somme communities feel that W3C is a leading organization exploring markets and creating the base of a new architecture.
Standards mean here innovation for the market.</p>

<h3>An Open Web Social Platform</h3>

<p>Both cases will bring bad and good karma to W3C. There are more than one community, sometimes they are quite disjoint or with a very different culture, approach with regards to the technology. And honestly, I'm not sure there is one solution that would satisfy everyone. But at least, I know that until now, the W3C Process has been flexible enough to accomodate a lot of different cases and needs. Under the market and the communities needs, the W3C Process has evolved. Remember the patent policy debates for example.</p>

<p>In my 8 years of working here, I come to think that W3C is a <strong>social platform for developing Open Web Standards</strong>.</p>

                           </div>
                           <div id="more" class="entry-more">


                           </div>
                       <p class="postinfo">Filed by <a href="http://www.w3.org/People/karl/">Karl Dubost</a> on November 10, 2008  2:32 AM in <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions &amp;amp; Editorial</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/11/w3c-open-web-standards.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2008/11/w3c-open-web-standards.html#comments">Comments (0)</a>
                                 | <a href="http://www.w3.org/QA/2008/11/w3c-open-web-standards.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="586" />
<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/16 03:03:09 $</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>