<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (bkerr)</title>
    <link>https://pinboard.in/u:bkerr/public/</link>
    <description>recent bookmarks from bkerr</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://www.djangoproject.com/weblog/2010/mar/09/django-1_2-release-schedule/"/>
	<rdf:li rdf:resource="http://liftlab.com/think/nova/2009/12/14/transportation-system-information/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+NicolasNova+%28Pasta%26Vinegar%29"/>
	<rdf:li rdf:resource="http://goodspeedupdate.com/2007/2145"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.djangoproject.com/weblog/2010/mar/09/django-1_2-release-schedule/">
    <title>Django | Weblog | Django 1.2 release schedule</title>
    <dc:date>2010-03-10T14:31:20+00:00</dc:date>
    <link>http://www.djangoproject.com/weblog/2010/mar/09/django-1_2-release-schedule/</link>
    <dc:creator>bkerr</dc:creator><description><![CDATA[Although Django's release cycle is generally date-based, we also try to keep our release dates flexible to account for bugfixing time. At the beginning of the development sprints at PyCon a few weeks ago, over 300 tickets were still open on the Django 1.2 milestone. Now it's down to 120 (we've been clearing out, on average, about ten tickets a day), but that's still a lot more than we're comfortable shipping; as a result, we're pushing back the final 1.2 release a bit.]]></description>
<dc:subject>django release schedule</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:bkerr/b:8b0a14806654/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:django"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:release"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:schedule"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://liftlab.com/think/nova/2009/12/14/transportation-system-information/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+NicolasNova+%28Pasta%26Vinegar%29">
    <title>Pasta&amp;Vinegar » Blog Archive » Transportation system information</title>
    <dc:date>2009-12-14T14:36:38+00:00</dc:date>
    <link>http://liftlab.com/think/nova/2009/12/14/transportation-system-information/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+NicolasNova+%28Pasta%26Vinegar%29</link>
    <dc:creator>bkerr</dc:creator><description><![CDATA[ The poster describes what the user needs (obviously, a phone and a service that allows to scan QR code), the different steps to make it work (I like the “Confirm the Internet connection” phase) and a warning that you should check with your mobile phone carrier what would be the price of such transaction. As usual with technological innovations, the stake-holders try to help potential users and give a large amount of details that make the poster as long as the schedule poster. Of course there are two supposed expectations from this long description: (1) Teaching people how to use a technical objects (the QR code scanning process that can help to get real-time information), (2) Once the lesson learned it will be OK to remove this description and only keep the two QR codes.]]></description>
<dc:subject>transit tram schedule qr code affordance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:bkerr/b:feaafe63bdff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:transit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:tram"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:schedule"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:qr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:affordance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://goodspeedupdate.com/2007/2145">
    <title>The Goodspeed Update » Blog Archive » Information Design and Public Transit</title>
    <dc:date>2009-01-04T23:00:41+00:00</dc:date>
    <link>http://goodspeedupdate.com/2007/2145</link>
    <dc:creator>bkerr</dc:creator><dc:subject>transit scheduling schedule information design</dc:subject>
<dc:identifier>https://pinboard.in/u:bkerr/b:1f909d8e9aab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:transit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:scheduling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:schedule"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:bkerr/t:design"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>