<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns="http://purl.org/rss/1.0/">
  <channel rdf:about="http://bitworking.org/Aggie.html">
    <title>Aggie News</title>
    <link>http://bitworking.org/Aggie.html</link>
    <description>Aggie: The open source desktop news aggregator from Bitworking.</description>
    <sy:updatePeriod>daily</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

    <items>
      <rdf:Seq>
        <rdf:li resource="http://bitworking.org/Aggie.html" />
        <rdf:li resource="http://bitworking.org/Aug2002.html#X631650869538886448" />
        <rdf:li resource="http://bitworking.org/2002/06/02.html#a177" />
        <rdf:li resource="http://bitworking.org/Aggie.html" />
      </rdf:Seq>
    </items>
  </channel>

  <item rdf:about="http://bitworking.org/Aggie.html">
    <title>Aggie RC5</title>     
    <link>http://bitworking.org/Aggie.html</link>
    <description>
<![CDATA[
<p>I am pleased to annouce the release of <a href="http://bitworking.org/Aggie.html">Aggie 1.0 RC5</a>. </p>
            <p>Special thanks to: <a href="http://pocketsoap.com/weblog">Simon Fell</a>, <a href="http://perceive.net">
                    Eric Vitiello Jr.</a>, <a href="http://radio.weblogs.com/0106548/">Ziv Caspi</a>,
                <a href="http://almostperfect.editthispage.com/">Ingve Voremstrand</a>, <a href="mailto:Tim.Danner@netiq.com">
                    Tim Danner</a>, and everybody that has submitted bug reports and 
                enhancement requests.
            </p>
            <h2>Aggie RC5 Changes</h2>
            <h3>Improvements in Feed Retrieval</h3>
            <dl>
                <dt>HTTP Compression</dt>
                <dd>
                    Added support for HTTP compression. [Simon Fell]</dd>
                <dt>RssHarvest</dt>
                <dd>
                    Aggie can now be taught how to 
                    transform any structured web page into an RSS feed. This is useful for sites 
                    that produce content in an orderly fashion, but publish no RSS feeds of their 
                        own (such as MSDN). See <a href="RssHarvest.html">here</a> for details [Ziv Caspi]</dd>
                <dt>XSLT transformation of XML documents into RSS feeds</dt>
                <dd>
                    Aggie can also directly transform XML content into RSS feeds if you provide it 
                    with a proper XSLT transform. To subscribe to a feed whose URL is
                    <i>xmlurl</i> and whose transform into RSS is <i>xslurl</i>, use the following
                    URL: <b>xslt:?xmlfile=<i>xmlurl</i>&amp;xslfile=<i>xslurl</i>&amp;title=<i>feedTitle</i></b>.
                    [Ziv Caspi]</dd>
            </dl>
            <h3>Improved Output</h3>
            <dl>
                <dt>Output Items as SMTP Messages</dt>
                <dd>
                    Optionally, Aggie can send SMTP mail messages to your Email account. You can 
                    have each new item in its own message, all new items in a given feed in a 
                    single message, or all new items in a given feed with the same title in a 
                    single message. See <a href="Emailer.html">here</a> for details. [Tim Danner, Ziv Caspi]</dd>
            </dl>
            <h3>Improved RSS Parsing and Vocabulary</h3>
            <dl>
                <dt>Robust and extensible RSS parser</dt>
                <dd>
                    The RSS parser has been completely rewritten. It is now very robust, will let 
                    you know if the feed is not stricly XML but will still parse non-well-formed 
                    feeds (within reason). Additionally, it is extensible, so you can ask it to 
                    parse elements that it does not know about. [Ziv Caspi]</dd>
                <dt>"Shame into submission"</dt>
                <dd>
                    If the RSS parser finds a feed which is not strictly well-formed, but it still 
                    readable, it generates a detailed description of what is wrong with the feed, 
                    to help authors locate problems. [Ziv Caspi]
                </dd>
                <dt>New RSS elements supported</dt>
                <dd>
                    In addition to title, link, and description elements, Aggie now supports Dublin 
                    Core date, encoded content, CDATA descriptions, RDF encoded content, and 
                    Trackback pings. [Ziv Caspi]</dd>
                <dt>Support for base element</dt>
                <dd>
                    Aggie can now identify feeds that publish their "base", and automatically 
                    provide the proper HTML base element. This feature works only for mail output, 
                    and is most useful with RSSHarvest-ed feeds. [Ziv Caspi]</dd>
            </dl>
            <h3>Miscellaneous</h3>
            <dl>
                <dt>Bug fixes</dt>
                <dd>
                    Multiple bug fixes have been applies, which are too numerous to include here. 
                    [All]</dd>
            </dl>
]]>
    </description>
</item>


  <item rdf:about="http://bitworking.org/Aug2002.html#X631650869538886448">
    <title>Aggie RC4</title>     
    <link>http://bitworking.org/Aug2002.html#X631650869538886448</link>
    <description>
<![CDATA[
<p>I am pleased to annouce the release of <a href="http://bitworking.org/Aggie.html">Aggie 1.0 RC4</a>. </p>
<p>Special thanks to:
<a href="http://pocketsoap.com/weblog">Simon Fell</a>, <a href="http://perceive.net">Eric Vitiello</a>, <a href="http://radio.weblogs.com/0106548/">Ziv Caspi</a>, <a href="http://almostperfect.editthispage.com/">Ingve Voremstrand</a>, and everybody that has submitted bug reports and enhancement requests.
</p>
<h3>Highlights for the RC4 release</h3>
<dl>
<dt>Internationalization</dt>
<dd>    Aggie now has better support for international feeds.</dd>
<dt>  Proxy Support</dt>
<dd>    Now you can use Aggie with a proxy server.</dd>
<dt>  Stylesheets</dt>
<dd>    Aggie supports having different stylesheets
    to style the resulting HTML. Each stylesheet can have
    it's own configuration dialog and saved parameters.
    Here is a detailed explaination of how this system works.
    <a href="http://bitworking.org/HowTemplatesWork.html">How Templates Work In Aggie.</a></dd>
<dt>Speed Improvements</dt>
<dd>    There have been many improvements that help Aggie get the news
    faster. There is now support for the "If-Modified-Since" HTTP header,
    meaning Aggie will only download a file if it has changed since
    the last time it was retrieved. Also the HTTP Redirection header is 
    obeyed and stored to reduce the number of round trips retrieving files.
    In addition all this information is stored in a seperate file so that if
    you are using Aggie to read an OPML file from a remote site you still
    get all the speed enhancements.</dd>
<dt>Command-Line</dt>
<dd>Aggie now ships with a command line version of Aggie that can be
    used in background tasks.</dd>
<dt>Referer Logs</dt>
<dd>  Aggie now supports placing a link back to the users website
    in the referer logs. The genesis and explaination of this idea
    is documented on <a href="http://rss.benhammersley.com/archives/000059.html">Content Syndication with XML and RSS.</a>
   
    The page that the referer log entry points to is here (using bitworking.org
    as the example site)
<code><a href="http://bitworking.org/AggieReferrers.html?userWeblog=http://bitworking.org">http://bitworking.org/AggieReferrers.html?userWeblog=http://bitworking.org</a></code>
</dd>
</dl>
]]>
    </description>
</item>


  <item rdf:about="http://bitworking.org/2002/06/02.html#a177">
    <title>Aggie RC3</title>     
    <link>http://bitworking.org/Aggie.html</link>
    <description>
<![CDATA[
           Aggie 1.0 RC3 is available for download.

	   This is a big release for Aggie with a raft of big changes, including:
	   <dl>
	   <dt>Diff support</dt><dd>There is now an option to only show news items that have changed since
	          the last time Aggie did a scan.</dd>
       
       <dt>RSS Auto-Discovery</dt><dd>
           You can now enter a URL of a web page into the Add Channel box. 
	   If the web page supports RSS Auto-Discovery then Aggie will find
	   the RSS file.
	   For further reading: <a href="http://diveintomark.org/archives/2002/05/31.html#more_on_rss_autodiscovery">RSS Auto-Discovery</a>
	   Note: Aggie will look for and process BOTH mime types at this time, "text/xml" and "application/rss+xml"
       </dd>
       <dt>Drag-N-Drop</dt><dd>
       You can now drag-and-drop links off the browser and onto the Add Channel
       address box.</dd>
       <dt>ETag</dt><dd>
       Using HTTP/1.1 it is possible to get an ETag value everytime you get a 
       file. If this value is then supplied in a "If-None-Match" header
       when the file is retrieved again the server should not return the 
       file and instead return a Not Modified message. This speeds up 
       processing as only modified files are returned. This required adding
       a new 'etag' attribute to the OPML file format.
       For further reading: <a href="http://www.pocketsoap.com/weblog/2002/05/25.html#a544">ETag support</a>
       </dd>
       <dt>Syndic8 OPML</dt><dd>
       Aggie can now use the OPML files produced from <a href="http://www.syndic8.com">Syndic8</a>.
       Syndic8 supplies a 'text' element where Aggie is looking for a 'title'
       element. This fix is to look for 'title', if that fails look for
       a 'text' element.</dd>
       <dt>Aggie News</dt><dd>
          Created a separate news channel from bitworking.org just for Aggie news. 
	  Added that channel to the list of default channels that Aggie ships with.
	  <a href="http://bitworking.org/AggieNews.xml">(RSS)</a>
	  </dd>
	  </dl>
]]>
    </description>
    </item>
  <item rdf:about="http://bitworking.org/Aggie.html#install">
    <title>Aggie RC2</title>     
    <link>http://bitworking.org/Aggie.html</link>
    <description>
           Aggie 1.0 RC2 is available for download.

	   I have found and corrected a bug in Aggie RC1 
	   and also added one feature. The bug is in handling namespaces. 
	   Some RSS feeds, like Ugu Cei's RSS 1.0 feed have all the elements
	   namespace qualified. This is perfectly valid and it was a bug in 
	   Aggie that it was not able to parse his 1.0 RSS feed.
	   The enhancement is the addition of a 4th column to the display
	   which contains detailed error information for channels that 
	   do not process properly.
	   The same install instructions apply, but be careful if you have added 
	   files to myChannels.opml that you either back it up before installing 
	   Aggie 1.0 RC2 or make sure you do not extract myChannels.opml from the ZIP file.
    </description>
  </item>   
</rdf:RDF>









