James M Snell wrote:
<link rel="enclosure" href="http://example.com/softwarepackage.zip";
type="application/zip" x:group="software-package" nf:follow="no">
<x:mirror href="http://example2.com/softwarepackage.zip";
title="California Server" />
<x:mirror href="http://example3.com/softwarepackage.zip"; title="European
Server" />
</link>
<link rel="enclosure" href="http://example.com/softwarepackage.tar.gz";
type="application/x-gzip" x:group="software-package" nf:follow="no">
<x:mirror href="http://example2.com/softwarepackage.tar.gz";
title="California Server" />
<x:mirror href="http://example3.com/softwarepackage.tar.gz";
title="European Server" />
</link>
I'm not quite clear how the nofollow attribute is supposed to work here. If
a feed producer wants to allow automatic downloads, but is providing the
file in multiple formats (only one of which is needed) how should that be
expressed? As you have it at the moment, the client can't auto-download at
all. Should he just leave nofollow off and rely on the client to download
only one?
Also, assuming the title on the main link is supposed to describe the
download file itself, there appears to be no way to inform the user of the
mirror location of the main URI. Without a location name of some sort, the
user can't make an informed decision about which mirror would be best to
use. Perhaps something along the line of Antone's "label" suggestion might
help here.
Regards
James
