Robert Sayre wrote:
>[snip]
> Looks like the IETF wants to publish a "proposed standard" explicitly
> designed to break a very popular implementation, with no technical
> reason. I think that speaks volumes about the IETF, its management,
> and the quality of its "individual" contributors.
>
"...explicitly designed to break a very popular implementation"!? Give
me a break. I've been purposefully judicious lately not to respond to
crap like this but given the Last Call status on the spec, I think
several very clear points need to be made:
1. My decision to use the attributes has absolutely nothing to do with
Microsoft's implementation. In fact, the attributes were introduced to
the spec *before* I knew any details about the Microsoft implementation.
Any claims to the contrary are false. Any claims that I *explicitly
designed* the extension to break a particular vendor implementation
borders on the downright absurd.
2. Microsoft's implementation is no more "broken" by the use of the
attributes than any other feed reader implementation that has not been
specifically modified to support the extensions. I use Liferea, it
can't do anything with the thr:count or thr:when attributes either. I
guess that means I "exlicitly designed" the spec to break Liferea as
well? Microsoft's implementation doesn't support multiple enclosures,
so I guess RFC4287 was "explicitly designed" to break their
implementation? Please, enough.
I asked Byrne Reese if he could load up Sam Ruby's personal blog feed in
IE7 and capture a screenshot. Sam's feed uses the thr:count and
thr:when attributes. IE7 worked as expected, properly ignoring the
extensions it does not understand.
http://www.snellspace.com/public/ie7screen.png
What's broken?
- James
