On 11/1/05 6:59 AM, "Danny Ayers" <[EMAIL PROTECTED]> wrote:
> Ok, I don't think there is any benefit in the normal case (feed ::=
> meta, (meta, content)*), but the recursive nesting method makes it
> possible to convey information about relationships between feeds.
> Which begs the questions:
>
> How useful are the semantics of one feed containing another?
> How desirable is it to convey such information in Atom format?
Would not the element set which describes a resource be an entry, regardless
of whether that resource is an html page, image/jpg, rss 0.91 feed, atom
feed, etc?
With our <link> element, we are able to clearly communicate that a resource
we link to is of type application/atom+xml.
Surely, if someone wanted to build the equivalent of an OPML file in Atom
format, they could do so simply by creating an entry for each feed ... where
any of those feeds could also be of the same OPML equivalent class, thus
giving you deep nesting if you really want it. Alternatively, shallow
nesting is possible by the presence of multiple <link> elements within an
entry, possibly with @rel="DC.refined" or whatever the DC term is.
I note that the Nature Publishing Group already have something similar:
http://npg.nature.com/pdf/newsfeeds.rdf
e.
