pre-obsolete-design.html 13.1 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='css, implementation, interoperability, specification, standard, w3c' />
    <meta name="description" content="Creating a specification is a challenge and a compromise. Far to be perfect it is an attempt at establishing stability for  a little while. The difficulty is often how long?" />
    <meta name="revision" content="$Id: pre-obsolete-design.html,v 1.40 2011/12/16 03:02:44 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>Pre-Obsolete Design - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2008/03/world-map-statistics.html" title="World Map and Statistics Challenge" />
   <link rel="next" href="http://www.w3.org/QA/2008/04/unescape-html-entities-python.html" title="Unescape HTML Entities in Python" />

   <!--
<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/03/pre-obsolete-design.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/154"
    dc:title="Pre-Obsolete Design"
    dc:identifier="http://www.w3.org/QA/2008/03/pre-obsolete-design.html"
    dc:subject="CSS"
    dc:description="Creating a specification is a challenge and a compromise. Far to be perfect it is an attempt at establishing stability for  a little while. The difficulty is often how long?"
    dc:creator="Karl Dubost"
    dc:date="2008-03-25T02:23:42+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/03/world-map-statistics.html">&laquo; World Map and Statistics Challenge</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2008/04/unescape-html-entities-python.html">Unescape HTML Entities in Python &raquo;</a>
                     </p>

                        <h2 class="entry-header">Pre-Obsolete Design</h2>
                           <div class="entry-body">
                              <p>Specifying a technology is a <a href="http://www.pantheon.org/articles/c/chronos.html">Chronos</a> dream. It is an attempt to take a snapshot of the state of art, to create stability for a little while. Technology users (such as Web designers and Web developers) are then able to create products (Web sites) with the basic assumption that people will have a similar user experience what ever the products they use. Douglas Coupland has shared in a <a href="http://www.guardian.co.uk/technology/2008/mar/22/gadgets.ebay">recent article in the Guardian</a> his relationship to devices:</p>

<blockquote>
  <p>What I essentially experienced this week was an ultra-high speed lesson in techno-obsolescence. Instead of taking 18 months to become doorstops, my new machines arrived pre-obsolete. They now reside in a Rubbermaid bin, along with my Museum of Old and Incompatible Cords, Adapters and Laptops. In about five years, when the bin fills to overflowing, its contents will be sent to the local landfill to be unearthed in one billion years by whatever species it is that supplants us.</p>
</blockquote>

<p>I have read on <a href="http://mezzoblue.com/">Dave Shea</a>'s blog about <a href="http://mezzoblue.com/archives/2008/03/18/mediatyping/">Mediatyping</a>. Dave Shea relates is unfortunate experience trying to setup a stylesheet for his blog that will work on mobile devices. He first started his design by specifying the CSS media type <code><a href="http://www.w3.org/TR/CSS21/media.html#media-types">handheld</a></code>. Dave said:</p>

<blockquote>
  <p>But here's the thing about media-specific style sheets: the browser in question has to support them. Mobile Safari grabs all screen media style sheets, and ignores the handheld media type entirely. So despite good intentions, my efforts were wasted on it. And that's what led me down the road of user agent sniffing...</p>
</blockquote>

<p>Dave went down the route of user agent sniffing. A discussion started on his blog to improve his code. A <a href="http://mezzoblue.com/archives/2008/03/18/mediatyping/#c038214">comment</a> by <a href="http://www.anildash.com/">Anil Dash</a> triggered a connection with Douglas' article:</p>

<blockquote>
  <p>what about what we've learned about the inadequacies of media types in CSS? Screen? Mobile? TV? Those aren't useful distinctions. It's another classic example of spec failure due to inadequate prognostication abilities. Someday we'll have the ability to see the future and this will all be easy.</p>
</blockquote>

<p>Chronos dream? We can't predict the future. A specification is here to fix time <strong>for a little while</strong>. The challenge is even greater for Web designers with the rise of ubiquitous computing. Small devices with a tremendous diversity in forms, size, capabilities factors and <strong>very short lifespan</strong>. W3C Working groups are working on these  challenging topics. For example, <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications</a> is working on a new version of <a href="http://www.webstandards.org/learn/articles/askw3c/feb2004/">CC/PP</a>. <a href="http://www.w3.org/Style/CSS/">CSS WG</a> is working on <a href="http://www.w3.org/TR/css3-mediaqueries/">Media Queries</a> with more customization capabilities. If a specification takes too much time to be released, it will be obsolete by the time it is published. If a specification is changing too often, people can't keep up with the changes and interoperability suffers. Finding the right compromise is difficult.</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 March 25, 2008  2:23 AM in <a href="http://www.w3.org/QA/archive/technology/css/">CSS</a>, <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/03/pre-obsolete-design.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2008/03/pre-obsolete-design.html#comments">Comments (1)</a>
                                 | <a href="http://www.w3.org/QA/2008/03/pre-obsolete-design.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-126502">
<p class="comment-meta" id="c126502">
<span class="comment-meta-author"><strong>David Shor </strong></span>
<span class="comment-meta-date"><a href="#c126502">#</a> 2008-03-30</span>
</p>
<div class="comment-bulk">
<p>The most fascinating thing about the times we live in are that those people who create the devices that pre-obsolesce are much more worried about their obsolescence than the general population. The obsession with the new by people who create the new is at an all-time high because of the global, transparent competition. </p>

<p>Yet the general public buys enormous quantities of very simple stuff to round out their lives all day long. Take for example, a simple little device my I bought my wife for valentine's day last year--[… edited…] Now, you'd think that everyone in the world had pretty much moved on from creating new technologies for something as old fashioned as purses, but you know what--the public thinks at that level and not beyond.</p>

<p>So let's not worry too much about the speed of things. It's all good.</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="164" />
<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:02:44 $</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>