<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns="http://purl.org/rss/1.0/">
  <channel rdf:about="http://times.usefulinc.com/tagexpectnation">
    <title>Edd Dumbill's Weblog: 'expectnation' articles</title>
    <description>Articles tagged as 'expectnation' from Edd Dumbill, technology writer and free software hacker.</description>
    <link>http://times.usefulinc.com/tagexpectnation</link>
    <dc:date>2008-07-01T16:00:17Z</dc:date>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://times.usefulinc.com/2008/07/01-oscon-sked"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2008/06/02-railsconf"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2008/05/23-updates"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2008/05/02-travel"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2008/04/01-going-solo"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/11/14-latest"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/06/22-disclosure"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/06/14-unconferences"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/06/01-expectnation"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/05/16-xtech-heatmaps"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/05/11-xtech"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/03/06-sparklines"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/02/27-openid-uformats"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2007/02/23-xtech"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2006/12/20-xtech-deadline"/>
        <rdf:li rdf:resource="http://times.usefulinc.com/2006/11/02-xtech-cfp"/>
      </rdf:Seq>
    </items>
  </channel>
  <item rdf:about="http://times.usefulinc.com/2008/07/01-oscon-sked">
    <title>OSCON: what are your must-see talks?</title>
    <link>http://times.usefulinc.com/2008/07/01-oscon-sked</link>
    <description>We've switched on personal schedule sharing on the OSCON web site.

</description>
    <dc:subject>linux</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>conferences</dc:subject>
    <dc:subject>oscon</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2008-07-01T15:58:59Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>&lt;p&gt;We've switched on personal schedule sharing on the &lt;a href="http://en.oreilly.com/oscon2008/"&gt;OSCON web site&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;When you've put together your desired schedule by starring sessions of interest, just hand out the "public view" link to let others know what you want to see.&lt;/p&gt;
&lt;p&gt;Here's &lt;a href="http://en.oreilly.com/oscon2008/public/schedule/share/71df5978de24b9ae2289b47712bf042c"&gt;my personal schedule&lt;/a&gt;. In it you'll find all the &lt;a href="http://en.oreilly.com/oscon2008/public/schedule/topic/Keynote"&gt;plenary sessions&lt;/a&gt; (as co-chair I simply cannot miss these, and neither should you, however late the party!)&lt;/p&gt;
&lt;p&gt;Also there's a fair smattering of my pet topics such as open web technologies, virtualization and dynamic languages, and a bunch of things I want to hear more about: &lt;a href="http://en.oreilly.com/oscon2008/public/schedule/detail/3098"&gt;Prophet&lt;/a&gt;, &lt;a href="http://en.oreilly.com/oscon2008/public/schedule/detail/2491"&gt;female participation in open source&lt;/a&gt;, &lt;a href="http://en.oreilly.com/oscon2008/public/schedule/detail/2383"&gt;Clutter&lt;/a&gt;, and of course &lt;a href="http://en.oreilly.com/oscon2008/public/schedule/detail/3373"&gt;Erlang&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I'm fascinated to find out what other people have got planned, so please publish your schedules too and let's compare notes.&lt;/p&gt;&lt;p&gt;&lt;a href="http://times.usefulinc.com/2008/07/01-oscon-sked#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2008/06/02-railsconf">
    <title>RailsConf, remotely</title>
    <link>http://times.usefulinc.com/2008/06/02-railsconf</link>
    <description>I couldn't make it to RailsConf this year, but have been playing my part from afar.</description>
    <dc:subject>rails</dc:subject>
    <dc:subject>railsconf</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>conferences</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2008-06-02T12:01:03Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>&lt;p&gt;I couldn't make it to &lt;a href="http://en.oreilly.com/rails2008/"&gt;RailsConf&lt;/a&gt; this year, but have been playing my part from afar. It gives me a small kick of pride to note that now RailsConf is run entirely out of &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt;, which is of course Rails-based.&lt;/p&gt;
&lt;p&gt;Here's a badge I clipped for my virtual scrapbook.&lt;/p&gt;
&lt;p&gt;&lt;img src="http://times.usefulinc.com/asset/name/43/dhh.png" alt="DHH's badge" width="504" height="166" /&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://times.usefulinc.com/2008/06/02-railsconf#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2008/05/23-updates">
    <title>Badges, blogging and bragging</title>
    <link>http://times.usefulinc.com/2008/05/23-updates</link>
    <description>Back from my travels, it's time for a few updates. I've mostly blogged about these elsewhere, so I'll just give some pointers here.</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>linux</dc:subject>
    <dc:subject>xml</dc:subject>
    <dc:subject>web</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2008-05-23T14:11:10Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>&lt;p&gt;Back from my travels, it's time for a few updates. I've mostly blogged about these elsewhere, so I'll just give some pointers here.&lt;/p&gt;
&lt;p&gt;The &lt;a href="http://www.expectnation.com/public/content/2008/05/22-reg-and-lead-retrieval"&gt;launch of magnetic-stripe cards&lt;/a&gt; at Where 2.0 went well.&lt;/p&gt;
&lt;p&gt;We had some initial teething issues with Linux talking to the card printers, which was resolved by backing down to Linux kernel 2.6.22 from 2.6.24. I'm not entirely sure what's up with 2.6.24, but it exhibited strange behavior talking to the card printers over ethernet &amp;mdash; as if there were MTU misconfigurations. It's a big nuisance, as 2.6.24 is the default kernel shipped with Ubuntu Hardy, an otherwise excellent release.&lt;/p&gt;
&lt;p&gt;I've been paying some attention to OpenID 2.0 recently, as it's time for me to upgrade my OpenID accepting websites to use the new release of the specification &amp;mdash; if for no other reason than Yahoo! OpenIDs are 2.0-only.&lt;/p&gt;
&lt;p&gt;This investigation led me to notice XRIs again, which are the confusing underbelly of the OpenID specs. The W3C Technical Architecture Group recently advised against using XRIs. I &lt;a href="http://www.oreillynet.com/xml/blog/2008/05/xris_bad_uris_good.html"&gt;wrote about this&lt;/a&gt;&amp;nbsp;over on my XML.com blog.&lt;/p&gt;
&lt;p&gt;I've not used for that blog for a long time, but will try to do so more. I've realized that I've still got a lot to say about the web, XML and open standards, and the XML.com blog seems like a good place to say it.&lt;/p&gt;
&lt;p&gt;Finally, to brag for a short moment. Another &lt;a href="http://2008.xtech.org/"&gt;XTech&lt;/a&gt;&amp;nbsp;has been and gone, and this year's was a great experience for everybody involved. This quote &lt;a href="http://paulsmith.blogs.ilrt.org/2008/05/19/xtech-2008-day-3/"&gt;from attendee Paul Smith&lt;/a&gt; summed things up nicely, as it tells me I succeeded in my main goal for the conference:&lt;/p&gt;
&lt;blockquote&gt;What I really liked about this conference was the mix of attendees and presenters, both from academia, and the commercial world both and small. It made it feel much more valid, and it really felt like everyone was there for the right reasons - not trying to sell anything, but out of a genuinely altruistic wish to make the web better.&lt;/blockquote&gt;
&lt;p&gt;My sincere thanks to everybody involved in XTech this year.&lt;/p&gt;&lt;p&gt;&lt;a href="http://times.usefulinc.com/2008/05/23-updates#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2008/05/02-travel">
    <title>Dublin and San Francisco</title>
    <link>http://times.usefulinc.com/2008/05/02-travel</link>
    <description>My next two jaunts; Dublin for XTech and San Francisco for Where 2.0</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>conferences</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2008-05-02T17:14:04Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>&lt;p&gt;About to go off travelling again.&lt;/p&gt;
&lt;p&gt;Next week is of course &lt;a href="http://2008.xtech.org/"&gt;XTech 2008&lt;/a&gt;, so I'll be in Dublin with some of the smartest people working in web technology today. The &lt;a href="http://2008.xtech.org/public/schedule/full"&gt;schedule&lt;/a&gt; looks fantastic, and we've still got proposals coming in for the &lt;a href="http://2008.xtech.org/public/schedule/detail/654"&gt;Lightning Talks&lt;/a&gt;, which promise to be highly entertaining and informative.&lt;/p&gt;
&lt;p&gt;If you didn't yet book, don't worry that you missed the online registration deadline, you can still register on-site.&lt;/p&gt;
&lt;h3&gt;Where 2.0&lt;/h3&gt;
&lt;p&gt;After XTech, it's straight to San Francisco (well, Burlingame) for the O'Reilly &lt;a href="http://en.oreilly.com/where2008"&gt;Where 2.0&lt;/a&gt; conference. Although I'm interested in the conference, my main reason for going is that &lt;a href="http://www.expectnation.com/"&gt;we're&lt;/a&gt; launching a new addition to our onsite check-in system: magnetic stripe conference badges.&lt;/p&gt;
&lt;p&gt;Here's a &lt;a href="http://assets.expectnation.com/1/eventprovider/1/where_badge.png"&gt;proof image of my badge&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img src="http://assets.expectnation.com/1/eventprovider/1/where_badge.png" alt="Badge proof for Where 2.0" width="499" height="160" /&gt;&lt;/p&gt;
&lt;p&gt;I've really enjoyed working with making badges: every so often as a software person, you get to write something that creates a physical artefact. I guess this is one reason &lt;a href="http://www.arduino.cc/"&gt;Arduino&lt;/a&gt; is so popular.&lt;/p&gt;
&lt;p&gt;It's also been interesting as we're working entirely within Linux. Specialized hardware like badge printers tends to be primarily aimed at Windows machines. Happily, the &lt;a href="http://www.evolis.com/"&gt;Evolis&lt;/a&gt; range of printers has CUPS drivers too.&lt;/p&gt;&lt;p&gt;&lt;a href="http://times.usefulinc.com/2008/05/02-travel#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2008/04/01-going-solo">
    <title>Freelancing in the internet industry</title>
    <link>http://times.usefulinc.com/2008/04/01-going-solo</link>
    <description>Stephanie Booth's Going Solo conference, coming up in May this year in Lausanne, is aimed at freelancers and self-employed people in the internet industry.</description>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>conferences</dc:subject>
    <dc:subject>work</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2008-04-01T09:34:17Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>&lt;p&gt;For all but the earliest part of my career I've either been, or been close to, freelancers in the web and free software world. While going solo is a rush of excitement, freedom and invention, there are also the hard parts of business to consider. I've seen too many people lose confidence and return to less liberated employment because they couldn't get to grips with the basics of getting work.&lt;/p&gt;
&lt;p&gt;This is why I'm really happy to see Stephanie Booth's &lt;a href="http://going-solo.net/"&gt;Going Solo&lt;/a&gt; conference, coming up in May this year in Lausanne. It's for freelancers and self-employed people in the internet industry, and will cover all the nitty gritty aspects of working alone, including business, marketing and the essentials of ensuring doing what you enjoy doesn't become a chore.&lt;/p&gt;
&lt;p&gt;I'll end with quoting from a recent posting of Stephanie's, &lt;a href="http://going-solo.net/2008/03/30/a-theory-about-freelancers-in-the-internet-industry/"&gt;A Theory About Freelancers in the Internet Industry&lt;/a&gt;. This struck a chord with me, and is what makes me think Going Solo is going to be an excellent event.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p style="color: #656565; font-family: 'Trebuchet MS'; font-size: 13px; line-height: 20px;"&gt;Most freelancers go solo because they are good at doing something that people are willing to pay for, and attracted by the freedom of being one&amp;rsquo;s own boss and the perspective of possible lucrative earnings. Business skills are not usually paid much attention to until they are suddenly needed, although they are what will determine how successful one can be in the long run. At that point, it&amp;rsquo;s common for the soloist to feel lost and isolated.&lt;/p&gt;
&lt;p style="color: #656565; font-family: 'Trebuchet MS'; font-size: 13px; line-height: 20px;"&gt;Going Solo is a one-day event that was designed to address this issue. We will gather 150 soloists and small business owners around a core group of speakers who are experienced freelancers and will share their knowledge on a variety of business topics. We also want to give freelancers an occasion to come in direct contact with others like them and build a European community where they can support each other.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;div style="text-align: center;"&gt;&lt;a href="http://going-solo.net/"&gt;&lt;img src="http://climbtothestars.org/files/going-solo/going-solo-badge-180px-wide.gif" alt="Going Solo conference for freelancers, May 16th, Lausanne (Switzerland)." /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;(Note: My conference software company,&amp;nbsp;&lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt;, is a sponsor of Going Solo, and it's been great for us to learn more about empowering small, focused operations as well as some of our&amp;nbsp;&lt;a href="http://conferences.oreilly.com/"&gt;larger customers&lt;/a&gt;.)&lt;/p&gt;
&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;p&gt;&lt;a href="http://times.usefulinc.com/2008/04/01-going-solo#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/11/14-latest">
    <title>Edd 10.5 release notes</title>
    <link>http://times.usefulinc.com/2007/11/14-latest</link>
    <description>The guilty catch-up obligatory before continuing to blog further.</description>
    <dc:subject>rails</dc:subject>
    <dc:subject>railsconf</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>family</dc:subject>
    <dc:subject>conferences</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-11-14T16:03:04Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded> 	 &lt;p&gt;I&amp;rsquo;ve had my head down with lots of hard work and exciting developments, and alas too little time to blog here. However, I wanted to post a few updates as to what&amp;rsquo;s been going on.&lt;/p&gt;    	&lt;h3&gt;Expectnation&lt;/h3&gt;   	 &lt;p&gt;Most of my time&amp;rsquo;s been spent working on &lt;a href="http://expectnation.com/"&gt;Expectnation&lt;/a&gt;, the conference and event management application my company works on.&lt;/p&gt;    	 &lt;p&gt;The highlight of this quarter is that we launched &lt;a href="http://expectnation.com/public/content/registration"&gt;registration facilities&lt;/a&gt;, so now in addition to planning content, creating your event web site and managing speakers, you can take money and register folk for your conference.&lt;/p&gt;    	 &lt;p&gt;We&amp;rsquo;re very excited about adding this, and it makes Expectnation the ideal &amp;ldquo;conference in a box&amp;rdquo; system.&lt;/p&gt;    	 &lt;p&gt;It&amp;rsquo;s a complete buzz to see submissions coming in for &lt;a href="http://en.oreilly.com/rails2008/public/content/home"&gt;RailsConf&lt;/a&gt; using our software&amp;mdash;Rails-based, of course!&lt;/p&gt;    	&lt;h3&gt;Conferences&lt;/h3&gt;   	 &lt;p&gt;I&amp;rsquo;m currently gearing up to open the call for participation for XTech 2008. We&amp;rsquo;ll be in Dublin, Ireland, in early May 2008. More soon on this front.&lt;/p&gt;    	 &lt;p&gt;Additionally, I&amp;rsquo;m going to be co-chair with Allison Randal for O&amp;rsquo;Reilly&amp;rsquo;s &lt;span class="caps"&gt;OSCON 2008&lt;/span&gt;. I can&amp;rsquo;t really say I&amp;rsquo;m filling Nat Torkington&amp;rsquo;s shoes (more like ironing &lt;a href="http://www.flickr.com/photos/x180/898259595/in/set-72157600967110580/"&gt;his shirts&lt;/a&gt;) but needless to say it&amp;rsquo;s a great privilege about which I&amp;rsquo;m thoroughly excited.&lt;/p&gt;    	 &lt;div style="margin: 2em; float: right"&gt;&lt;img width="350" height="263" src="/asset/name/40/k-read.jpg" alt="Katherine reading" /&gt;&lt;/div&gt;  &lt;p&gt;With being so busy, I&amp;rsquo;ve not had the time to travel as nearly as much as I&amp;rsquo;d like this year (the small matter of the baby twins has some bearing on this, too). I&amp;rsquo;m very sad to be missing &lt;a href="http://2007.xmlconference.org"&gt;&lt;span class="caps"&gt;XML 2007&lt;/span&gt;&lt;/a&gt;, as the &lt;span class="caps"&gt;XML&lt;/span&gt; crowd remains the most erudite, eclectic and friendly bunch of people I&amp;rsquo;ve ever had the pleasure to work with.&lt;/p&gt;    	&lt;h3&gt;Writing&lt;/h3&gt;   	 &lt;p&gt;My sporadic attempts to attain literary posterity will again come to the fore over the next few months, as a new project starts with my old friend and co-conspirator &lt;a href="http://www.simonstl.com/"&gt;Simon St.Laurent&lt;/a&gt;. All hush-hush for now, but I look forward to sharing the news and maybe some early-access content here.&lt;/p&gt; &lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/11/14-latest#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/06/22-disclosure">
    <title>Collecting minimal user information</title>
    <link>http://times.usefulinc.com/2007/06/22-disclosure</link>
    <description>Asking for too much information from users is a barrier to participation. So, we invented a way to make sure that users only get asked for as much as we need to know.</description>
    <dc:subject>programming</dc:subject>
    <dc:subject>rails</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>community</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-06-22T15:37:46Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded> &lt;p&gt;Web applications are in constant competition for a user's attention. Unlike shrink-wrap software, there's often no captive audience, and web apps must gently guide and woo users to help them to the best experience of the software.&lt;/p&gt; &lt;p&gt;This is particularly true when considering the problem of collecting personal details from a user. Collect too little information, and your app might not be able to function effectively. Collect too much information, and you raise the barrier for participation with your application. Users may either not be bothered, be alarmed at the apparent intrusion into their privacy, or fill out bogus information.&amp;nbsp;&lt;/p&gt; &lt;h3&gt;One size doesn't fit all&lt;br /&gt; &lt;/h3&gt; &lt;p&gt;I originally stumbled on the issue in the development of &lt;a href="http://expectnation.com/"&gt;Expectnation&lt;/a&gt;. The amount of information a conference speaker needs to give the organizers is significantly more than that of, say, a reviewer. An organizer will often want postal and phone details for a speaker, which are largely irrelevant to the review process. All conferences and events rely on the willingess of participants, so the path to participation needs to be as frictionless as possible.&lt;br /&gt;&lt;/p&gt; &lt;p&gt;Thus, a one-size-fits-all personal details form didn't make sense for us. At best, we could have simply made more fields optional, but that would result in missing information that we really did need.&lt;/p&gt; &lt;p&gt;Another solution would be to provide a dedicated personal details form per user type, e.g. different forms for speakers and reviewers. This is a non-starter, however, as users can take on many roles within a conference.&lt;/p&gt; &lt;p&gt;So, we had a problem on our hands: different levels of interaction with our application requires different levels of personal information.&lt;/p&gt; &lt;p&gt;We also had a second problem, which is that not all events and organizers want the same level of information. For example, a user group event is unlikely to need the same amount of information from speakers as an academic conference.&lt;/p&gt; &lt;p&gt;Thus we have two axes on which the amount of information required varies: by role, and by event.&amp;nbsp;&lt;/p&gt; &lt;h3&gt;Our solution: progressive disclosure&lt;/h3&gt; &lt;p&gt;We concluded that we wanted to adhere to two principles in the collection of user information for Expectnation:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;collect as little information from users as possible, and&lt;br /&gt; &lt;/li&gt; &lt;li&gt;allow organizers to determine the level of information they wish to collect.&lt;/li&gt; &lt;/ul&gt; The first objective was achieved by constructing a matrix of information items against user role, with the possible values of {required, optional, unused} for each item. We then achieved the second objective by allowing this matrix to be varied over each event. &lt;p&gt;We've named this concept &amp;quot;&lt;a href="http://expectnation.com/public/content/2007/06/21-tip-user-disclosure"&gt;progressive disclosure&lt;/a&gt;.&amp;quot;&lt;/p&gt; &lt;p&gt;What this means in practice is that a user is only ever asked for the information required to fulfil the roles they have within Expectnation. If they take on another role, they are asked for the additional information at that point, and not before.&lt;/p&gt; &lt;h3&gt;Implementation concerns&lt;/h3&gt; &lt;p style="float: right; margin-left: 10px; text-align: center"&gt;&lt;img width="341" height="229" src="http://times.usefulinc.com/asset/name/39/small-disc.jpg" alt="Expectnation user disclosure editing" /&gt;&lt;br /&gt;Extract from disclosure level editing UI&lt;/p&gt; &lt;p&gt;It would be untrue to say that progressive disclosure is simple to implement.&lt;/p&gt; &lt;p&gt;A user in our system will have disclosure requirements that are the union of all of their roles in all of the events they attend. Within Ruby on Rails, this means the conventional validation logic is useless to us, as it only deals with static requirements. Secondly, disclosure requirements are expensive to compute, so we need to cache them, with the inevitable addition of issues such as cache invalidation.&lt;/p&gt; &lt;p&gt;Beyond the data model issues, the user interface issues are, if anything, more troublesome. From an end-user's point of view, the difficulty arises when we need extra information from them, and presenting this in a way that makes sense.&lt;/p&gt; &lt;p&gt;From the event organizer's point of view, we have the challenge of presenting a controlling user interface for rather a complex concept. Organizers must be able to change the level of required information either globally, or per-event.&lt;/p&gt; &lt;p&gt;We opted for a grid presentation, an extract from which is shown in the screenshot in this article. Over time we'll be able to see how effective this interface is, and what we can do to improve it.&lt;/p&gt; &lt;p&gt;Finally, we have chosen sensible defaults for all disclosure levels, as the best result would be that organizers have little need to reconfigure the settings in the first place.&lt;/p&gt; &lt;h3&gt;Making it look easy&lt;/h3&gt; &lt;p&gt;Because Expectnation is a general application for organizing events, rather than targetting one specific one, we've had to construct a framework for minimizing user information collection, as opposed to simple implementation of known scenarios.&lt;/p&gt; &lt;p&gt;At the end of the day we have added a fairly complicated subsystem and an extra degree of complexity to our codebase. However, the result from the user's point of view is increased simplicity and a streamlined experience.&lt;/p&gt; &lt;p&gt;Every time you embark on something that wide-reaching and complex, you have to ask yourself whether the feature is really worth it. In this case, though, the answer is a resounding &amp;quot;yes&amp;quot;. The user is the most important factor in our software, and making their life easier in an unobtrusive manner is a priority.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Expectnation blog: &lt;a href="http://expectnation.com/public/content/2007/06/21-tip-user-disclosure"&gt;Only ask users for the information you need&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt; &lt;br /&gt; &lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/06/22-disclosure#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/06/14-unconferences">
    <title>BarCamps and unconferences: what software support do you need? </title>
    <link>http://times.usefulinc.com/2007/06/14-unconferences</link>
    <description>Discussing how Expectnation can be made even more useful to ad-hoc conferences.</description>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>conferences</dc:subject>
    <dc:subject>barcamp</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-06-14T17:45:07Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded> &lt;p&gt;My latest venture, &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt;, is conference management software aimed primarily at the traditional form of running conferences. The schedule, speakers and topics are all lined up in advance.&lt;/p&gt;  &lt;p style="float: right; margin-left: 10px; text-align: center"&gt;&lt;img width="394" height="250" alt="Foo Camp" src="http://times.usefulinc.com/asset/name/38/foocamp.jpg" style="border-bottom: 0.5em none" /&gt;&lt;br /&gt;&lt;em&gt;Campers at O'Reilly's Foo Camp unconference&lt;/em&gt;&lt;/p&gt;  &lt;p&gt;However, many conferences now are taking the form of &amp;quot;&lt;a href="http://en.wikipedia.org/wiki/Unconference"&gt;unconferences&lt;/a&gt;&amp;quot; in whole or part, exemplified by the &lt;a href="http://barcamp.org/"&gt;BarCamp&lt;/a&gt; movement. At these events, the schedule is assembled just in time, and almost everybody is a presenter.&lt;/p&gt; &lt;p&gt;The same problems exist for BarCamp organizers as for conventional event organizers. They still need to use a bunch of diverse tools for their web sites, registration, communication and reportage. Expectnation solves this problem by being a &amp;quot;one-stop shop&amp;quot; tool for conventional conference structures, and we want to do it for BarCamps and unconferences too.&lt;/p&gt; &lt;h3&gt;Tell me what you need&amp;nbsp;&lt;/h3&gt; &lt;p&gt;I'm asking for feedback from attendees and organizers of BarCamp-like events as to what kinds of features they're seeking in their support software. We already have the platform to build on, and we want to find out the best ways in which to do it.&lt;/p&gt;&lt;p&gt;The sort of subject areas I'm keen to hear about include&lt;/p&gt;&lt;ul&gt;&lt;li&gt;registration,&lt;/li&gt;&lt;li&gt;attendee social networking,&lt;/li&gt;&lt;li&gt;documenting the event,&lt;/li&gt;&lt;li&gt;tools already in use, and their effectiveness.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;If you have views on this, please join the &lt;a href="http://forums.expectnation.com/viewtopic.php?id=22"&gt;discussion thread over on the forums&lt;/a&gt;. It's worth restating too that I'm very keen to talk about this with attendees as well as organizers.&lt;/p&gt;&lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/06/14-unconferences#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/06/01-expectnation">
    <title>Launching Expectnation</title>
    <link>http://times.usefulinc.com/2007/06/01-expectnation</link>
    <description>For the last 18 months, I've been hard at work with Expectnation. Now it's live!</description>
    <dc:subject>software</dc:subject>
    <dc:subject>web</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>conferences</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-06-01T15:04:46Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded> &lt;p&gt;I'm very pleased to announce the launch of &lt;a href="http://expectnation.com/"&gt;Expectnation&lt;/a&gt;, a web application for managing conferences.&lt;/p&gt; &lt;p style="float: right; margin-left: 15px"&gt;&lt;img width="218" height="46" src="http://times.usefulinc.com/asset/name/37/enation-logo.png" alt="Expectnation logo" /&gt;&lt;/p&gt; &lt;h3&gt;What does it do?&lt;/h3&gt; &lt;p&gt;Expectnation is intended to replace the ad-hoc collection of emails, spreadsheets, documents and hacks that hold together the organization of most conferences. The aim is to improve the quality and reliability of communication between the organizers, speakers and attendees.&lt;/p&gt; &lt;p&gt;But it doesn't stop there. What I'm really excited about is the chance to enhance the conference experience through the web. Expectnation is capable of managing the complete web site for a conference, which provides many opportunities for bringing the best of the social software world to augment events.&lt;/p&gt; &lt;p&gt;Our tagline is &amp;quot;build your conference into a community&amp;quot;, which underpins a key aim: to help organizers make events more relevant and useful to attendees, and to live on beyond the event itself. We do this in two ways: saving time, so you can spend it on improving your conference, and providing online tools to support community building.&lt;br /&gt; &lt;/p&gt; &lt;p&gt;Right now Expectnation is able to manage the proposal, review, scheduling and publication of presentations, along with the conference web site and smart emailing to speakers, reviewers and chairs. Over the next two months we'll be introducing our registration module, with optional online payments, and working on extending the social software features available for attendees.&lt;/p&gt; &lt;h3&gt;Take a look&amp;nbsp;&lt;/h3&gt; &lt;p&gt;I'm really excited about letting users get started with Expectnation, and seeing the uses it gets put to. We believe Expectnation will be just as handy for organizing events inside an organization as for traditional conferences.&lt;/p&gt; &lt;p&gt;So, if you organize, speak at, or attend conferences of any sort, please check out &lt;a href="http://expectnation.com/"&gt;Expectnation&lt;/a&gt; and recommend it to a conference organizer near you!&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Related links&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="http://expectnation.com/public/content/website"&gt;Expectnation tour&lt;/a&gt; complete with screenshots &lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://times.usefulinc.com/tag/expectnation"&gt;Previous posts&lt;/a&gt; I've written about Expectnation&lt;/li&gt;&lt;li&gt;&lt;a href="http://2007.xtech.org/"&gt;XTech 2007&lt;/a&gt; was completely managed inside Expectnation&amp;nbsp;&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/06/01-expectnation#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/05/16-xtech-heatmaps">
    <title>XTech heatmaps</title>
    <link>http://times.usefulinc.com/2007/05/16-xtech-heatmaps</link>
    <description>Simple visualisation to help conference organizers.</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>visualization</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-05-16T15:16:57Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded> &lt;p&gt;One of the fun and useful things we've been able to do in &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt; with the &lt;a href="http://times.usefulinc.com/2007/05/11-xtech"&gt;personal scheduler&lt;/a&gt; is to use the data to help us as organizers.&lt;/p&gt; &lt;p&gt;We recently added in dynamic overlays to the organizer's view of the schedule, enabling us to create heatmaps of the most popular talks.&lt;/p&gt; &lt;p style="text-align: center"&gt;&lt;img width="184" height="424" alt="Heatmap" src="http://times.usefulinc.com/asset/name/35/heatmap.png" title="Heatmap" /&gt;&lt;br /&gt;Screenshot of personal scheduler popularity overlaid on event timetable&lt;/p&gt; &lt;p&gt;As well as satisfying natural curiosity, the heatmaps let us identify issues such as possible room overcrowding in advance.&lt;/p&gt; &lt;p&gt;We're able also to record actual attendance figures as the conference goes on, and I will try and make an analysis of how attendees' intentions stack up against their actions.&amp;nbsp;&lt;/p&gt; &lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/05/16-xtech-heatmaps#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/05/11-xtech">
    <title>Up close and personal at XTech</title>
    <link>http://times.usefulinc.com/2007/05/11-xtech</link>
    <description>News of the XTech browser summit and personal scheduler.</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>web</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-05-11T16:53:19Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded> &lt;p&gt;It's been a long time since I last wrote, mostly because we've been pulling out all the stops for &lt;a href="http://2007.xtech.org/"&gt;XTech&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;Next week is set to be stimulating and challenging. I'm amazed at the collection of thinkers and innovators we've drawn together, and am looking forward to getting a boost of energy and inspiration from the conference.&lt;br /&gt; &lt;/p&gt; &lt;h3&gt;Browser summit&lt;/h3&gt; &lt;p&gt;On Tuesday next week, &lt;a href="http://molly.com/"&gt;Molly Holzschlag&lt;/a&gt; and I are sponsoring a &lt;a href="http://2007.xtech.org/public/content/2007/05/10-browser-summit"&gt;Web Browser, Standards and Interop Summit&lt;/a&gt;. This is an opportunity for browser vendors, standards advocates, W3C and related standards supporters to talk in a vendor (and standards-body) neutral atmosphere about tackling the problem of browser interoperability.&lt;/p&gt; &lt;p&gt;As the &lt;a href="http://2007.xtech.org/public/content/2007/05/10-browser-summit"&gt;full announcement&lt;/a&gt; mentions, we're also throwing open the doors to interested bloggers and journalists to get involved in and cover the discussion.&lt;/p&gt; &lt;p&gt;The summit came about after Molly and I got talking about our desire to provide a forum for effective exchange between the people shaping the future of HTML. This is something that spawned the vision of the Browser Track and XTech in the first place three years ago.&lt;/p&gt; &lt;p&gt;I don't know how much we'll solve at the first summit, but it puts down a marker and a challenge for participation. I am not the only one concerned at the increasing fragmentation of the HTML landscape, the breakdown in communication, and the ultimate ill-effects for web developers and users.&lt;/p&gt; &lt;h3&gt;Personal scheduler and evaluations&lt;/h3&gt; &lt;p&gt;As my conference software &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt; nears its public launch, we'll be using some of its fun features at XTech. Normally, the bulk of the work is done behind the scenes, so it's nice to have a feature to show off to attendees and the wider public.&lt;/p&gt;  &lt;p&gt;&lt;img width="195" hspace="8" height="163" align="right" src="http://times.usefulinc.com/asset/name/34/psched.png" alt="Personal scheduler" title="Personal scheduler" /&gt;&lt;/p&gt;  &lt;p&gt;The personal scheduling feature lets you compose your own timetable for the conference, just by clicking on the stars throughout the schedule. As a bonus, you can subscribe to your personal schedule as iCal, allowing you to take it with you on your phone or PDA.&lt;/p&gt; &lt;p&gt;In addition, we'll be allowing attendees to submit evaluations of sessions online. If you're using the personal scheduler, it gets even neater as you can quickly find links to submit your evaluations, and review ones you've already submitted.&lt;/p&gt; &lt;p&gt;Behind the scenes, I can see which sessions are the most popular and get advance warning if we're likely to need to move rooms to avoid overcrowding.&lt;/p&gt; &lt;p&gt;I'm pretty excited about this. Features like this aren't exactly new, but now we've made them a standard feature for every conference. We're looking forward to adding more social software facilities to enhance the conference experience.&lt;/p&gt;&lt;p&gt;&lt;img width="444" height="246" title="Submitting session evaluations" alt="Submitting session evaluations" src="http://times.usefulinc.com/asset/name/33/eval.png" /&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/05/11-xtech#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/03/06-sparklines">
    <title>Using sparklines to aid conference proposal selection</title>
    <link>http://times.usefulinc.com/2007/03/06-sparklines</link>
    <description>A brief survey of XTech voting patterns as illustrated by sparklines.</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>visualization</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-03-06T15:34:10Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>  &lt;p&gt;In a &lt;a href="http://times.usefulinc.com/2007/02/23-xtech"&gt;recent article&lt;/a&gt; I explained some of the mechanics behind putting together the schedule for &lt;a href="http://2007.xtech.org/"&gt;XTech 2007&lt;/a&gt;. We've just added new visualization features to &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt; that make proposal choice easier, and I thought I'd show some examples from the XTech 2007 review voting.&lt;/p&gt;   &lt;p&gt;&lt;a href="http://en.wikipedia.org/wiki/Sparkline"&gt;Sparklines&lt;/a&gt;, devised by Edward Tufte, are thumbnail sketches of data that succinctly convey patterns. When Nat Torkington used sparklines to show reviewer voting patterns for OSCON program committee, it seemed a helpful addition to make to Expectnation.&lt;/p&gt;   &lt;p&gt;The profile of each reviewer is interesting &amp;mdash; are they a harsh marker, or liberal with the top grades? &amp;mdash; but sparklines really come into their own when drawn per proposal. Here are some small screenshots from this year's XTech voting, anonymized of course.&lt;br /&gt;&lt;/p&gt;  &lt;h3&gt;High flyers&lt;/h3&gt;  &lt;p&gt;&lt;img width="185" height="15" alt="High scoring chart" src="/asset/name/24/high-1.png" /&gt;&lt;/p&gt; &lt;p&gt;Reviewers are pretty unanimous about this proposal, as 4.0 is the top grade in our scoring system. The lack of variance suggests that I ought to ensure that all the assigned reviewers put in their scores &amp;mdash; this could be just one person voting.&amp;nbsp;&lt;/p&gt;   &lt;p&gt;&lt;img width="185" height="15" alt="High scoring chart" src="/asset/name/25/high-2.png" /&gt;&lt;/p&gt;   &lt;p&gt;&lt;img width="185" height="15" alt="High scoring chart" src="/asset/name/26/high-3.png" /&gt;&lt;/p&gt;   &lt;p&gt;These next two are the pretty typical distribution for highly graded proposals: mostly top marks and a few average ones.&amp;nbsp;&lt;/p&gt;  &lt;h3&gt;Middle ranking&lt;/h3&gt;&lt;p&gt;Some of the more interesting trends show up when the scoring isn't biased to either the top or bottom ends of the scale.&amp;nbsp;&lt;/p&gt;  &lt;p&gt;&lt;img width="185" height="15" src="/asset/name/30/medium-1.png" alt="Medium scoring chart" /&gt;&lt;/p&gt;&lt;p&gt;The reviewers are unanimous about this paper's soundness. It's not made anyone go &amp;quot;wow&amp;quot;, but there's nothing to grumble about either.&amp;nbsp;&lt;/p&gt; &lt;p&gt;&lt;img width="185" height="15" src="/asset/name/31/medium-2.png" alt="Medium scoring chart" /&gt;&lt;/p&gt;&lt;p&gt;This proposal clearly polarises opinion, and is such stands a better chance than the unanimous 3.0 above. Perhaps the subject matter or approach is controversial or timely.&lt;br /&gt;&lt;/p&gt; &lt;p&gt;&lt;img width="185" height="15" src="/asset/name/32/medium-3.png" alt="Medium scoring chart" /&gt;&lt;/p&gt;&lt;p&gt;Another proposal that divides the reviewers' opinions. It's also worth me checking here that I don't either have a pathologically strict reviewer, or at the other end, a reviewer with a wild passion for the cause this paper advocates.&amp;nbsp;&lt;/p&gt;  &lt;h3&gt;Low scoring&lt;/h3&gt;  &lt;p&gt;The quality of submissions is usually so good that I don't give low graded proposals much attention, but the sparklines could alert me to potential oversights.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;img width="185" height="15" src="/asset/name/27/low-1.png" alt="Low scoring chart" /&gt;&lt;/p&gt;&lt;p&gt;This proposal seems to polarise opinion between &amp;quot;rubbish&amp;quot; and &amp;quot;ok&amp;quot;, so it's interesting to me to check out the subject matter and see if I'm missing something with potential.&amp;nbsp;&lt;/p&gt; &lt;p&gt;&lt;img width="185" height="15" src="/asset/name/28/low-2.png" alt="Low scoring chart" /&gt;&lt;/p&gt; &lt;p&gt;&lt;img width="185" height="15" src="/asset/name/29/low-3.png" alt="Low scoring chart" /&gt;&lt;/p&gt; &lt;p&gt;These proposals were not received at all well.&lt;/p&gt;&lt;p&gt;In summary, I'm delighted to find a solid practical application for sparklines. My thanks to Nat Torkington for the inspiration.&amp;nbsp;&lt;/p&gt;  &lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/03/06-sparklines#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/02/27-openid-uformats">
    <title>OpenID and microformats support on XTech site</title>
    <link>http://times.usefulinc.com/2007/02/27-openid-uformats</link>
    <description>Two useful new additions to the Expectnation conference system:  decentralized identity support and easy ways to integrate the schedule with your calendar</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>semweb</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>openid</dc:subject>
    <dc:subject>microformats</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-02-27T10:08:42Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>  &lt;p&gt;Thanks in no small part to the advocacy of &lt;a href="http://simonwillison.net/"&gt;Simon Willison&lt;/a&gt;, I've just &lt;a href="http://openid.net/"&gt;OpenID&lt;/a&gt;-enabled the &lt;a href="http://xtech.expectnation.com/"&gt;XTech&lt;/a&gt; web site.&lt;/p&gt;       &lt;p style="float: right; margin-left: 8px"&gt;&lt;img width="196" height="195" src="/asset/name/22/enation-openid.png" alt="OpenID log in box on Expectnation" /&gt; &lt;/p&gt;      &lt;p&gt;Users can now create their accounts using an OpenID, or associate an OpenID with an existing account.&lt;/p&gt;   &lt;p&gt;A single-sign on solution like OpenID solves an important problem for us, as most people tend to interact with our conference web sites in only one or two time periods each year. While we've gone to the trouble of making retrieving a password easy, there's still the mental burden on the user of setting up the account and noting it down somewhere.&lt;/p&gt;   &lt;p&gt;As a measure of the impact of this on me personally: I habitually save registration confirmation emails in a certain mail folder. Since 1997 I have collected no fewer than 572 of these, and I'm sure some have been missed!&lt;/p&gt;      &lt;p&gt;One other cool thing about OpenID is that finally I can get the identity I wish to have. No longer do I have to be a compulsive early adopter of every service just to get the name &lt;em&gt;edd&lt;/em&gt;. (Well, as long as said service integrates OpenID of course!) Personal branding is an important attractive aspect of OpenID.&lt;/p&gt;&lt;h3&gt;Implementation&lt;/h3&gt;&lt;p&gt;Implementing OpenID using the Ruby &lt;em&gt;ruby-openid&lt;/em&gt; gem was quite straightforward, as was the logical integration into our user models. I've not been the only one following this path recently, as illustrated by &lt;a href="http://www.danwebb.net/2007/2/27/the-no-shit-guide-to-supporting-openid-in-your-applications"&gt;this post on Rails OpenID integration&lt;/a&gt; from Dan Webb.&lt;/p&gt;&lt;p&gt;The harder problem of deploying OpenID lies in making the user interface work well: ultimately that will have a huge influence over its uptake.&lt;/p&gt;   &lt;p&gt;We've made a decent first go of it in &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt;, but I'm sure we'll evolve and improve it over time. The main puzzling thing is how obvious to make the OpenID facility, given its relatively small take-up right now. We don't want to confuse normal users too much by using it.&lt;/p&gt;  &lt;h3&gt;Microformats&lt;/h3&gt;  &lt;p&gt;When I did my &lt;a href="http://times.usefulinc.com/2007/02/23-xtech"&gt;behind-the-scenes piece&lt;/a&gt; on the building of the XTech schedule last week, one feature I didn't discuss was the support for &lt;a href="http://microformats.org/"&gt;microformats&lt;/a&gt; we have in the schedule and on the session pages. If you use a tool such as &lt;a href="http://labs.mozilla.com/2006/12/introducing-operator"&gt;Operator&lt;/a&gt;, you can easily save talk times to your calendar while reading the schedule.&lt;br /&gt;&lt;/p&gt;   &lt;p style="text-align: center"&gt;&lt;img width="404" height="274" src="/asset/name/23/microformats.png" alt="XTech schedule microformats" /&gt;&lt;/p&gt;   &lt;p&gt;I'm personally a little late to the microformats party. Being a fan of pragmatic RDF, I didn't see much need for microformats right away. However, with tools like Operator I can honestly say that the use of microformats does enhance the XTech schedule.&lt;/p&gt;&lt;p&gt;My impressions of microformats (in particular hCalendar and hCard) from using them are mixed. One the plus side, it was very easy to do. On the negative side, I found them restrictive in the sense that for the metadata to be present in the hCalendar object, it needs to be part of the HTML presentation.&lt;/p&gt;&lt;p&gt;So, while microformats are meant to be about making human readable data useful for computers, they can have a tail-wagging effect on the human markup. Let me elaborate.&lt;/p&gt;&lt;p&gt; In the conference schedule there is a grid overview. For readability here we want to keep the details down to a minimum in each box. There is definitely no need to repeat the date of each presentation when you can see there's a grid per day.&lt;/p&gt;&lt;p&gt;But also we want to have microformats available in the page so users can use the grid to pick off talks to add to their calendar. The only details you currently get from the microformat are those you physically include inside the &lt;em&gt;div&lt;/em&gt; marked as &lt;em&gt;vevent&lt;/em&gt;. This means we can't embed the full details, such as the talk description. It also means I indulge in some dubious markup practices (an empty &lt;em&gt;abbr&lt;/em&gt; element) in order to get the date and time into each hCalendar object.&lt;/p&gt;&lt;p&gt;It seems to me that this could be ameliorated by more intelligent user agent behaviour. Each of my hCalendar events is given a URL. At the end of that URL is a full description of the event, using microformats. So, as long as I reference the URL in a summary page, the user agent can beetle off and pull down the full information, in much the same sort of way that &lt;a href="http://www.foaf-project.org/"&gt;FOAF&lt;/a&gt; uses the &lt;em&gt;rdfs:seeAlso&lt;/em&gt; property.&lt;/p&gt;&lt;p&gt;So, remove the expectation that microformats provide complete data, and I'm sold.&lt;/p&gt;&lt;h3&gt;Other schedule features: iCal, Upcoming.org&lt;br /&gt;&lt;/h3&gt;&lt;p&gt;Of course, we have iCalendar support in the XTech &lt;a href="http://xtech.expectnation.com/event/1/public/schedule"&gt;schedule&lt;/a&gt;, so you can subscribe conventionally using iCal, Evolution or a similar program. &lt;a href="http://www.aaronstraupcope.com/"&gt;Aaron Straup Cope&lt;/a&gt; took the iCalendar, and uploaded each event into Upcoming.org. If you look at the &lt;a href="http://upcoming.org/tag/xtech07/"&gt;upcoming events tagged xtech07&lt;/a&gt;, you see the results of his work.&lt;/p&gt;&lt;p&gt;This foreshadows some of the social elements we plan to add to Expectnation itself: indicating your intent to attend a talk, and adding comments to it. As a program chair I'm finding this quite fascinating to watch.&lt;br /&gt;&lt;/p&gt; &lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/02/27-openid-uformats#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2007/02/23-xtech">
    <title>XTech 2007 schedule: behind the scenes</title>
    <link>http://times.usefulinc.com/2007/02/23-xtech</link>
    <description>The building of the XTech 2007 schedule.</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:subject>conferences</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2007-02-23T15:10:00Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>       &lt;p&gt;After a couple of months' hard work, I've &lt;a href="http://xtech.expectnation.com/event/1/public/schedule/grid"&gt;posted the schedule for XTech 2007&lt;/a&gt;. And, though I say so myself, it looks good.&lt;/p&gt;             &lt;p style="float: right; margin-left: 8px"&gt;&lt;a href="http://xtech.expectnation.com/event/1/public/schedule/grid"&gt;&lt;img width="304" height="270" border="0" src="http://times.usefulinc.com/asset/name/19/grid.png" alt="XTech 2007 grid" /&gt;&lt;/a&gt; &lt;/p&gt;             &lt;p&gt;You can read more about the schedule itself &lt;a href="http://xtech.expectnation.com/event/1/public/content/2007/02/22-schedule-posted"&gt;over on the XTech web site&lt;/a&gt;, but I thought it would be interesting to explain how we got there.&lt;/p&gt;     &lt;h3&gt;The people bit&amp;nbsp;&lt;/h3&gt;     &lt;p&gt;After the &lt;a href="http://xtech.expectnation.com/event/1/public/cfp/1"&gt;call for participation&lt;/a&gt;, we wound up with 200 proposals in the system. From there, the target was to get down to 5 tutorials and 68 presentations.&lt;/p&gt;         &lt;p&gt;Each proposal contains an abstract of at most 500 words. I enlisted a small army of reviewers (69 in all) to help, and assigned four or five reviewers to each abstract. 829 reviews were assigned in all. The reviewers work blind, so they don't get to see who the proposer is.&lt;br /&gt;     &lt;/p&gt;         &lt;p&gt;After the review, I read every score and proposal, and created a shortlist of the best scoring proposals plus those that had spuriously low scores given their quality. From this shortlist the hard graft of preparing a draft schedule started.&lt;/p&gt;         &lt;p&gt;We had already decided in advance on our usual format: four parallel tracks of browsers, core tech, applications and open data. I then filled in the schedule, aiming to create themes for days, or at least for the 2-session blocks.&lt;/p&gt;         &lt;p&gt;The draft schedule and details of those shortlisted but who missed the cut were circulated among the committee. After some iteration and feedback the final schedule emerged.&lt;/p&gt;         &lt;p&gt;Picking tutorials was a little different, as this is done by myself and the committee directly. The constraints on choice are more commercially-oriented. Experience has shown we need mainstream topics that people will be happy to pay for. Even so, each year we try to include one emerging topic. Last year, it was Rails. This year, it's &lt;a href="http://xtech.expectnation.com/event/1/public/schedule/detail/185"&gt;OpenStreetMap&lt;/a&gt;.&lt;br /&gt;     &lt;/p&gt;         &lt;p&gt;Choices made, I then notified the speakers, awaited their confirmation, and reached the point where we could publish the schedule.&lt;/p&gt;     &lt;h3&gt;The mechanics of it all&lt;/h3&gt;     &lt;p&gt;A glib reading of the above would make it all sound quite simple. And this year I'm pleased to report that it was a lot simpler than previous years. We have been able to use &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt; from beginning to end, which has streamlined a lot of the work.&amp;nbsp;&lt;/p&gt;   &lt;p&gt; Expectnation's my super startup that's taking up the time that XTech and fatherhood don't! I'm about to tell you why it's wonderful, so please forgive a little pride.&lt;br /&gt;  &lt;/p&gt;         &lt;p&gt;Gathering the proposals was easy once the CFP had been set up inside Expectnation. I set up three calls: one for presentations, one for tutorials, and a secret one that the public doesn't get to see. (We always need a secret one for people who have very good reasons why they didn't make the public deadlines.)&lt;/p&gt;         &lt;p style="float: right; margin-left: 8px; margin-bottom: 8px"&gt;&lt;img width="218" height="210" alt="Request response" src="http://times.usefulinc.com/asset/name/20/Picture_27.png" /&gt;&lt;/p&gt;      &lt;h4&gt;The review phase&lt;/h4&gt;   &lt;p&gt;Recruiting reviewers was done by Expectnation's request system. This lets me send a request to a large number of people simultaneously, and collect their responses via the web app. (Previously, this had involved email, spreadsheets and wasted time.) The chart you see to the right shows the breakdown of the response to this request.&lt;/p&gt;         &lt;p&gt;If a reviewer said 'yes', they added a note to say which types of proposal they would review, and signed up for an account in the system.&lt;/p&gt;     &lt;p&gt;I then passed through every paper assigning four or five appropriate reviewers. A quick search each time allowed me to look for the right reviewers, and ensure no one reviewer got overloaded with work.&lt;/p&gt;     &lt;p&gt;Once reviewers were assigned, I headed over to the Mailroom department. Expectnation has a large number of configurable mailing targets, one of which is &amp;quot;reviewers with work to do&amp;quot;. I emailed each reviewer with details of how to get on with the reviewing.&lt;/p&gt;     &lt;p&gt;Every reviewer then logged into Expectnation, saw the proposals they needed to review, and used the interface to efficiently score the proposals. One big lesson here is that it needs to be very efficient if you want to get the best reviewers, who are often the busiest.&lt;/p&gt;     &lt;p&gt;Another wizzy graph enabled me to keep track of the reviews, and the mailroom let me send out a reminder to those reviewers who hadn't finished their work yet, when the time for the close of reviewing drew near.&lt;/p&gt;   &lt;h4&gt;Picking the papers&lt;/h4&gt;   &lt;p style="float: right; margin-left: 8px; margin-bottom: 8px"&gt;&lt;img width="217" height="247" alt="Gridding out XTech 2007" src="/asset/name/21/gridding.png" /&gt;&lt;/p&gt;     &lt;p&gt;Expectnation lets me sort and filter proposals pretty flexibly, so I went through the papers for each track in turn, ordered by their review score. Anything scored 3 or higher (4 is best, 1 is worst) was almost certain to be shortlisted. I read all the reviews and the abstract, and moderated any score that was unusually low (for some reason, reviewers rarely overrate proposals!)&lt;/p&gt;     &lt;p&gt;The next step was to set up the empty grid, shown in the top half of the diagram to the right. Here I added the empty time slots to the rooms we had, and assigned putative tracks to each of the rooms (they can be swapped around later if needed.)&lt;/p&gt;   &lt;p&gt;After that, the scheduling can start, shown in the second half of the picture to the right. Each empty slot can be assigned a paper from the shortlist for the relevant topic. That way it's easy to &amp;quot;paint on&amp;quot; talks into each room and quickly get a sense for the overall flow of the conference.&lt;/p&gt;   &lt;p&gt;Once it was time to finalize matters, I mass-marked all the scheduled papers as accepted, which automatically sent a notification to the presenters, using the same request system as for reviewers. When a speaker confirms, their proposal status changes and they appear in the final &lt;a href="http://xtech.expectnation.com/event/1/public/schedule/grid"&gt;public grid&lt;/a&gt;. From there, I am able to use the mailroom again to inform speakers of the information they need to know. Additionally, speakers can log into the system at any time to see when they've been scheduled to speak.&lt;br /&gt;  &lt;/p&gt;   &lt;p&gt;Gridding out the conference in Expectnation is probably the biggest timesaver of all. Previously this involved a lot of sketching on paper or a spreadsheet, and a lot of manual work notifying people, and then more work creating the timetable to go on the web site. Now, both the grid and a &lt;a href="http://xtech.expectnation.com/event/1/public/schedule/full"&gt;full web of abstracts and speaker details&lt;/a&gt; are generated automatically.&lt;/p&gt;  &lt;h3&gt;What next?&lt;/h3&gt;  &lt;p&gt;As you can probably tell, I'm rather excited about both XTech 2007 and also about the work we're doing with Expectnation.&lt;/p&gt;   &lt;p&gt;What's next for XTech is the process of publicising the conference among attendees, recruiting session moderators, and also the writing of papers by the presenters. As the conference draws nearer, the attendee-level interactive features of Expectnation will kick in, allowing personal scheduling and rating of sessions.&lt;/p&gt;   &lt;p&gt;What's next for Expectnation is that we're ramping up to our 1.0 launch. We're working with a handful of early adopter customers right now, and are always interested in new use cases. As we get nearer the end of the first tranche of engineering work, we're going to gear up the publicity effort and start explaining to the world why we're special.&lt;/p&gt;   &lt;p&gt;As usual, I'd &lt;a href="mailto:edd-web@usefulinc.com"&gt;love to hear&lt;/a&gt; questions, feedback and suggestions.&lt;/p&gt;  &lt;p&gt;&lt;a href="http://times.usefulinc.com/2007/02/23-xtech#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2006/12/20-xtech-deadline">
    <title>Deadlines to focus the mind</title>
    <link>http://times.usefulinc.com/2006/12/20-xtech-deadline</link>
    <description>Douglas Adams may have loved the sound of them as they whooshed by, but a conference organizer can't live without them.</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2006-12-20T12:40:49Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded> &lt;p&gt;Here is a graph showing the number of proposals sent in for &lt;a href="http://2007.xtech.org/"&gt;XTech 2007&lt;/a&gt; over the last two weeks.&lt;/p&gt; &lt;p&gt;&lt;img width="379" height="228" alt="Proposals submitted for XTech" src="http://times.usefulinc.com/asset/name/16/xtech-graph.png" title="Proposals submitted for XTech" /&gt;&lt;/p&gt;&lt;p&gt;The actual deadline date is the highest bar. The Monday after, when everybody realised they'd missed the deadline, is the second highest bar. Of course, it's an open secret that tech conferences regularly extend their deadlines to account for such things. I am probably stricter than most programme chairs in this respect.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;This year we &lt;a href="http://xtech.expectnation.com/event/1/public/content/2006/12/20-cfp-over"&gt;got over 200 proposals&lt;/a&gt;. That means over three proposals to each slot, so choosing's going to be tough.&lt;/p&gt;&lt;p&gt;This graph is one of the bits of helpful eye candy &lt;a href="http://www.expectnation.com/"&gt;ExpectNation&lt;/a&gt; gives me. As the conference organization proceeds I'll publish some other interesting details about the inner workings of XTech.&lt;/p&gt;&lt;p&gt;Meanwhile, I'm overwhelmed as usual with the quality of conference submissions, and will enjoy the task of reading each one this week.&amp;nbsp;&lt;/p&gt; &lt;p&gt;&lt;a href="http://times.usefulinc.com/2006/12/20-xtech-deadline#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
  <item rdf:about="http://times.usefulinc.com/2006/11/02-xtech-cfp">
    <title>XTech 2007 is go!</title>
    <link>http://times.usefulinc.com/2006/11/02-xtech-cfp</link>
    <description>I've just published the call for participation for XTech 2007.  Hurry there now and get involved!</description>
    <dc:subject>xtech</dc:subject>
    <dc:subject>expectnation</dc:subject>
    <dc:creator>Edd Dumbill</dc:creator>
    <dc:date>2006-11-02T19:34:24Z</dc:date>
    <foaf:maker>
      <foaf:Person>
        <foaf:mbox rdf:resource="mailto:edd@usefulinc.com"/>
      </foaf:Person>
    </foaf:maker>
    <content:encoded>&lt;p&gt;I've just published the &lt;a href="http://xtech.expectnation.com/event/1/public/content/2006/10/31-cfp-open"&gt;call for participation&lt;/a&gt; for &lt;a href="http://2007.xtech.org/"&gt;XTech 2007&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;The theme for this year&amp;rsquo;s conference is &amp;ldquo;The Ubiquitous Web&amp;rdquo;. As the web reaches further into our lives, we will consider the increasing ubiquity of connectivity, what it means for real world objects to be connected with the web, and the increasing blurring of the lines between virtual worlds and our own.&lt;/p&gt;&lt;p&gt;XTech will have its usual &lt;a href="http://xtech.expectnation.com/event/1/public/content/tracks"&gt;four tracks&lt;/a&gt;: &lt;a href="http://xtech.expectnation.com/event/1/public/content/tracks#apps"&gt;Applications&lt;/a&gt;, &lt;a href="http://xtech.expectnation.com/event/1/public/content/tracks#browser"&gt;Browser Technologies&lt;/a&gt;, &lt;a href="http://xtech.expectnation.com/event/1/public/content/tracks#core"&gt;Core Technology&lt;/a&gt;, &lt;a href="http://xtech.expectnation.com/event/1/public/content/tracks#opendata"&gt;Open Data&lt;/a&gt;. Keynotes addresses will be given by Adam Greenfield, author of &amp;ldquo;Everyware: The Dawning Age of Ubiquitous Computing&amp;rdquo;, Gavin Starks of Global Cool and designers of the future Matt Webb and Jack Schulze.&lt;/p&gt;&lt;p&gt;Head over to the &lt;a href="http://xtech.expectnation.com/event/1/public/cfp"&gt;call pages&lt;/a&gt; and submit your proposal. The deadline is 15 December 2006. The conference itself is in Paris, France, 15-18 May 2007.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Expectnation&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;The publication of the XTech call is doubly exciting for me. XTech 2007 will be the first conference to be managed completely from &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt;, the software I've been building over the course of the last year.&lt;/p&gt;&lt;p&gt;Expectnation is a web-based system for managing conferences and training events. Right now we're conducting tests with some customers, and are working hard on readying the system for a public trial.&lt;/p&gt;&lt;p&gt;The particular strengths of Expectnation include the management of speakers, proposals and delegates. If you would like to stay informed of our progress, there's a place to sign up for news on the &lt;a href="http://www.expectnation.com/"&gt;Expectnation&lt;/a&gt; home page.&lt;/p&gt;&lt;p&gt;&lt;a href="http://times.usefulinc.com/2006/11/02-xtech-cfp#disqus_thread"&gt;Join the conversation about this post&lt;/a&gt;&lt;/p&gt;</content:encoded>
  </item>
</rdf:RDF>
