Actually, I recall this has been discussed previously (providing
Enclosure-like support) [1 for an example] which eventually pointed up
the PaceLinkRelated[2] which covered much of the same ground. But
your proposal raises a few questions/comments on my part:
1) There has been some controversy as to the "arbitrary" restriction
of one enclosure per item in RSS. Should we duplicate that
restriction? If so, why?
2) Why not have an 'image' link in an entry? I recall discussion of
using <content src="..."%gt; or somesuch for graphics, but has a
Flikr-like usecase been discussed? Using an 'image' link and regular
content seems appropriate.
3) On the 'size' attribute. 'size', 'length' and 'content-length'
have been proposed ('length' is in the PaceLinkRelated [2]. I prefer
(content-)length, as size appears ambiguous.
4) Perhaps we could add a 'dimension' attribute for images? kidding.
Lance
[1] http://www.imc.org/atom-syntax/mail-archive/msg03805.html
[2] http://www.intertwingly.net/wiki/pie/PaceLinkRelated
On Wed, 05 Jan 2005 13:36:06 -0800, Tim Bray <[EMAIL PROTECTED]> wrote:
>
> There are a couple of areas where we don't quite have feature parity
> with RSS2.0, this tries to address that:
> http://www.intertwingly.net/wiki/pie/PaceEnclosuresAndPix -Tim
>
>
