<?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/index.jsp?blogger=vladimir">
    <title>Vladimir Ritz Bossicard's Weblog</title>
    <description>
Pragmatic JUnit Testing
    </description>
    <link>http://www.artima.com/weblogs/index.jsp?blogger=vladimir</link>
    <image rdf:resource="http://www.artima.com/images/artima88x33.gif" />
   <items>
      <rdf:Seq>
        <rdf:li resource="http://www.artima.com/weblogs/viewpost.jsp?thread=4603" />
      </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=4603">
    <title>The Third State of your Binary JUnit Tests</title>
    <link>http://www.artima.com/weblogs/viewpost.jsp?thread=4603</link>
    <description>
Passing or failing: these are the usual states of JUnit tests.  But discover a third state that many use but only few acknowledge, and how you can elegantly manage these tests with JUnit-addons Runner. (From Vladimir Ritz Bossicard's Weblog)
    </description>
  </item>

</rdf:RDF>
