Bob Wyman wrote:
The impact here is not just limited to APP implementations. If a new media type is defined, it will undoubtedly appear in other contexts as well. Given the current definition of the atom syntax, it is perfectly reasonable for an "aggregator" to treat a single entry as the semantic equivelant of a single-entry feed.
I don't agree. atom:source is optional, and even then that does not cater for situations where entries have been annotated downstream.
If a new media type is defined, such an application would end up having to be modified. That's not right... APP is not the only context within which Atom is used.
What matters is whether atom:feed is the only context within which atom:entry is used, and/or whether atom:entry is an atom:feed in masquerade. After who knows how many posts and having gone back to the RFC, as I see it, neither of those is true or supported by the spec. There'll have to be another rationale presented for not spinning out a new media type.
cheers Bill
