pete (archive)
Usenet Archive
- Joined
- Jun 1, 2000
- Messages
- 6,981
- Reaction score
- 0
I've been playing with writing my own RSS reader (in Ruby -- yes, I know there are lots out there, but it's mostly for my own experience and amusement). I tailored it to read the XML from the BBC feeds, but it's been happy with others as well (occasionally needing minor tweaking because of missing elements).
For interest, though, I downloaded a 'Have Your Say' forum RSS feed, again from the BBC, and initially all I got in the HTML conversion was a bunch of little titles, all the same... [That similarity was expected because they're just the title of the thread.]
When I looked in detail at the source, I saw that, first, the 'description' element was in CDATA form, which my reader wasn't set up for. I suppose this makes sense, because some of the descriptions included HTML tags. (Though looking at the 'XML FAQ' I see that the contents of CDATA are
*not* supposed to be inviolate from translation into entities, so I gather that if I was using say XSLT for the conversion it wouldn't work right anyway.)
However, the other strangeness was that important items like the author and creationDate were in the 'jf:' namespace ("JiveSoftware"). This meant that I had to specifically add these tags to my reader to be able to see this data. (The <item>s didn't have any <pubDate> element at all.)
Isn't this sort of against the intent of RSS? Is this a case of proprietary selfishness, or is there some good reason for using a namespace to handle important generic parts of the content? I see that some other feeds use 'itunes:' or other spaces, but they seem to be for more specific data and don't really impact reading by an app that doesn't know about them.
-- Pete --
For interest, though, I downloaded a 'Have Your Say' forum RSS feed, again from the BBC, and initially all I got in the HTML conversion was a bunch of little titles, all the same... [That similarity was expected because they're just the title of the thread.]
When I looked in detail at the source, I saw that, first, the 'description' element was in CDATA form, which my reader wasn't set up for. I suppose this makes sense, because some of the descriptions included HTML tags. (Though looking at the 'XML FAQ' I see that the contents of CDATA are
*not* supposed to be inviolate from translation into entities, so I gather that if I was using say XSLT for the conversion it wouldn't work right anyway.)
However, the other strangeness was that important items like the author and creationDate were in the 'jf:' namespace ("JiveSoftware"). This meant that I had to specifically add these tags to my reader to be able to see this data. (The <item>s didn't have any <pubDate> element at all.)
Isn't this sort of against the intent of RSS? Is this a case of proprietary selfishness, or is there some good reason for using a namespace to handle important generic parts of the content? I see that some other feeds use 'itunes:' or other spaces, but they seem to be for more specific data and don't really impact reading by an app that doesn't know about them.
-- Pete --