A. Pagaltzis wrote:
And with that, getting back to your question, the answer seems
pretty clear: it depends on whether the extension element is more
like atom:contributor, ie defines a property which an entry may
or may not have, or more like atom:author, ie defines a property
that every entry inevitably has.
But because that is a matter of interpretation, I would strongly
prefer to say that if the extension does not specify a meaning
for an element at the feed level, then the meaning is undefined.
On the other, related point, the same principle of avoiding the
necessity of complicated override mechanisms is why I say that
aggregators should assume that unknown extension elements (which
therefore have *unknown* as opposed to *undefined* semantics)
pertain only to the feed, not to its entries.
Ok, I retract my earlier comment about apps not making any assumptions
about unknown extensions. This is better.
Regarding Bob Wyman's separate note about what aggregators like pubsub
should do, If the aggregator is generating the source element, the
aggregator should include everything it finds in the feed.. even if it
does not understand it. If the entry already contains a source element,
leave it as is.
- James
