On 24 Oct 2005, at 22:59, A. Pagaltzis wrote:
* Antone Roundy <[EMAIL PROTECTED]> [2005-10-24 22:35]:
Interesting. Filling an attribute with a list of URIs doesn't
really appeal to me though.
+1000000 (me and all my co-voting cats)
How about this:
<link rel="enclosure" type="audio/mpeg" href="http://example.com/
file.mp3" xml:id="x-file">
<altlink:mirror href="http://www2.example.com/file.mp3"; />
<altlink:mirror href="http://www3.example.com/file.mp3"; />
</link>
It’s a lot more verbose and you have to fiddle with nesting.
What do you get in return? “It looks more XMLish”?
yes!? We are using xml!
Sounds good, but you may have noticed above that I used a
prefix not specific to enclosures--there's no reason to tie
this all to one particular type of link (nor to make it look
as if it were tied to one specific link type). So the other
link might, for example, be:
I don’t know if striving for generality in this fashion without
a practical need is worthwhile. It smells of architecture
astronautics for a reason I can’t particularly pinpoint. So maybe
my instinct is wrong.
maybe :-)
A million cats can't be wrong.
Note that I changed "alternative-to" to "primary" just because
it's shorter and one word.
Works for me.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
