<?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 (Urbanscale)</title>
    <link>https://pinboard.in/u:Urbanscale/public/</link>
    <description>recent bookmarks from Urbanscale</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://alper.nl/dingen/2010/09/boris-bikes-are-made-of-epic-win/"/>
	<rdf:li rdf:resource="http://www.groupechronos.org/index.php/fre/blog/l-homo-mobilis-et-ses-risques"/>
	<rdf:li rdf:resource="http://code.google.com/transit/spec/transit_feed_specification.html"/>
	<rdf:li rdf:resource="http://2009.dconstruct.org/podcast/networkedurbanism/"/>
	<rdf:li rdf:resource="http://vagueterrain.net/journal13/crisis-fronts/01"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://alper.nl/dingen/2010/09/boris-bikes-are-made-of-epic-win/">
    <title>Alper.nl: Boris Bikes are made of epic win</title>
    <dc:date>2010-09-06T15:45:26+00:00</dc:date>
    <link>http://alper.nl/dingen/2010/09/boris-bikes-are-made-of-epic-win/</link>
    <dc:creator>Urbanscale</dc:creator><description><![CDATA[On best practices for bikesharing.]]></description>
<dc:subject>london cycling urbanism urbancomputing urbansystemsdesign transportation transmobility</dc:subject>
<dc:identifier>https://pinboard.in/u:Urbanscale/b:6ea173ba058d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:london"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:cycling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbanism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbancomputing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbansystemsdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:transportation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:transmobility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.groupechronos.org/index.php/fre/blog/l-homo-mobilis-et-ses-risques">
    <title>Groupe Chronos: L'Homo Mobilis et ses risques</title>
    <dc:date>2010-07-01T14:44:00+00:00</dc:date>
    <link>http://www.groupechronos.org/index.php/fre/blog/l-homo-mobilis-et-ses-risques</link>
    <dc:creator>Urbanscale</dc:creator><description><![CDATA[Bruno Marzloff - intelligent critique and extension of Georges Amar's thought, and my own.
]]></description>
<dc:subject>transmobility transportation transit mobility cities urbanism urbansystemsdesign</dc:subject>
<dc:identifier>https://pinboard.in/u:Urbanscale/b:ba6c6f844322/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:transmobility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:transportation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:transit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:mobility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:cities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbanism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbansystemsdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/transit/spec/transit_feed_specification.html">
    <title>Google Code: General Transit Feed Specification</title>
    <dc:date>2010-04-19T10:18:45+00:00</dc:date>
    <link>http://code.google.com/transit/spec/transit_feed_specification.html</link>
    <dc:creator>Urbanscale</dc:creator><description><![CDATA[So my question would have to be, who decided on the parameters of this specification? Is Google now in a position to tell transit operators how to structure their data (duh), or was there some existing semantics they picked up and extended?
]]></description>
<dc:subject>API google transit urbancomputing urbansystemsdesign</dc:subject>
<dc:identifier>https://pinboard.in/u:Urbanscale/b:cbeb787e79d5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:API"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:transit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbancomputing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbansystemsdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://2009.dconstruct.org/podcast/networkedurbanism/">
    <title>dConstruct 2009: Elements of a Networked Urbanism</title>
    <dc:date>2010-02-10T10:24:14+00:00</dc:date>
    <link>http://2009.dconstruct.org/podcast/networkedurbanism/</link>
    <dc:creator>Urbanscale</dc:creator><description><![CDATA[A heroic transcription of the talk I gave in Brighton last year. While revealing all my tics and weaknesses as a speaker, it's nonetheless not a bad effort.
]]></description>
<dc:subject>urbanism urbancomputing urbanplanning urbansystemsdesign cities infrastructure transit technology economics surveillance publicspace interactiondesign</dc:subject>
<dc:identifier>https://pinboard.in/u:Urbanscale/b:c9131e1e3bf9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbanism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbancomputing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbanplanning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbansystemsdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:cities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:transit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:surveillance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:publicspace"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:interactiondesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://vagueterrain.net/journal13/crisis-fronts/01">
    <title>Vague Terrain: Cognitive Maps and Database Urbanisms</title>
    <dc:date>2009-10-14T13:02:39+00:00</dc:date>
    <link>http://vagueterrain.net/journal13/crisis-fronts/01</link>
    <dc:creator>Urbanscale</dc:creator><description><![CDATA["These...logics and relationships...resist conventional forms of representation[,] and to operate within them requires the development of tools of analysis and design that account for the multiplicities of scale and complex logics that are found within the contemporary city."
]]></description>
<dc:subject>urbanism architecture maps designingdesign urbancomputing urbansystemsdesign complexity politics</dc:subject>
<dc:identifier>https://pinboard.in/u:Urbanscale/b:8eeab8d1452e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbanism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:designingdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbancomputing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:urbansystemsdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Urbanscale/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>