Hey Danny, we're working on it.
And I agree with your point. You're right, no one
on RSS-DEV list was clamoring for RSS 2.0. They were happy with the status quo.
I even think I understand why.
However, if we can maneuver it so that it's safe
for UserLand to ship a Radio that uses namespaces, it may have the effect of
pulling through an upgrade of XML parsers out there in the AggregatorLand, even
the one-offs, and that would be good for everyone, n'est-ce pas.
In other words, stick around, we may be on the
verge of nailing it.
----- Original Message -----
Sent: Saturday, September 28, 2002 10:27
Subject: RE: [RSS2-Support] Re: Summary
of issue with xmlns attribute
I support your position, and I wish the
community would adopt it as well. But no vendor should step out and have to
support this situation. No vendor in his right mind will.
However that said, there's a big distinction
between Radio not including the xmlns attribute on the rss element, and it
being removed from RSS 2.0. Rado is just a product. Once this is sorted out,
and I hope it happens soon, and we won't be subject to stump speeches and
declarations of broken-ness (see Sam Ruby's weblog), maybe we'll be able to
bring it back.
But the community has to manage the
politics. It's totally a political thing. I can't let UserLand be the
scapegoat for this stuff. Can't do it.
Oh, come on - it wasn't the community that pushed
out RSS 2.0, and that's the stuff that's caused the problem. I'm happy to help try and move things
forward, as are a lot of other people, despite major misgivings about the
course of recent events. Ok, don't let UserLand be the scapegoat for this stuff
either - accept a bit of responsibility for your own actions, and either do what you can to help fix
things or drop 2.0 altogether.
unsubscribe from this group, send an email
use of Yahoo! Groups is subject to the Yahoo! Terms of Service.