Namespace undefined
0xDECAFBAD:
And your conclusion would likely be correct. I
disagree. To help illustrate the point, I've made a change to
the namespace in my rss2
feed. Is it valid according to the specification?
I don't know. If so, it would be very more
difficult to write an
XSLT based aggregator which could handle the potentially
infinite number of possible namespaces apparently permitted by the
spec.
RSS 1.0 has been free of such discontinuities. Title has always been required. The namespace has always been specified. As you said, This is an issue of versioning, understanding the technology's implications, and reverse-compatibility
Similar to the statement that I said about the change in title, adding namespaces to the RSS 2.0 spec was a was a bold step that may break a number of assumptions that tools were making, but mades possible a large number of innovations and creativity.