James Holderness wrote: > Thomas Broyer wrote: >> Compare their atom:[EMAIL PROTECTED]"self" and >> @type="application/atom+xml"]/@href, they'll point you to the "start" of >> the "list", the one whose author and copyright apply. > > On the whole I tend to agree, but since there isn't a "self" link in > either of the RSS formats and Mark would like this extension to be format > neutral, he would either have to introduce an equivalent element into the > spec or strongly suggest that RSS feeds include a "self" atom:link.
Maybe one more reason to use an atom:link instead of fh:prev... > Technically it isn't even required that all Atom feeds have such a link, > so either way it's something worth clarifying. Agreed. >> (Actually, author >> and copyright should really appear in "history feed documents" as well, >> aggregators shouldn't "apply copyright" from one document to other >> documents linked from it). > > Technically yes, but try and imagine how an aggregator might handle that > sort of thing. The feed may be made up of a collection of documents, but > from the user's point of view it's all just one big feed. A copyright > message is the sort of thing that would show up once in a properties > dialog for the feed, or somewhere in the header or footer in a "newspaper" > view. Hmm, right. > It's highly unlikely an aggregator would try and track multiple copyright > messages and display them on a per item basis. atom:rights at feed-level don't apply to its entries, just to the feed as it stands. If you want to grant/restrict rights at an entry-level, use the entry-level atom:rights. I can understand how an entry-level atom:rights could be presented to the end-user, but I can't imagine how it could be done for the feed-level atom:rights, given that it can change during the feed's "life". The only solution I can see is to store feed metadata on an atom:source inside each entry, so you can ask for the entry-level and feed-level atom:rights for each entry in your aggregator. > As for author, if you've got item-level author elements you should be ok, > but if there aren't, the aggregator is quite likely to take the last > feed-level author it received and apply it to all subsequent items. It can > be argued that that's a bug, but it's not unreasonable to imagine than > many aggregators might do such a thing unless explicitly told not to. Aggregators are more likely to copy/paste de feed-level authors into each entry and totally forget about feed-level ones. -- Thomas Broyer
