* Bill de hÓra <[EMAIL PROTECTED]> [2005-07-11 17:55]: > [[[ > Interoperability considerations: Some existing agents and feeds > that support the Atom 0.3 specification make use of this media > type despite Atom 0.3 not being compatible with Atom 1.0. Such > feeds SHOULD be considered invalid Atom 1.0. > ]]]
-1 first and foremost because of the SHOULD. I don’t see how anything less than a MUST can be justified. Even if that was changed, though, -1 anyway. The only reason we’ll probably have 0.3 feeds in the wild for a while to come is that MovableType users seem to be upgrade-lazy. (I still frequently encounter MT 2.x installs with x as low as 5, whereas I don’t remember the last time I stumbled across a site still running WordPress <1.5.) Most everyone else who did not craft their feed themselves will have it taken care of either by their host or by their vendor’s next release, and those who craft it themselves will fix it in short order anyway. (I know I intend to as soon as my aggregator can eat it, and their effort for that is already underway.) However, the likelihood for sites with old MT installs to be offering *only* an Atom 0.3 feed but no RSS (1.0|2.0) feed is vanishingly small anyway, so even if all aggregators dropped support for 0.3 tomorrow, very few people would actually be affected worse than having to resubscribe some sites. The worst to happen with an aggressive deprecation strategy is that there’ll be a somewhat annoying transitory period of a few months before aggregators and producers all support the new spec in unison. So in light of these and Robert’s arguments, there’s no apparent reason to attempt to interoperate. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
