A reassuring post from Six Apart on why we need Echo. Reassuring
because I think several nails have been hit on the head here. With
a big hammer. Here are the bullets (to mix metaphors).
Why we need Echo
1. The RSS spec does not say how to encode content.
2. XML-RPC is severely lacking in internationalization (I18N) support.
3. Content is represented differently in an API than it is in a syndicated feed.
4. Confusion over elements.
5. No universally-supported and -defined extensions.
1, 4 and 5 are all symptomatic of how RSS and the Blogger/MetaBlog APIs are inadequately specified. According to Dave, 2. isn't an issue, in which case this too isn't adequately dealt with in the spec. I think the justification for a redesign/refactor/rebuild (rather than a patch-up of existing specs) is best evinced by 3 and 5. Reworking the whole lot to work consistently could potentially save a lot of application development time. Having proper support for extensions means application innovation can move forward, with common ground for all developers. The post is diplomatic on the politics, but does point to the way these specs are frozen. But with Echo we don't need to choose between a 1990's timewarp and being called funky.