<?xml version="1.0" encoding="utf-8"?>

  <rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns="http://purl.org/rss/1.0/"
  >

  <channel rdf:about="http://www.artima.com/weblogs/feeds/bloggers/kevlin.rss">
    <title>Kevlin Henney's Weblog</title>
    <link>http://www.artima.com/weblogs/index.jsp?blogger=kevlin</link>
    <description>
Artima Weblogs is a community of bloggers posting on a wide range of topics of interest to software developers.
    </description>
    <image rdf:resource="http://www.artima.com/images/artima88x33.gif"/>
    <items>
      <rdf:Seq>
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=67178" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=8791" />
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=5432" />
      </rdf:Seq>
    </items>
  </channel>

  <image rdf:about="http://www.artima.com/images/artima88x33.gif">
    <title>Artima.com</title>
    <url>http://www.artima.com/images/artima88x33.gif</url>
    <link>http://www.artima.com/</link>
  </image>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=67178">
    <title>Code versus Software</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=67178</link>
    <description>
There is a subtle but useful distinction between code and software. Programmers write code: a formal plan of the software, expressing its intent in maximal detail. Software is the end product: in execution it is what the user perceives, interacts with and experiences. Sometimes this difference can be significant.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=8791">
    <title>The Taxation of Representation</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=8791</link>
    <description>
Be careful not to confuse the map with the territory. Presentation and representation are different concepts for different purposes. The everyday notation for many quantities, such as money or time of day, is not necessarily a good indicator of how they should best be represented in a program.
    </description>
  </item>

  <item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=5432">
    <title>Five Possible Things after Breakfast</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=5432</link>
    <description>
We were in the pub when Charles posed an NP-hard problem: &quot;How do you teach programmers style and elegance in code? I would like five points or properties that I can teach to my programmers.&quot; Trusty pints of Guinness in hand, Charles, Frank and I set about trying to find some kind of answer.
    </description>
  </item>

</rdf:RDF>
