the-digital-stakhanovite.html 13.4 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='data, exif, metadata, photo' />
    <meta name="description" content="Designing a technology that will accomodate our social contexts of the digital Stakhanovite is a big challenge, far to be simple to solve." />
    <meta name="revision" content="$Id: the-digital-stakhanovite.html,v 1.40 2011/12/16 03:03:00 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>The Digital Stakhanovite - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2008/08/markup_validator_updated.html" title="Markup Validator Updated" />
   <link rel="next" href="http://www.w3.org/QA/2008/08/web-directions-east-2008.html" title="Web Directions East 2008" />

   <!--
<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/08/the-digital-stakhanovite.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/206"
    dc:title="The Digital Stakhanovite"
    dc:identifier="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html"
    dc:subject="HTML"
    dc:description="Designing a technology that will accomodate our social contexts of the digital Stakhanovite is a big challenge, far to be simple to solve."
    dc:creator="Karl Dubost"
    dc:date="2008-08-18T02:18:43+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/08/markup_validator_updated.html">&laquo; Markup Validator Updated</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2008/08/web-directions-east-2008.html">Web Directions East 2008 &raquo;</a>
                     </p>

                        <h2 class="entry-header">The Digital Stakhanovite</h2>
                           <div class="entry-body">
                              <p>There is an increasing number of people living in a digital era. Not only the environment becomes digital, but their own life products are digital. I'm not the earliest adopter, but I have used computers since 1983, Internet since 1991 and digital photography since 1993. I have accumulated around 418.000 emails and around 45.000 photos.</p>

<p>Emails have basic metadata (author, subject, date), which helps to create proper indexing and search. It could be certainly refined with sophisticated search algorithms. Digital photos have now <a href="http://en.wikipedia.org/wiki/Exchangeable_image_file_format">EXIF</a> (including date, and technical parameters of the camera) but nothing much else. My brain associates these photos ordered in a dated space with a list that I maintain of my very rough location. It helps me remember in which city it was taken, but nothing more.  </p>

<p>Here lies the challenge. Giving more precise metadata to these photographs would be certainly useful for my own consumption but … a fulltime job. That would make me a <strong>digital <a href="http://en.wikipedia.org/wiki/Stakhanovite">Stakhanovite</a></strong>.</p>

<p>In <cite><a href="http://www.itworld.com/opinion/54005/musings-photographic-metadata">Musings on photographic metadata</a>, Sean McGrath</cite> says: </p>

<blockquote>
  <p>A great tragedy lies herein. A sad law of this universe seeps forth
  like an Einstinien nightmare. A law that goes something like this :
  "the chances of any normal human being taking the time to add
  incredibly valuable meta-data to the great wads of digital data they
  create daily, approximates zero." An alternative formulation - using
  the classic dentistry analogy goes like this: "Most people would
  prefer root canal work than the utter tedium and ambient feeling of
  futility that accompanies meta-data creation. Besides everyone is too
  busy. Oh, and besides that again, it always seems to be more fun to
  create new stuff than to create stuff about old stuff."</p>
</blockquote>

<p>Sean is trying to see what could be done automatically through the devices, location is certainly one that should happen more and more often, see the new <a href="http://www.dpreview.com/news/0808/08080702nikonp6000.asp">Nikon Coolpix P6000</a>  with <a href="http://en.wikipedia.org/wiki/GPS">GPS</a> and the <a href="http://www.w3.org/2008/06/geolocation/charter/">geolocation activity creation</a> being discussed at W3C right now.</p>

<p>The challenges become bigger when you want to share these photos with a larger public. At regular cycle, there is a rage debate over <code>alt</code> attribute on <a href="http://lists.w3.org/Archives/Public/public-html/">html working group</a> mailing list. I'm not sure there is a perfect solution and we have to find a way to accomodate the circumstances of this sharing. The difficulty is that the right solution is more social than technical. Giving meaningful alternative information for the images you put online, really depends on the context.  These are real scenarios.</p>

<ol>
<li>You want to share photos with your family. You sent them by emails (HTML emails most of the time), or you create an html gallery which is made by a software and put them online. You usually don't put more information than giving the <strong>context</strong> of the event and maybe sometimes description of some particular outstanding image, such as "Hey see the image below, it is the beach just in front of our room." The <strong>value</strong> of the image is limited to a few persons you know, still it might be here for public consumption.</li>
<li>You are writing an article on the Web about graphics arts. The article has a lot of   illustrations which are part of the argumentation, demonstrations. There are not only visual references, there are elements of the discourse.</li>
<li>You are writing an online diary mixing images, quotes, and different impressions. Your site is more like a scrapbooking exercise. Images are often here to give a mood of your writings. There are like simple touches of colors, or even sometimes an element of phrase. They have more emotional values for the readers who can see than anything else.</li>
</ol>

<p>There are many more possible cases. The big issue is how do we <strong>design the technology</strong> so that it will accomodate a maximum of use cases (<strong>social contexts</strong>) without making impossible for others to exist. There is not yet a definitive answer.</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 August 18, 2008  2:18 AM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</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/technology/semantic_web/">Semantic Web</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html#comments">Comments (1)</a>
                                 | <a href="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-163595">
<p class="comment-meta" id="c163595">
<span class="comment-meta-author"><strong>Christopher Yeleighton </strong></span>
<span class="comment-meta-date"><a href="#c163595">#</a> 2008-08-29</span>
</p>
<div class="comment-bulk">
<p>The situation is even worse when you think you should enter metadata in three incompatible places: EXIF comments, file system comments and picture gallery properties.  My goodness.</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="216" />
<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:00 $</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>