This is because it's a about link, i.e. the package info page , maybe we could add one other element which would be rdf:download and there is what your requesting, how does that sound ?

Well what's the point of linking back to the package homepage in relevance to the releases, it's the Release RSS feed we are taling about?

I think the about URL should go to page the has information ABOUT the specific release.  It just doesn't make any sense to be any other way.

It might be nice to also have another element which is an actual download link such as:

<rdf:download>http://pear.php.net/get/Structures_DataGrid-0.5.3.tgz</rdf:download>

To keep BC I'd rather like to keep the about as is, and maybe rather add that download idea, and about-release ...

I don't think we need to worry about backwards compatibility too much in this respect, and I like Andrew's suggestion.

Okey cool, I just assumed it had to be BC like the rest of PEAR ;)

So where changing the about tag and also adding the download tag, right ?

I was thinking of something like

Index: Common.php
===================================================================
RCS file: /repository/pearweb/include/Damblan/RSS/Common.php,v
retrieving revision 1.10
diff -u -r1.10 Common.php
--- Common.php  20 Mar 2004 17:35:39 -0000      1.10
+++ Common.php  28 Oct 2004 20:09:05 -0000
@@ -121,7 +121,7 @@
     function __addItems($list) {
         foreach ($list as $item) {
             $date = date("Y-m-d\TH:i:s-05:00", strtotime($item['releasedate']));
-            $node = $this->newItem($item['name'] . " " . $item['version'], "http://pear.php.net/package/" . $item['name'], $item['releasenotes'], $date);
+            $node = $this->newItem($item['name'] . " " . $item['version'], "http://pear.php.net/package/" . $item['name'] . "/download/" . $item['version'] . "/", $item['releasenotes'], $date);
             $this->addItem($node);
         }
     }

Yeah sounds, good, would do the trick for the about part, but what about what Andrew proposed regarding having a straight link to the .tgz of the package also ?

This bug has been fixed in CVS.

In case this was a documentation problem, the fix will show up at the
end of next Sunday (CET) on pear.php.net.

In case this was a pear.php.net website problem, the change will show
up on the website in short time.
 
Thank you for the report, and for helping us make PEAR better.

Implanted, <link> now links to the release info, plus I added a <download> tag with the info on the url to the .tgz for the  release