Erik Wilde wrote:
good point. i have not hey thought about how aggregation of aggregated feeds would work. i guess that for the second aggregator, the fact that it is aggregating an agggregated feed should not matter. but then the question is how to treat the <atom:source> and more specifically its via:via="" attribute. so i guess aggregation of aggregated feeds does need some special treatment. how about retaining all the <atom:source> children, but replacing the via:via="" attribute's value with the ID of the aggregated feed?
There should be one and only one atom:source element per entry, reflecting the original source of the entry. If you're aggregating an entry that already has an atom:source, that atom:source element should be left unchanged.
See section 4.1.2 of RFC4287: "atom:entry elements MUST NOT contain more than one atom:source element." And 4.2.11: "...by adding an atom:source child element, if it is not already present in the entry".
Regards James
