- So I'm thinking that since there are all sorts of cool callbacks in the
radio process, it shouldn't be too hard to knock out the review meta
data spec (http://www.pmbrowser.info/wiki.pl?RVW) as a plugin.
But I've run into the 4th or 5th representation of xml in radio in the
callbacks for writeRssFile. (see
http://backend.userland.com/stories/storyReader$210 for the specs)
In short, you are allowed attributes and a value. You are not allowed
e.g. <foo bar="baz">bonk</foo> works, but
can't be made to work. The xml can't even be included as the /value
element, since entities are encoded when they are added to the string.
Which is a real bummer, since the spec has structures like:
<dc:title>Life of Pi</dc:title>
<ent:topic ent:id="paperback" ent:classification="book"
That seems like a straight forward application of the basic xml verbs:
adrItem = xml.addTable(adrTable,"rvw.item");
xml.addValue(adrItem, "rvw.link", link);
What's unclear to me is why we have an incomplete representation of xml
for this fragment when there are at least two complete ones at our
- Hi Eric,
I think I must have solved this problem when I implemented the K-
Collector client for Radio. One of it's jobs is to put ENT metadata
into the Radio RSS feed.
From memory, what I did was to write a writeRssFile callback which
is, effective, a copy of the existing writeRssFile function with a
fix to allow properly nested XML being output.
I'm out for the rest of the day but will post further when I get a
p.s. Thanks to JY for alerting me to this message.