RE: [xml-dev] best practice for providing newsfeeds ?

["Joshua Allen" <joshuaa@microsoft.com>]

> liberal.  The question is whether this success will continue once
> serious businesspeople get into the act, when real money is at stake,
> when lots of people start syndicating information that is mostly
> processed by machines (calendars and schedules data that would be

OK, is it fair to paraphrase this argument as "RSS works fine today, but
Atom will enable you to be more flexible in seizing new opportunities
tomorrow?"  This is certainly the sort of argument that is directed at
businesspeople instead of techies, but it still comes across as FUD.  I
say FUD because the argument so far is unsubstantiated by any real-world
examples that would make someone at NYT pay attention.  And the converse
could easily prove true.

You also raise the point of "steeped in XML best practices", which is
probably fair to classify as a philosophical argument.  If we are
concerned about architectural purism, and want a way to exchange
calendar information (and it's not clear that there is customer demand
for RSS to do this anyway), I would argue that RDF iCal is the best
practice.  In fact, based on that I always thought that R(DF)SS 1.0 had
the unassailable high ground with respect to purity of practice (as
opposed to RSS's "loose consensus and running code").  For people
concerned about best practices, why would anyone abandon RSS 1.0 and
jump to Atom, especially when RDF parsers are *finally* becoming
widespread?  I hear Danny's unbridled optimism that "one day RDF will
work well with Atom", but we have heard that song and dance before.  Why
anyone who cared about RDF would abandon a perfectly good RDF-based
format in favor of a format that "might one day work great with RDF" is
beyond me.