html5_the_jewel_in_the_open_we.html 17.9 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='html5' />
    <meta name="description" content="The Open Web Platform to us is HTML5, a game-changing suite
of tools that incorporates SVG, CSS and other standards that are in
various stages of development and implementation by the community at
W3C. At this stage community feedback plays an important role in ensuring that
the HTML5 specification is the highest quality." />
    <meta name="revision" content="$Id: html5_the_jewel_in_the_open_we.html,v 1.20 2011/12/05 17:18:31 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>HTML5: The jewel in the Open Web Platform - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2010/10/introducing_the_web_font_award.html" title="Introducing the Web Font Awards" />
   <link rel="next" href="http://www.w3.org/QA/2010/10/css_wg_specs.html" title="CSS WG specs" />

   <!--
<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/10/html5_the_jewel_in_the_open_we.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/356"
    dc:title="HTML5: The jewel in the Open Web Platform"
    dc:identifier="http://www.w3.org/QA/2010/10/html5_the_jewel_in_the_open_we.html"
    dc:subject="HTML"
    dc:description="The Open Web Platform to us is HTML5, a game-changing suite
of tools that incorporates SVG, CSS and other standards that are in
various stages of development and implementation by the community at
W3C. At this stage community feedback plays an important role in ensuring that
the HTML5 specification is the highest quality."
    dc:creator="Philippe Le Hégaret"
    dc:date="2010-10-08T20:22:16+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/10/introducing_the_web_font_award.html">&laquo; Introducing the Web Font Awards</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2010/10/css_wg_specs.html">CSS WG specs &raquo;</a>
                     </p>

                        <h2 class="entry-header">HTML5: The jewel in the Open Web Platform</h2>
                           <div class="entry-body">
                              <p>
Over the past two weeks, I traveled across the U.S. from New York to
San Francisco to talk about HTML5 with developers and W3C member
organizations. This continues my global tour which has also taken me
earlier to France and Japan. I am inspired by the enthusiasm for the
suite of technical standards that make up what W3C calls the 'Open Web
Platform.' The Open Web Platform to us is HTML5, a game-changing suite
of tools that incorporates SVG, CSS and other standards that are in
various stages of development and implementation by the community at
W3C. Recent demos show the potential of certain features of HTML5,
however, the platform in its entirety is still a work in progress. At
this stage, community feedback plays an important role in ensuring that
the HTML5 specification is the highest quality.
</p>
<p>
The power of this platform is that it is so comprehensive. The
challenge presented by HTML5, which I mentioned <a href='http://www.w3.org/QA/2010/09/how_do_we_test_a_web_browser_o.html'>a month ago</a>, is the need to test, refine and mature certain aspects of
the specification in order to support the early adopters, the
innovators and the engineers who are embracing this technology today.
</p>
<p>
Recently I wrote about the HTML5 WG's decision to move the HTML5
specification to <a href='http://www.w3.org/QA/2010/09/html5_getting_to_last_call.html'>last call in May of next year</a>. As
a result of this milestone, W3C opened a call to developers to submit
their issues by October 1, in order to speed the process of
standardization and implementation of HTML5 as early as possible. In
addition, because HTML5 is seeing early adoption, there is a need to
refine the draft specification to support the work of those who are
pushing this technology out into the public domain.
</p>
<p>
From week to week, we see promising examples of the potential of HTML5
demonstrated by impressive displays of 3D animation, navigation and
video technologies. There is not a single month when W3C does not
receive a request to extend APIs in order to address new
functionalities. The video community is requesting more features in
our support of HTML5 video (more metadata support, chapters, quality
feedback). The television industry is just starting to think about
having APIs to control television channels or the TV remote. The
electronic book industry would like to have better text support, in
particular vertical text, in CSS. Several companies met this week to
talk about supporting audio and video teleconferencing in HTML (ICE,
STUN, notification API for incoming calls, etc.). Our newly created
Web Performance Working Group had a very fruitful face-to-face this
week, to discuss latency measurements related to user navigation. The
work and the speed of the Working Group is literally a race against
clock, with the plan of finalizing the API in the next 4 to 6 months.
</p>
<p>
The adoption of HTML5 by browser vendors and other members of the IT
community is an important factor in the ongoing traction of the
platform. We want to hear from those already working with the draft
specification so we can use the test cases to identify
interoperability issues that need to be addressed leading up to last
call in May of next year.  It is because of your work and feedback
that W3C can build the solid foundation for the Web's continuing
evolution. Please provide your feedback by using the <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG">HTML5 public bug database</a>.
</p>

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

                           </div>
                       <p class="postinfo">Filed by <a href="http://www.w3.org/People/LeHegaret/">Philippe Le Hégaret</a> on October  8, 2010  8:22 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/10/html5_the_jewel_in_the_open_we.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2010/10/html5_the_jewel_in_the_open_we.html#comments">Comments (3)</a>
                                 | <a href="http://www.w3.org/QA/2010/10/html5_the_jewel_in_the_open_we.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-202623">
<p class="comment-meta" id="c202623">
<span class="comment-meta-author"><strong>jpvincent </strong></span>
<span class="comment-meta-date"><a href="#c202623">#</a> 2010-10-09</span>
</p>
<div class="comment-bulk">
<p>I'm thinking since a while (french post : <a href="http://braincracking.org/2010/01/22/features-html5-appel-aux-armes-pour-les-librairies-js/)" rel="nofollow">http://braincracking.org/2010/01/22/features-html5-appel-aux-armes-pour-les-librairies-js/)</a> that what the webdev's world and the W3C need right now is a JS implementation of the HTML5 APIs, when it's possible (that mean 80% of the spec).
Webdevs are in a production stressful environment : some braves make demos with the new APIs, few of them put them into production and very few of them give feedback to the W3C. Most of them wait for the browsers to implement fully HTML5 and IE8 to disappear ...</p>

<p>so what could speed up most of HTML5 features adoption and provide you more feedback from the tranchees would be a library implementing the API as defined in the current drafts, detecting native browser implementation and fallbacking to what's appropriate (hidden flash pieces most of the time ...)</p>

<p>it's probably rather the community's role to write it rather than the W3C, but for now there is various individual initiative (look at that long libraries list : <a href="http://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-browser-Polyfills)," rel="nofollow">http://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-browser-Polyfills),</a> what the community need is a meta library or project coordinating and regrouping those small specialized libs, to ease the access to other web developers
Maybe the W3 could arrange that ?</p>

</div>
</div>


<div class="comment" id="comment-202962">
<p class="comment-meta" id="c202962">
<span class="comment-meta-author"><strong>风情主人 </strong></span>
<span class="comment-meta-date"><a href="#c202962">#</a> 2010-10-15</span>
</p>
<div class="comment-bulk">
<p>For me personally, I hope the perfect browser with the following features 【hope that we express their views:
Add the following functions aimed at improving the performance of web applications, application development to improve usability and development efficiency
A, JS api
   1, support the Object to the json data format conversion
   2, support Object to the url encoding, conversion (key does not encode, value automatically encoded as follows: in such a way) to support the url decoding format to Object conversion
   3, Ajax Asynchronous further package, able to directly send Object, or the Form object, automatically converted to a form of data format, can support with the submission of documents
   4, support large collection of data sorting, filtering, easy to do large data fast multi-column table sorting, filtering
   5, Array support the iterative and indexOf, filter
   6, from the key --- alue Object quickly fill out the form to the form the form, providing quick transition from the form for the key - value of the Object
Second, HTML dom api and some other
   1, supports XPath, css selector to select the API, and support the iterative
   3, all the form elements to support automatic data capture, auto-complete function, support the development of url parameters to complete the drop-down list automatically capture
   2, support for dates, numbers, period number, ID, zip code, telephone with the power of application development using HTML tags
   3, internal standard html tag down to allow entry of new values should be supported, support for the specified URL from the drop-down list to obtain data to support multi-column display, support for fast positioning and support features such as rapid filtration
   4, more than something to support the container label from the given reference to the specified url in the html id of the element as its content fragments - in particular to support , rather than simply innerhtml
   5, page leaving the page to release all the memory resources, even if it is js and HTML objects that reference each other
   6, all html tags visible support for hide and show the api, and hidden when not in the position occupied by
   7, to provide detailed, based on high-level programming language (eg C) expansion of the new code html tags - that is, the core of the browser frame is a micro-kernel, all the html tags are plug-ins
   8, enhance and simplify the object with the domain of interaction between the function of the window
   9, img directly support binary data, not only to get src
   10, to achieve powerful forms html tags, can refer to the PB in the datawindow, EXCEL, here I am not going to detail the features listed
   11 static resources to support P2P streaming</p>

</div>
</div>


<div class="comment" id="comment-204333">
<p class="comment-meta" id="c204333">
<span class="comment-meta-author"><strong>Christopher Marsh </strong></span>
<span class="comment-meta-date"><a href="#c204333">#</a> 2010-10-27</span>
</p>
<div class="comment-bulk">
<p>I figured out why the private sector is already using HTML5 but not the government/contractor sector. The private sector oftentimes will push the envelope to take advantage of new features. The solution is to get a new browser. Section 508 rules for people with disabilities often do not apply. </p>

<p>However they do in government. Government requires standardization for all Web browsers so everyone can take advantage of technology, especially people with disabilities. Therefore we can't take advantage of HTML5 until it is standardized.</p>

<p>That is why I haven't heard of HTML5 until recently as a Federal contractor. When I was temporarily looking for work I found out this was old news to the private sector.</p>

<p>Christopher Marsh
INDUS Corporation
Vienna, Virginia USA</p>

</div>
</div>


  <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="8924" />
<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/05 17:18:31 $</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>