html_classes_of_products_and_a.html 14.6 KB
<?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='' />
    <meta name="description" content="Rene Saarsoo has published a survey of Coding practices of Web pages. It contains a lot of very useful information for those who try to understand how the Web is authored in the wild. One of the major concerns of..." />
    <meta name="revision" content="$Id: html_classes_of_products_and_a.html,v 1.103 2011/12/16 02:58:30 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>HTML Classes of Products and Authoring - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2007/07/web_education_survey.html" title="WASP's Education Task Force Curriculum Survey" />
   <link rel="next" href="http://www.w3.org/QA/2007/07/why-html-5-matters.html" title="Why HTML 5 Specification Matters?" />

   <!--
<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/2007/07/html_classes_of_products_and_a.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/64"
    dc:title="HTML Classes of Products and Authoring"
    dc:identifier="http://www.w3.org/QA/2007/07/html_classes_of_products_and_a.html"
    dc:subject="HTML"
    dc:description="Rene Saarsoo has published a survey of Coding practices of Web pages. It contains a lot of very useful information for those who try to understand how the Web is authored in the wild. One of the major concerns of..."
    dc:creator="Karl Dubost"
    dc:date="2007-07-06T01:49:50+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/2007/07/web_education_survey.html">&laquo; WASP's Education Task Force Curriculum Survey</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2007/07/why-html-5-matters.html">Why HTML 5 Specification Matters? &raquo;</a>
                     </p>

                        <h2 class="entry-header">HTML Classes of Products and Authoring</h2>
                           <div class="entry-body">
                              <p><a href="http://triin.net/">Rene Saarsoo</a> has published a survey of <a href="http://triin.net/2006/06/12/Coding_practices_of_web_pages" title="Coding practices of web pages">Coding practices of Web pages</a>. It contains a lot of very useful information for those who try to understand how the Web is authored in the wild. One of the major concerns of HTML WG is to try to design <a href="http://www.w3.org/html/wg/html5/" title="HTML 5 Editor's draft">HTML 5</a> in a way which is mostly compatible with what authors mostly do on the Web.</p>

<p>It is not an easy task. There are different types of authors on the Web, and then different types of requirements for different products. A while ago, I posted on the mailing-list trying to work out some of the <a href="http://lists.w3.org/Archives/Public/public-html/2007May/0009.html" title="HTML classes of products">possible categories of products</a>.</p>

<h3 id="web_author_hand_coding">Web author (hand coding)</h3>

<p>From the point of view of the author, HTML is a set of tags with a
clear defined meaning (ex: &#8216;q&#8217;) or functional semantics (ex: &#8216;a&#8217;).
Sometimes, the definitions given by previous specifications,
books, tutorials, lead to misunderstanding and then the features are not properly used. They are many categories of HTML hand coders with different
capabilities and knowledge. Some of the authors will see it just as a
support for CSS for example and do not care that much about the
meaning. Some will be very precise and be frustrated by the lack of
defined elements.</p>

<h3 id="web_author_wysiwyg">Web author (wysiwyg)</h3>

<p>By far this is the <strong>most common author</strong> on the Web, and basically, they
do not know what HTML is at all. Most of these people use a form
where they put simple text, sometimes enrich with javascript toolbar,
some send html emails, some save their office document as web
document to be loaded by the CMS.</p>

<h3 id="cms_developer_scripting_libraries">CMS developer, scripting libraries.</h3>

<p>HTML is a language that in the best case have some rules of nesting
for tags and help to put content on a web page. It is something to
put bits of content coming from a database on the Web. It is very
rare that the semantics is understood or even care of. It is very
rare to have CMS which puts a quality process in the publishing step.
Their conception is more html fragment than document.</p>

<h3 id="web_authoring_wysiwyg_tool">Web authoring Wysiwyg tool</h3>

<p>HTML is a very difficult thing to implement. The specification in the
past have not been defined for Wysiwyg tools. They had to produce a
document which respects the syntactic rules of the language. But there is no or little guidance on implementing the language at the <acronym title="user interface">UI</acronym> level.
We have a tendency to define, right now, a lot more how to render and
not that much how to create.</p>

<h3 id="web_visual_browser">Web Visual Browser</h3>

<p>From the point of view of a Web visual browser (and then its
developers), it is a blurb of tags, most of the time not written very
well. They <strong>have to parse</strong> HTML, Javascript, CSS rules, plug-ins to give something mostly usable by a random person on the Web.</p>

<h3 id="assist_browser">Assistive Technologies Browser</h3>

<p>They see HTML as a powerful language to give easily access to content
for people who had no access to it in the past. Giving access to a
paper book to someone who is blind has a high cost, it becomes easy
on the Web. Though it is also difficult to implement a useful tool
because not many Web authors and <acronym title="Content Management System">CMS</acronym> care for accessibility. So
people themselves using these browsers fill the gap when they can by
using their own skills and intelligence.</p>

<h3 id="web_search">Web search</h3>

<p>Strange world. It is not a uniform world. They are at least two big
sub-classes:</p>

<h4 id="web_search_services">Web search services (Yahoo!, MS Live, Google and Quaero)</h4>

<p>For those, they need to parse the web content which is not only html
and which is mostly a few tags and a lot of content. They are
interested by <strong>links</strong> and some of the meaningful tags but not that
much.</p>

<h4 id="web_search_engines_ht_dig_nutch_etc">Web search engines (ht://Dig, Nutch, etc.)</h4>

<p>More skilled and more powerful, they are used on corporate, academic,
personal Web sites. They are crafted to index all kind of metadata
and semantics. HTML is a fully meaningful language. It helps users on
the Web to have a more precise answer within the context of a
corporate site. Initiatives like explicit data (RDFa, microformats),
metadata in head, etc. are very important for them. Some of these
engines work on the Desktop and then are a tool for desktop users
(Spotlight (Apple) for example.)</p>

<h3 id="validators_conformance_checker_helping_tools">Validators, Conformance checker, Helping tools</h3>

<p>HTML is a set of rules and definitions, that helps to define if the document is in contradiction with these rules. Some of the rules can be checked easily, can be processed by a machine, some others are a lot more difficult.</p>

<h3 id="other_specifications">Other Specifications</h3>

<p>HTML is a set of rules and syntactic constraints with a defined
semantics that can be used, be encapsulated in another technology.</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 July  6, 2007  1:49 AM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_spotting/reference/">Reference</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/07/html_classes_of_products_and_a.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2007/07/html_classes_of_products_and_a.html#comments">Comments (2)</a>
                                 | <a href="http://www.w3.org/QA/2007/07/html_classes_of_products_and_a.html#trackback">TrackBacks (0)</a>
</p>



<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-53368">
<p class="comment-meta" id="c053368">
<span class="comment-meta-author"><strong>thacker </strong></span>
<span class="comment-meta-date"><a href="#c053368">#</a> 2007-07-06</span>
</p>
<div class="comment-bulk">
<p>Standards, in short, must adapt to the 'Chaos' theory? [rhetorical] Glad I don't have your job. </p>

<p>Further evolution of two standards: HTML [chaos] and XHTML [linear and controlled]?</p>

</div>
</div>


<div class="comment" id="comment-56428">
<p class="comment-meta" id="c056428">
<span class="comment-meta-author"><strong>yogesh </strong></span>
<span class="comment-meta-date"><a href="#c056428">#</a> 2007-07-22</span>
</p>
<div class="comment-bulk">
<p>what is html &amp; what is tag</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="68" />
<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 02:58:30 $</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>