w3c_cheatsheet_for_developers.html 25.5 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='' />
    <meta name="description" content="Yesterday, as part of the W3C Technical Plenary day, I got the opportunity to introduce a new tool that I had been working on over the past few weeks, the W3C Cheatsheet for Web developers. This cheatsheet aims at providing..." />
    <meta name="revision" content="$Id: w3c_cheatsheet_for_developers.html,v 1.75 2011/12/05 17:18:28 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>W3C Cheatsheet for developers - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2009/10/w3c_developer_gathering_next_w.html" title="W3C Developer Gathering Next Week; Registration Closes Today" />
   <link rel="next" href="http://www.w3.org/QA/2009/11/broadening_the_w3c_community.html" title="W3C community bridges unicorns and werewolves #tpac09" />

   <!--
<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/2009/11/w3c_cheatsheet_for_developers.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/291"
    dc:title="W3C Cheatsheet for developers"
    dc:identifier="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html"
    dc:subject="Mobile"
    dc:description="Yesterday, as part of the W3C Technical Plenary day, I got the opportunity to introduce a new tool that I had been working on over the past few weeks, the W3C Cheatsheet for Web developers. This cheatsheet aims at providing..."
    dc:creator="Dominique Hazaël-Massieux"
    dc:date="2009-11-05T21:47:15+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/2009/10/w3c_developer_gathering_next_w.html">&laquo; W3C Developer Gathering Next Week; Registration Closes Today</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2009/11/broadening_the_w3c_community.html">W3C community bridges unicorns and werewolves #tpac09 &raquo;</a>
                     </p>

                        <h2 class="entry-header">W3C Cheatsheet for developers</h2>
                           <div class="entry-body">
                              <p>Yesterday, as part of the <a href="http://www.w3.org/2009/11/TPAC/PlenaryAgenda">W3C Technical Plenary day</a>, I got the opportunity to introduce a new tool that I had been working on over the past few weeks, the <a href="http://www.w3.org/2009/cheatsheet/">W3C Cheatsheet for Web developers</a>.</p>
<p style='float:left;padding:0.5em;'><img src='/2009/11/cheatsheet-screenshot' width='318' height='228' alt='Screenshot of the W3C Cheatsheet on a phone' /></p>
<p>This cheatsheet aims at providing in a very compact and mobile-friendly format a compilation of useful knowledge extracted from W3C specifications — at this time, CSS, HTML, SVG and XPath —, completed by summaries of guidelines developed at W3C, in particular the WCAG2 accessibility guidelines, the Mobile Web Best Practices, and a number of internationalization tips.</p>
<p>Its main feature is a lookup search box, where one can start typing a keyword and get a list of matching properties/elements/attributes/functions in the above-mentioned specifications, and further details on those when selecting the one of interest.</p>
<p>The early feedback received both from TPAC participants after the demo and from the microblogging community has been really positive and makes me optimistic that this tool is filling a useful role.</p>

<p>This is very much a first release, and there are many aspects that will likely need improvements over time, in particular:</p>
<ul>
<li>I would like the cheatsheet to cover more content — from specifications not yet released as standards as well as from topics not yet covered (e.g. JavaScript interfaces),</li>
<li>some people have reported that there might be accessibility problems with the current interface, that I’m eager to fix once I get specific bug reports,</li>
<li>the cheatsheet doesn’t work in IE6 (and probably even in later versions), and it would be nice to make it work at least somewhat there.</li>
</ul>
<p>The <a href="http://dev.w3.org/cvsweb/2009/cheatsheet/index.html">code behind the cheatsheet</a> is already publicly available, and I’m hoping others will be interested to join me in developing this tool — I’m fully aware that the first thing that will need to get others involved will be some documentation on the architecture and data formats used in the cheatsheet, and I’m thus hoping to work on that in the upcoming few weeks.</p>
<p>In the meantime, I very much welcome bug reports and suggestions for improvements, either by private email to me (<a href="mailto:dom@w3.org">dom@w3.org</a>) or preferably to the <a href="http://lists.w3.org/Archives/Public/public-qa-dev/">publicly archived</a> mailing list <a href="mailto:public-qa-dev@w3.org">public-qa-dev@w3.org</a>.</p>
                           </div>
                           <div id="more" class="entry-more">

                           </div>
                       <p class="postinfo">Filed by <a href="http://www.w3.org/People/Dom/">Dominique Hazaël-Massieux</a> on November  5, 2009  9:47 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/css/">CSS</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/internationalization/">Internationalization</a>, <a href="http://www.w3.org/QA/archive/technology/mobile/">Mobile</a>, <a href="http://www.w3.org/QA/archive/technology/svg/">SVG</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/tools/">Tools</a>, <a href="http://www.w3.org/QA/archive/web_spotting/tutorials/">Tutorials</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html#comments">Comments (22)</a>
                                 | <a href="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-184771">
<p class="comment-meta" id="c184771">
<span class="comment-meta-author"><strong>Cameron McCormack </strong></span>
<span class="comment-meta-date"><a href="#c184771">#</a> 2009-11-05</span>
</p>
<div class="comment-bulk">
<p>Nice!  I found it pretty useful for looking up XPath 2.0 function prototypes.</p>

<p>Can you add keywords for SVG 1.1 elements/attributes/properties that aren't in 1.2T?</p>

</div>
</div>


<div class="comment" id="comment-184773">
<p class="comment-meta" id="c184773">
<span class="comment-meta-author"><strong>Alex Media </strong></span>
<span class="comment-meta-date"><a href="#c184773">#</a> 2009-11-06</span>
</p>
<div class="comment-bulk">
<p>It would be nice if you added a iPhone bookmark icon :)</p>

<p>Great tool too!!</p>

</div>
</div>


<div class="comment" id="comment-184774">
<p class="comment-meta" id="c184774">
<span class="comment-meta-author"><strong>Spike </strong></span>
<span class="comment-meta-date"><a href="#c184774">#</a> 2009-11-06</span>
</p>
<div class="comment-bulk">
<p>Urm - <a href="http://validator.w3.org/check?verbose=1&amp;uri=http%3A%2F%2Fwww.w3.org%2FQA%2F2009%2F11%2Fw3c" rel="nofollow">http://validator.w3.org/check?verbose=1&amp;uri=http%3A%2F%2Fwww.w3.org%2FQA%2F2009%2F11%2Fw3c</a><em>cheatsheet</em>for_developers.html - "1591 Errors, 1583 warning(s)"?</p>

<p>Or am I missing something?</p>

</div>
</div>


<div class="comment" id="comment-184810">
<p class="comment-meta" id="c184810">
<span class="comment-meta-author"><strong>Sean </strong></span>
<span class="comment-meta-date"><a href="#c184810">#</a> 2009-11-08</span>
</p>
<div class="comment-bulk">
<p>Great, looks like a big help. </p>

</div>
</div>


<div class="comment" id="comment-184815">
<p class="comment-meta" id="c184815">
<span class="comment-meta-author"><strong>John </strong></span>
<span class="comment-meta-date"><a href="#c184815">#</a> 2009-11-08</span>
</p>
<div class="comment-bulk">
<p>It says </p>

<blockquote><p> >>>>>> 1.21 ======= >>>>>> 1.21 ======= >>>>>> 1.25 ======= >>>>>>> 1.21 ======= >>>>>> 1.24 ======= >>>>>>> 1.24 >>>>>>> 1.25 ======= >>>>>> 1.21 >>>>>>> 1.22 >>>>>>> 1.23 </p>
</blockquote>

<p>above the header. I dont think it should be there.</p>

</div>
</div>


<div class="comment" id="comment-184837">
<p class="comment-meta" id="c184837">
<span class="comment-meta-author"><strong>Dom </strong></span>
<span class="comment-meta-date"><a href="#c184837">#</a> 2009-11-09</span>
</p>
<div class="comment-bulk">
<p>The cheatsheet now works at least somewhat in Internet Explorer; the problem came from training commas in the JSON data, à la {foo:"bar",baz:"quuz"<strong>,</strong>}</p>

</div>
</div>


<div class="comment" id="comment-184852">
<p class="comment-meta" id="c184852">
<span class="comment-meta-author"><strong>Jordan Clark </strong></span>
<span class="comment-meta-date"><a href="#c184852">#</a> 2009-11-10</span>
</p>
<div class="comment-bulk">
<p>What a handy little tool! I've always been a fan of your <a href="http://www.w3.org/2003/12/semantic-extractor.html" rel="nofollow">Semantic Data Extractor</a> &ndash; thanks once again for providing another excellent tool to make my life easier, Dom!</p>

<p>Regards,</p>

<p>Jordan Clark</p>

</div>
</div>


<div class="comment" id="comment-184957">
<p class="comment-meta" id="c184957">
<span class="comment-meta-author"><strong>kunter ilalan </strong></span>
<span class="comment-meta-date"><a href="#c184957">#</a> 2009-11-17</span>
</p>
<div class="comment-bulk">
<p>I have just Twitted this: "Definitely a starter page, not another bookmark for web developers: <a href="http://www.w3.org/2009/chea..." rel="nofollow">http://www.w3.org/2009/chea...</a> #html #css #mobile #accessibility #I18"</p>

<p>Besides, the same here - about Jordan Clark's phrases on Semantic Data Extractor.
Congratulations for the effort; everything seems to be working perfectly.</p>

<p>Regards;
Kunter Ilalan</p>

</div>
</div>


<div class="comment" id="comment-185023">
<p class="comment-meta" id="c185023">
<span class="comment-meta-author"><strong>UDL Intermedia Group </strong></span>
<span class="comment-meta-date"><a href="#c185023">#</a> 2009-11-19</span>
</p>
<div class="comment-bulk">
<p>Great, looks like a big help.
UDL Intermedia</p>

</div>
</div>


<div class="comment" id="comment-185179">
<p class="comment-meta" id="c185179">
<span class="comment-meta-author"><strong>Julie Labrouste </strong></span>
<span class="comment-meta-date"><a href="#c185179">#</a> 2009-12-02</span>
</p>
<div class="comment-bulk">
<p>Via VB client-side script on an ASP.NET WebForm, I'm trying to make a , which becomes, I assume, a , visible or invisible based on other form controls. I am able, for example, to set the innerHTML of such a cell like so:</p>

<p>document.getElementById("tbcP1d1").innerHTML = "whatever"</p>

<p>The above works great on client-side, which I'm placing indirectly into an OnBlur event. However, I want to be able to render the same tablecell (or a tablerow if that's the only way, or a table for that matter) visible or invisible.</p>

<p>Practical Questions:</p>

<ol>
<li><p>Is there an attribute like visible that I can use?</p></li>
<li><p>If so, what is the name for this most-basic-of attributes?</p></li>
<li><p>If not, is there some code somewhere that accomplishes this seemingly simple task? No, I don't want to do it server-side thank-you anyway; it must be client-side.</p></li>
</ol>

<p>Academic Questions:</p>

<ol>
<li><p>If not, why not? Why would something so basic be left-out?</p></li>
<li><p>Why are the names of these attributes not uniform? For example, there is the well-known, "enabled," attribute, but also the, "disabled," attribute. Or is that just a fight between HTML and Microsoft?</p></li>
<li><p>Why are some names so bizarre? For example, who came up with the galactically absurd name for the lost focus event, "OnBlur"? On BLUR? What does the word BLUR have to do with loosing focus in even the most remote way? Some time ago, I spent a considerable amount of time trying to find the lost focus event on client-side. I kept seeing OnBlur and thought that this couldn't possibly be the name that very intelligent people came-up-with and so I disregarded it until I finally got desperate and said, "Oh what the hell. I'll try this funky OnBlur event. If nothing else, I'll discover how to make a control blur." It worked of course; surprise! Ever thought of changing, "Focus," to, oh I don't know, how about the clearly intuative, "KANGAROO"?</p></li>
<li><p>I've used all sorts of Internet means to comment on things, ask questions, polite and otherwise, and I've yet to find any that actually respond, or, are in any way, helpful. Most of the time, there is never any reply at all, which makes me feel that leaving comments on any of these technical sites is like leaving a baby in a dumpster. The rest of the time the replies are very often ridiculously complicated, even when the question is, or seems to be, an extremely simple matter (like my main question here), or insultingly stupid, like, "Is the power on for your computer?" I get better answers on WorldofWarcraft forms for God sake. On the off-chance that somebody does reply to this comment, is this a good place and if not, do you know one of a FREE site (and one that doesn't insist on getting your entire life's history just to ask a question) that replies with useful information and if so, what is the URL?</p></li>
</ol>

<p>If I sound bitter, I am. The people who come up with this stuff are all believed to be smart and for 25+ years now, I keep seeing evidence to the contrary in things like the ONBLUR event.</p>

<p>Julie Labrouste
On Facebook and
julielabrouste@yahoo.com</p>

</div>
</div>


<div class="comment" id="comment-185185">
<p class="comment-meta" id="c185185">
<span class="comment-meta-author"><strong>Dom </strong></span>
<span class="comment-meta-date"><a href="#c185185">#</a> 2009-12-03</span>
</p>
<div class="comment-bulk">
<p>Hi Julie,</p>

<p>You can make an HTML element invisible using style properties, e.g. document.getElementById("tbcP1d1").style.display='none' — I assume this works in VBscript, this is how it would be written in JavaScript at least.</p>

<p>That said, I don’t think this blog is the right place to ask specific technical questions on how to write scripts.</p>

</div>
</div>


<div class="comment" id="comment-185287">
<p class="comment-meta" id="c185287">
<span class="comment-meta-author"><strong>swati </strong></span>
<span class="comment-meta-date"><a href="#c185287">#</a> 2009-12-10</span>
</p>
<div class="comment-bulk">
<p>•I would like the cheatsheet to cover more content — from specifications not yet released as standards as well as from topics not yet covered.
IT solution</p>

</div>
</div>


<div class="comment" id="comment-185969">
<p class="comment-meta" id="c185969">
<span class="comment-meta-author"><strong>Günther </strong></span>
<span class="comment-meta-date"><a href="#c185969">#</a> 2010-01-07</span>
</p>
<div class="comment-bulk">
<p>Your site and the tools are really great and a very big help for webmasters. Keep up the good and thank you ...<a>Rss News</a></p>

</div>
</div>


<div class="comment" id="comment-186074">
<p class="comment-meta" id="c186074">
<span class="comment-meta-author"><strong>Tom </strong></span>
<span class="comment-meta-date"><a href="#c186074">#</a> 2010-01-11</span>
</p>
<div class="comment-bulk">
<p>I just the tool has tried out. <br />
For webmaster it is a real relief and help.
Thank you Tommy of IT Service</p>

</div>
</div>


<div class="comment" id="comment-186147">
<p class="comment-meta" id="c186147">
<span class="comment-meta-author"><strong>Ranjit </strong></span>
<span class="comment-meta-date"><a href="#c186147">#</a> 2010-01-15</span>
</p>
<div class="comment-bulk">
<p>The post was of great help. <a>Ranjit Behera</a></p>

</div>
</div>


<div class="comment" id="comment-186174">
<p class="comment-meta" id="c186174">
<span class="comment-meta-author"><strong>phpLD Germany </strong></span>
<span class="comment-meta-date"><a href="#c186174">#</a> 2010-01-16</span>
</p>
<div class="comment-bulk">
<p>I LOVE W3C.ORG :-)
I use the tools daily and i have learned very much thanks to the W3C team.
Thank you phpLD Germany</p>

</div>
</div>


<div class="comment" id="comment-186187">
<p class="comment-meta" id="c186187">
<span class="comment-meta-author"><strong>enderandpeter </strong></span>
<span class="comment-meta-date"><a href="#c186187">#</a> 2010-01-17</span>
</p>
<div class="comment-bulk">
<p>Thanks for making such an awesome tool! And the articles you link to are simply invaluable!</p>

<p>I must truly and sincerely thank you for bringing my attention to the html codes for the right and left double quotes and the em and en dashes. I'll be more vigilant in my use of them.</p>

<p>I was wondering, though. It's come to my attention that &#8216; (or &lsquo;) is used as a single left quotation mark while &#8217; (or &rsquo;) is used as a right quotation mark, which you have listed as an apostrophe. It actually seems that it's ideal as an apostrophe, because most browsers, if not all of them, render it bolder than the left single quote.</p>

<p>Does anyone happen to know if there is a less bold single right quotation mark / apostrophe or a bolder left single quote mark? I've been using the two single quote codes I mentioned on <a href="http://aninternetpresence.net" rel="nofollow">my blog</a> (specifically in the third entry), and the lighter and darker quotes look kind of neat, but it would be nice to conform how they look a little more.</p>

<p>Once again, thanks for making such a useful web app!</p>

</div>
</div>


<div class="comment" id="comment-186285">
<p class="comment-meta" id="c186285">
<span class="comment-meta-author"><strong>Manfred Carsten </strong></span>
<span class="comment-meta-date"><a href="#c186285">#</a> 2010-01-22</span>
</p>
<div class="comment-bulk">
<p>Hi! Now after I tried this tool, I often use it and I find it very useful! Thanks for developing it! Greetings, Fred. </p>

</div>
</div>


<div class="comment" id="comment-186376">
<p class="comment-meta" id="c186376">
<span class="comment-meta-author"><strong>enderandpeter </strong></span>
<span class="comment-meta-date"><a href="#c186376">#</a> 2010-01-26</span>
</p>
<div class="comment-bulk">
<p>Well, it's come to my attention that different fonts will give you different double and single quotes, some of which give you perfect symmetry, as my previous post shows.</p>

</div>
</div>


<div class="comment" id="comment-186474">
<p class="comment-meta" id="c186474">
<span class="comment-meta-author"><strong>David </strong></span>
<span class="comment-meta-date"><a href="#c186474">#</a> 2010-01-29</span>
</p>
<div class="comment-bulk">
<p>Many thanks for the cheatsheet. I always refer to these when I'm developing a site since it's often easy to overlook simple design features and usability that in the end will contribute towards a more usable site. Although the cheatsheet does not work in IE6 it's fair to say that IE6 is a challenging browser to develop for anyway! </p>

</div>
</div>


<div class="comment" id="comment-198707">
<p class="comment-meta" id="c198707">
<span class="comment-meta-author"><strong>SalmanAbbas007 </strong></span>
<span class="comment-meta-date"><a href="#c198707">#</a> 2010-08-19</span>
</p>
<div class="comment-bulk">
<p>Where the HELL is Border-Radius?? :S</p>

</div>
</div>


<div class="comment" id="comment-198882">
<p class="comment-meta" id="c198882">
<span class="comment-meta-author"><strong>Dom </strong></span>
<span class="comment-meta-date"><a href="#c198882">#</a> 2010-08-23</span>
</p>
<div class="comment-bulk">
<p>@SalmanAbbas007  border-radius is part of CSS3, which hasn't been integrated in the cheatsheet yet (but probably will in a future release)</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="8652" />
<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:28 $</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>