Quoting Lindsley Brett-ABL001 [EMAIL PROTECTED]:
I have raised this question a few times. The issue is separating the
resource from its representation. A single resource (e.g. a football
game) may have many representations (audio only, slide show,
audio/video, etc.). We would need a more
* Lindsley Brett-ABL001 [EMAIL PROTECTED] [2005-11-07 15:05]:
In following with the example below, one idea I toyed with was
to include an ID attribute on the link. Links with the same ID
were different representations of the same resource:
Check the recent thread, particularly the discussion
* David Powell [EMAIL PROTECTED] [2005-11-07 15:45]:
I'm generally not a fan of adding attributes to atom elements
rather than using the proper extensibility constructs, but how
about something like this:
This has come up before, and drawbacks have been pointed out.
Again, see the previous
A. Pagaltzis wrote:
* J.B. Nicholson-Owens [EMAIL PROTECTED] [2005-11-07 06:40]:
I'd like to be able to tell the user's software that there are
multiple encodings of the same show, one in Ogg Vorbis, another
in FLAC, and a third in Speex.
The basic idea is simple:
link
It's in progress. A newborn tends to slow these things down a bit ;-)
Expect a draft by the end of the week.
A. Pagaltzis wrote:
The basic idea is simple:
link rel=enclosure type=audio/mpeg href=show.mp3 /
link rel=enclosure type=application/ogg href=show.ogg /
link
