[
Lists Home |
Date Index |
Thread Index
]
The breakage was small (as you say) short-lived and easily fixed. In a
corner-turn like this one there have to be *some* mistakes. There was one,
at first we made RSS itself a namespace. I had Scripting News set up that
way for a couple of weeks so people could test, but of course some people
didn't see it and didn't report the breakage. When we flipped the switch on
Radio's serializer, that's when the breakage showed. We pulled back RSS
being a namespace, and the outage cleared. Dave
----- Original Message -----
From: "bryan" <bry@itnisk.com>
To: "'Dave Winer'" <dave@userland.com>
Cc: <xml-dev@lists.xml.org>
Sent: Thursday, October 10, 2002 2:34 AM
Subject: RE: [xml-dev] Great piece on RSS
>
> >They *are* one format Bryan -- and designed to be that way. A 0.91 file
> is
> >also a valid 0.92 file which is also a valid 2.0 file. This has a very
> >important practical feature -- it means that current aggregators can
> read
> >the new format. That seems to be borne out, btw, our 2.0 feeds are
> being
> >read by aggregators that know nothing about 2.0. No problems to report
> so
> >far. (Praise Murphy.)
>
> I've seen a couple of people complaining that their home-rolled RSS
> consumers broke, complaints were on weblogs that I rolled to from
> scripting.com so I figured you probably saw them to, guess I was wrong,
> they were written in xslt; I looked at the xslt and saw of course as I
> expected that the breakage was caused by the namespace - i.e
> blogChannel, these were of course not complex things to fix, but it was
> breakage. If you have some xml aware processing doing your consuming
> such annoying little breakages might become par for the course. Of
> course if the consumption is being done by a Perl script with Regex
> things should be fine. I prefer xml aware processing, guess that shows
> my intellectual deficiencies somewhere.
>
>
>
|
