<?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 (infovore)</title>
    <link>https://pinboard.in/u:infovore/public/</link>
    <description>recent bookmarks from infovore</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.bbcelite.com/"/>
	<rdf:li rdf:resource="https://sambleckley.com/writing/lab-notebooks.html"/>
	<rdf:li rdf:resource="https://pmarsceill.github.io/just-the-docs/"/>
	<rdf:li rdf:resource="https://twitter.com/i/moments/1065556549542846464"/>
	<rdf:li rdf:resource="http://brendandawes.com/blog/gitbook"/>
	<rdf:li rdf:resource="http://www.crummy.com/writing/postcards/"/>
	<rdf:li rdf:resource="http://bonsaiden.github.com/JavaScript-Garden/#function.arguments"/>
	<rdf:li rdf:resource="http://tom.preston-werner.com/2010/08/23/readme-driven-development.html"/>
	<rdf:li rdf:resource="http://mediumexposure.com/rails-3-reading-material/"/>
	<rdf:li rdf:resource="http://snippets.dzone.com/posts/show/4274"/>
	<rdf:li rdf:resource="http://toolmantim.com/article/2008/1/22/merb_routing_in_0_5"/>
	<rdf:li rdf:resource="http://apidock.com/"/>
	<rdf:li rdf:resource="http://www.adaptivepath.com/blog/2008/08/20/pencil-and-paper-to-live-prototype-whered-the-wireframe-go/"/>
	<rdf:li rdf:resource="http://www.screensteps.com/"/>
	<rdf:li rdf:resource="http://chmox.sourceforge.net/"/>
	<rdf:li rdf:resource="http://prototypejs.org/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.bbcelite.com/">
    <title>BBC Micro Elite source code - BBC Micro Elite</title>
    <dc:date>2020-09-29T10:01:01+00:00</dc:date>
    <link>https://www.bbcelite.com/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["This site contains the original source code for Elite on the BBC Micro, with every single line documented and (for the most part) explained."

Assembly is, it turns out, dark, dark magic. This is a very impressive thing to pore over - like Lions' Guide, but for Elite.]]></description>
<dc:subject>games elite code programming documentation bbc archive history</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:b236241fae4a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:elite"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:bbc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:archive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:history"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://sambleckley.com/writing/lab-notebooks.html">
    <title>Lab Notebooks | Sam Bleckley</title>
    <dc:date>2020-07-22T21:53:02+00:00</dc:date>
    <link>https://sambleckley.com/writing/lab-notebooks.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[I actually write READMEs a bit like Sam describes - onwards, never erased, first-person diary accounts of what I'm trying, where I'm typing it, and what happened. But the case for pen is a good one. (Also: I enjoy Sam's writing).]]></description>
<dc:subject>labnotebooks notebooks writing software process documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:f069e859c727/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:labnotebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:notebooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pmarsceill.github.io/just-the-docs/">
    <title>Home - Just the Docs</title>
    <dc:date>2019-11-10T14:12:18+00:00</dc:date>
    <link>https://pmarsceill.github.io/just-the-docs/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["Just the Docs gives your documentation a jumpstart with a responsive Jekyll theme that is easily customizable and hosted on GitHub Pages." As used by the excellent update monome docs - this is a really great template for clear, searchable documentation. You still have to write the docs, of course, but this is a great format for that output.]]></description>
<dc:subject>documentation templates git github</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:ef2efc7bb4ff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:templates"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:github"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/i/moments/1065556549542846464">
    <title>@OskSta Bad North Tech</title>
    <dc:date>2018-11-22T13:00:02+00:00</dc:date>
    <link>https://twitter.com/i/moments/1065556549542846464</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Oskar Stålberg illustrates some of his work on Bad North. I love illustrations of software development through animation - captures the change-over-time aspect of code work.]]></description>
<dc:subject>badnorth games oskarstalberg illustration development software programming documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:70a81966462d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:badnorth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:oskarstalberg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:illustration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://brendandawes.com/blog/gitbook">
    <title>Brendan Dawes - Using a Git Repo to create a physical document of the work</title>
    <dc:date>2018-02-09T14:18:08+00:00</dc:date>
    <link>http://brendandawes.com/blog/gitbook</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["All my work is tracked through a Git repository — a way to track code changes over time, complete with comments on why something has changed or what that commit was about. In conduction with that I take timestamped screenshots. These two things combined — words and image — have the side-effect of creating a document of the making process. So with that in mind I have begun to take those words and images and compile them chronologically into small books, both for myself and the client, as an historical record of how something went from A to B." Very good. I really like (in general) the idea of Project Books.]]></description>
<dc:subject>brendandawes git documentation history</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:7bdc02f729ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:brendandawes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:history"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.crummy.com/writing/postcards/">
    <title>Roy's Postcards</title>
    <dc:date>2012-01-03T12:34:36+00:00</dc:date>
    <link>http://www.crummy.com/writing/postcards/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["It's 1981. Roy Richardson is a manager at a Los Angeles computer company. A devout Mormon, he has a two-year-old son, with two daughters yet to be born. He has a little over ten years to live.

I was that two-year-old and Roy was my father. I grew up without him, knowing the outlines of his life but not the details. In 2006, at my mother's house, I found three boxes of details." Leonard never fails to surprise and amaze. This is wonderful.]]></description>
<dc:subject>leonardr postcards family history writing documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:75db6197fbdc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:leonardr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:postcards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:family"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bonsaiden.github.com/JavaScript-Garden/#function.arguments">
    <title>JavaScript Garden</title>
    <dc:date>2011-04-17T10:05:26+00:00</dc:date>
    <link>http://bonsaiden.github.com/JavaScript-Garden/#function.arguments</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["JavaScript Garden is a growing collection of documentation about the most quirky parts of the JavaScript programming language. It gives advice to avoid common mistakes, subtle bugs, as well as performance issues and bad practices that non-expert JavaScript programmers may encounter on their endeavours into the depths of the language." This looks really, really good. Alas, unlike Phil, I'm still not quite fully up-to-speed on Prototypes, but it's a great piece of documentation nontheless.]]></description>
<dc:subject>javascript reference documentation programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:83471f6e72e3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tom.preston-werner.com/2010/08/23/readme-driven-development.html">
    <title>Readme Driven Development</title>
    <dc:date>2010-08-23T20:31:36+00:00</dc:date>
    <link>http://tom.preston-werner.com/2010/08/23/readme-driven-development.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["Consider the process of writing the Readme for your project as the true act of creation. This is where all your brilliant ideas should be expressed. This document should stand on its own as a testament to your creativity and expressiveness. The Readme should be the single most important document in your codebase; writing it first is the proper thing to do." I like this: after all, a README is basically the story you tell about your software. Why not write it before the software exists?
]]></description>
<dc:subject>documentation development readme process</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:a217822ad127/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:readme"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:process"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mediumexposure.com/rails-3-reading-material/">
    <title>Rails 3 Reading Material | Medium eXposure</title>
    <dc:date>2010-02-01T11:15:27+00:00</dc:date>
    <link>http://mediumexposure.com/rails-3-reading-material/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Great round-up of all the stuff out there about Rails 3. If you're as behind as I am on preparing for this, there's some really good stuff here; nice to have it all in one place.
]]></description>
<dc:subject>ruby rails rails3 documentation tutorials</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:c4179d2ff1e1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rails3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:tutorials"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://snippets.dzone.com/posts/show/4274">
    <title>pman -- create, print, save, view PDF man pages</title>
    <dc:date>2010-01-04T16:36:46+00:00</dc:date>
    <link>http://snippets.dzone.com/posts/show/4274</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["convert man pages into PDF documents and save them to a specified directory; (batch) print or view PDF man pages from the command line". Which is, you know, clever.
]]></description>
<dc:subject>man manpage programming documentation unix script shell utility</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:520bfc036fcc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:man"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:manpage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:script"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:shell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:utility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://toolmantim.com/article/2008/1/22/merb_routing_in_0_5">
    <title>Merb Routing in 0.5</title>
    <dc:date>2008-09-08T13:08:58+00:00</dc:date>
    <link>http://toolmantim.com/article/2008/1/22/merb_routing_in_0_5</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["Merb’s routing shiznits needs some serious documentation love. Whilst I have a shot at getting some proper docpatches together here’s an overview of how to use routing in Merb 0.5." Thank god for that - was finding Merb's docs a little patchy in places.
]]></description>
<dc:subject>merb routing ruby programming documentation</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:d66f9ba255a8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:merb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:routing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://apidock.com/">
    <title>Front page - APIdock</title>
    <dc:date>2008-08-27T14:29:17+00:00</dc:date>
    <link>http://apidock.com/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["APIdock is a web app that provides a rich and usable interface for searching, perusing and improving the documentation of projects that are included in the app." Handy.
]]></description>
<dc:subject>api reference documentation doc ruby rspec rails</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:629690086d9c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:doc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rails"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.adaptivepath.com/blog/2008/08/20/pencil-and-paper-to-live-prototype-whered-the-wireframe-go/">
    <title>adaptive path » blog » Peter Merholz » Pen(cil) and paper to live prototype - where’d the wireframe go?</title>
    <dc:date>2008-08-27T13:54:20+00:00</dc:date>
    <link>http://www.adaptivepath.com/blog/2008/08/20/pencil-and-paper-to-live-prototype-whered-the-wireframe-go/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["I think the role of the architecture diagram, user flow, and wireframe belongs very much after the fact, after we’ve sketched and prototyped an experience. Those are tools to document what has been agreed through sketching and prototyping. They are not the best means for solving challenging design problems." That seems like a good way of putting it.
]]></description>
<dc:subject>documentation ux userexperience design sketching prototyping wireframe making</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:d3e2ca050daf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:userexperience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:sketching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:prototyping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:wireframe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:making"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.screensteps.com/">
    <title>ScreenSteps</title>
    <dc:date>2008-01-17T16:08:31+00:00</dc:date>
    <link>http://www.screensteps.com/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["ScreenSteps brings simplicity to the labor intensive process of software documentation." Focusing on the screengrab, rather than video, as instruction tool. Could be a nice approach, especially if export is any good.
]]></description>
<dc:subject>help documentation creation tool application mac osx</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:7abdb44cd2d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:help"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:creation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:tool"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:application"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:osx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://chmox.sourceforge.net/">
    <title>Chmox - a Mac OS X CHM viewer</title>
    <dc:date>2007-04-11T07:58:14+00:00</dc:date>
    <link>http://chmox.sourceforge.net/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[CHM files - compiled HTML - are basically Windows Help files. You need something like this to view them on a Mac.
]]></description>
<dc:subject>mac osx application chm documentation reader</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:243ee98e3881/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:application"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:chm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:reader"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://prototypejs.org/">
    <title>Prototype Javascript Library easing the development of dynamic web applications</title>
    <dc:date>2007-01-18T23:02:33+00:00</dc:date>
    <link>http://prototypejs.org/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Prototype finally has its own website. About bloody time - but it&#39;s great to see it being supported so thoroughly.
]]></description>
<dc:subject>protoype javascript rails api documentation ajax js development programming</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:ac6796fe8ac5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:protoype"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:js"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>