Hi, I try to be precise in a generic and popularized RSS definition for non coders. RSS is an XML dialect. It can handle external namespaces declared by...
I've always found this mildly problematic. Ideally, you should be able to define a namespace for RSS and prefix the elements, but I imagine that would break...
... 1. The syntax which you might use for this actually undeclares the prefix. You can’t actually declare a prefix for the null namespace. 2. What would be...
If you wanted to use the null namespace for some other purpose, then you could prefix the RSS elements with a properly declared namespace prefix (in an ideal...
... I tried that with Atom, which *is* in a namespace, and even then most clients broke: http://plasmasturm.org/log/376/ The situation is greatly improved now...
I think there's two scenarios that exist with RSS vis-a-vis namespaces. -RSS elements in RSS documents -RSS elements in other XML documents 1. RSS elements in...
Dave Winer's original suggestion of a portable RSS format is now available here: http://www.rssboard.org/news/186 The original is gone from Harvard's blog...
... To give my opinion as an implementer: do we really need another feed format? Effectively, aggregators have support RSS 0.90, RSS 2.0, Atom 0.3, and Atom...
... RSS 2.0 is one of the most widely supported XML dialects in existence. That puts a lot of code out there that handles RSS elements and a lot of brains...
... But "title" and "{http://backend.userland.com/rss2}title" _aren't_ the same element, and the same goes for any other local name, and as such for anyone...
... Under that logic we don't need RSS at all. Atom does everything RSS does and is more precisely specified. Whenever anybody asks me which format they should...
... Atom happens to be in a namespace, and may therefore theoretically be more suited to solving this particular type of problem, but beyond the AtomPub...
Although I agree that using backend.userland.com might be a better solution, I'm not personally comfortable with hi-jacking their domain without permission....
I agree. Theoretically, any URL that provides the XSD should be legal, though. But as far as a recommendation, I think we should have our own URL. ... domain...
I think we should start with a discussion of which URL to use "IF" we decide to create namespace for RSS elements used in document other than RSS documents. ...
... Except, elements in a namespace and elements outside a namespace aren’t the same thing even if they have the same localname. So this proposal does not...
I'm not aware of any tools that expect XSDs at the namespace. In fact, namespaces don't have to be URIs, they can be any token. Convention is to put a human...
Both Visual Studio and SlickEdit will verify XML grammar against the XSD located at the URI, and both warn if that URI does not lead to a schema that can be...
... It doesn’t surprise me that SOAPy things show bias in their coverage of the data-vs-document spectrum of uses for XML. Regards, -- Aristotle Pagaltzis //...
After some further research: Visual Studio only generates a warning if the URI points to a file with extension .xsd that either cannot be opened or is not in...
Awesome! I think then that most of us are in agreement, we just need to decide whether to go with the userland or rssboard namespace. I'm going to start a...
... My concern is that, no matter what you say in the spec, you can be sure that people will start using that namespace in regular feeds. And when they do, I ...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
Offline 
Send Email