Herbert van de Sompel wrote:
The Atom use cases we refer to use Entries as containers to provide
"metadata" about some web resource other than the Entry itself. For
example, the GData Entry
<http://gdata.youtube.com/feeds/api/videos/S_bcAOlK0io > is about the
YouTube video by the Cribs <http://www.youtube.com/watch?v=S_bcAOlK0io>
My impression upon looking at the entry is that you could do this
instead (and add an atom:summary element with textual content):
<content src="http://www.youtube.com/watch?v=S_bcAOlK0io"; />
What that would do is incorporate the YouTube video as part of the
entry. That would seem the appropriate method if you want the entry
metadata to talk about the external resource.
If the content of the entry is commentary about an external resource,
then I could see having an "about" link relation to indicate that, but
then the entry metadata would be talking about the entry, not the
external resource.
> We understand that an RFC that specifies the proposed rel="about"
> relationship would have to express which child elements of atom:entry
> pertain to the resource described by the Entry, and which to the Entry
> itself, whenever a rel="about" is present in an Entry.
The idea of a link relation changing the meaning of a core Atom element
doesn't sound right to me.
Antone
