Hmmm...
Mirrors:
<link rel="..." href="..." type="...">
<x:mirror href="..." title="..." />
</link>
Alternates:
<link rel="..." href="..." type="..." x:group="alternate-group" />
<link rel="..." href="..." type="..." x:group="alternate-group" />
All-in-one example
The x:group attribute links the two alternates into a single grouping;
the x:mirror specifies the mirrors for each link. nf:follow="no" is my
Atom Link No Follow extension that tells clients not to automatically
download the enclosure. Dumb clients will see what amounts to the
current status quo, two different enclosures of different types. Smart
clients will see the mirrors, the grouping and the no-follow instruction.
<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>
Thoughts?
- James
