<?xml version="1.0" encoding="UTF-8"?>
<essay xml:lang="en" version="5.0" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:gal="http://norman.walsh.name/rdf/gallery#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
<info>
    
    
    
    
    
    
    
    
    
    
    
<title>W3C Technical Plenary 2006</title><biblioid class="uri">http://norman.walsh.name/2006/03/06/tp</biblioid>
<volumenum>9</volumenum>
<issuenum>25</issuenum>
<pubdate>2006-03-06T07:36:45-05:00</pubdate>
<date>$Date$</date>
<author>
      <personname>
<firstname>Norman</firstname>
	<surname>Walsh</surname>
</personname>
    </author>
<copyright>
      <year>2006</year>
      <holder>Norman Walsh</holder>
    </copyright>
<abstract>
<para>Meetings galore.</para>
</abstract>
<html:style type="text/css" xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">
#banner {
  background-image: url("images/pano.jpg");
  color: white;
}
#banner a {
  color: black;
  border-bottom: 1px dotted black;
}
#search {
  color: black;
}
</html:style>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#Conferences"/>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#W3C"/>
</info>

<para xml:id="p1">This year's
<link xlink:href="http://www.w3.org/2005/12/allgroupoverview.html">technical
plenary</link> was another
wall-to-wall meeting-fest. I started with two days of
<link xlink:href="http://xproc.org/">XProc</link> meetings.
It was our first face-to-face and I think it went really well.
Teleconferences, email, and
<link xlink:href="http://en.wikipedia.org/wiki/Internet_Relay_Chat">IRC</link>
are effective ways to communicate, but
some things just work better if you're in the same room arguing about
the same drawings on the same white board. I haven't finished crafting
what I hope is a synthesis of our discussions, but I think we reached
consensus about the conceptual nature of a pipeline, or at least of a
stage in a pipeline, and made some real progress on dealing with
multiple inputs and outputs and iteration. We might have made progress
on conditionals, but I'm not sure. There are some deeper issues about
the nature of pipeline processing (pull or push, forward or backward chaining)
that aren't resolved and conditionals seem to bear hard on those
issues. Personally, I hope that we will eventually agree that some of
those issues are implementation and optimization details, but it's not
clear we'll be able to. At this point, though, it's not clear we won't
either.</para>

<para xml:id="p2">Next was the plenary day. If you
aren't familiar with how these things work, the plenary week is
divided into three sections. Monday and Tuesday are devoted to working
group meetings. Wednesday is a
<link xlink:href="http://www.w3.org/2006/03/01-TechPlenAgenda.html">full-day,
all-hands plenary session</link>
with presentations, lightning talks, and panel sessions. On Thursday
and Friday, we return to working group meetings. Part of the benefit
of the plenary is that there are so many working groups meeting at the
same time and place, it's often possible to bring different groups
together to discuss common issues.</para>

<para xml:id="p3">I think I saw most of the presentations on the plenary day.
In no particular order, I recall sessions on data ownership and
<link xlink:href="http://en.wikipedia.org/wiki/Microformats">microformats</link>;
one of the “lightning talks” discussed
<link xlink:href="http://en.wikipedia.org/wiki/Single_Transferable_Vote">single
transferable voting</link> (STV) as a way of achieving
consensus;
there was also a session on grid computing; and the semweb folks had
a couple of slots, highlighted perhaps by
<personname>
      <firstname>Jim</firstname>
      <surname>Melton</surname>
    </personname>'s
discussion of
SQL and SPARQL. (Something of a reprise of his XML 2005 talk.)
There were some interesting SVG demos.
The XForms, HTML, and accessibility folks discussed a “rich web
application backplane” and demoed some
interactive web applications developed with more declarative markup.
And somewhere in there <personname>
      <firstname>Steven</firstname>
<surname>Pemberton</surname>
    </personname>, who's always provocative and
entertaining, discussed the
<link xlink:href="http://en.wikipedia.org/wiki/Sapir-Whorf_hypothesis">Sapir-Whorf hypothesis</link>.
We ended the day with a demo of <application>chad</application>, an
IRC bot implementing STV voting, and the consensus was that the
session on microformats was the favorite.</para>

<para xml:id="p4">I've
<link xlink:href="/2005/09/05/microformats">written about</link>
microformats before. They demo well and have
enough apparent simplicity to be appealing. As one of my colleagues
observed, it's like 1994 all over again, except this time instead of
making up tag names, we're making up class values. I suppose, over
time, we'll have to make up something like namespaces too<footnote>
<para xml:id="p5">“No” claim the microformats crowd. They're only going to standardize
a few common things, I think the argument goes, but that's not how these
things work. Cat. Bag. Out of. We will wind up with microformats using
the same class values in incompatible ways. But maybe there'll always be
enough heuristics to disambiguate them.</para>
    </footnote>. Class
values are an extension point in the design of HTML, I wonder what
the extension point in the microformats space will look like. What's
a micro-microformat going to look like? Square brackets? Hyphens? Maybe
there's an appropriate
<link xlink:href="http://en.wikipedia.org/wiki/Unicode">Unicode</link>
“extension” character?</para>

<para xml:id="p6">Anyway, I'm not saying microformats are without value. It's not
the approach that I wish we'd been able to take (I'd have been much
happier with a story that allowed me to put elements from a foreign
namespace in XHTML, using XML's more tractable extensibility points,
and then styling those with CSS) but that's just the way it is. While
I see significant problems with the microformats strategy, I'm trying
not to sound like an ivory tower nay-sayer to bottom-up design.</para>

<para xml:id="p7">I spent all day Thursday and Friday morning with the XML Core
working group. We had good discussions with some of the C14N
participants, some mobile folks, and hashed out a plan for
incorporating IRIs into the XML stack. And then maybe going into
maintenance mode. On Friday afternoon, I slipped away to join the second
TAG meeting of the week (I was chairing during the first meeting and
couldn't get away).</para>

<para xml:id="p8">All-in-all a good week. I collected a few new name-to-face mappings
and refreshed some stale ones. And I
<link xlink:href="http://flickr.com/photos/ndw/sets/72057594076292222/">took
pictures</link>, like everyone else.</para>

<para xml:id="p9">See you next time!</para>

</essay>

