Bob Wyman wrote:
Robert Sayre wrote:
HeadInEntry is trivial to do as an extension, so there's no reason to leave it in.
There are a number of excellent reasons to leave it in!
I totally disagree! But you can keep it! (see other mail :)
1. Just about the only functional "advantage" that Atom has over RSS is that HeadInEntry provides core support for aggregated feeds. If you're unwilling to innovate in even this one tiny spot, why the heck bother with this effort at all? Perhaps we should all join Dare over in RSS-land... With Microsoft being so anti-Atom, we need *some* argument for expending the effort and political capital needed to support this format!
We'll do a SOAP protocol and they can call it "Atom Indigo". Don't you think that sounds approproately cool but also banal? Besides, if you move to RSS-land, Dare will have to move somewhere else (XAML-land?) and call people morons from there.
We decided to support HeadInEntry. It doesn't make sense to back off now. Deferring HeadInEntry to a non-core extension essentially kills it and ensures that Atom use will provide virtually no advantage to anyone who is building aggregated feeds.
Oh, that's not true. No one will call you names when you build extensions, and there will always be titles, ids, and dates--like other formats that work.
Robert Sayre
