Re: Namespace support in Radio: (was: Re: [RSS2-Support] Re: This appears to be a bug report)
Jake Savin wrote:
> We have a place where we and our users can provide scripts that are
> associated with elements that have a particular namespace URI. The
> script gets control when the parser finds an element whose namespace
> URI matches. It can do whatever it wants to with the given element.
> More often than not, it will store the data in the table that contains
> the parsed feed, which will then be picked up in Radio's user
> interface. These scripts (actually collections of scripts) are called
> moduleDrivers in Radio parlance. (Though that name might change before
> we release).
>
> There's a place for UserLand-supplied moduleDrivers, and a place for
> user-supplied ones. If both exist, then the user-supplied version
> takes precedence. This way UserLand can add support for modules, and
> if our users or developers want to extend or override the given
> functionality, they can easily write their own drivers.
Drool. Down my chin, soaking my shirt, drool. You just sold a copy. I only
hope that this time I can manage to teach myself UserTalk.
>
> The way I see it working, at least right now, is that moduleDrivers
> will come along with some user-interface elements that go in Radio's
> desktop website. Exactly how that will happen is still being worked
> out. (People on-list who develop in Radio are welcome to toss in their
> $.02 here.)
>
> There's also the matter of how a Radio user would add modules to the
> feeds that they produce, which is probably more interesting for most
> users. We're still thinking about how best to do that, and again, your
> $.02 are welcome. Perhaps an example might lead to some ideas here:
> How do users (not developers, but perhaps power-users) add a module
> to a feed they create using other tools? Could one or more of you
> provide a bird's eye overview or step-by-step?
The only one I know about is Movable Type, which just does RSS feeds off
templates just like the template for the main page (in fact, it doesn't
actually know which is which). So if you want to add something to a feed,
you just add it to the template. Adding Sam's <slash:comments> would just be
It's not a bug, fear not. He's done two things. He's dropped his 0.91 feed back to the original Netscape 0.91spec - to include the DTD - and secondly, he's...
Um, this wasn't meant as a bug report... I used a pre-existing module which will enable RSS2 aware aggregators who care to do so to know when there is a new...
... Looks spot on to me. If you're doing modules, you might like to add <dc:contributor> and give the names of all the people who have commented. Going mad...
... Oh, quit teasing him. ... It probably would have been more instructive if you also included the 2.0 core "comments" element. Especially if you switched the...
... I think that's more a case of /. not using the latest version of Slashcode. But you'd have to ask CmdrTaco. Certainly the Slashcode site uses it: ...
... I can't see a reason why not: namespaced: check no rdf elements: check does something useful: check documented: check lovely. I shall implement the same....
I wasn't sure. Thanks for explaining. Dave ... From: Sam Ruby To: RSS2-Support@yahoogroups.com Sent: Monday, September 30, 2002 1:14 PM Subject: [RSS2-Support]...
So it was a bug report? Dave ... From: Sam Ruby To: RSS2-Support@yahoogroups.com Sent: Monday, September 30, 2002 1:43 PM Subject: [RSS2-Support] Re: This...
Another tradition of RSS has been that you must use common sense, even street smarts, when designing your feeds. I know you're new to this. This has been a...
... Actually, it's an excellent idea all around. The aggregator most likely to implement the RSS2 core comments element is Radio. You've now served notice on...
... Hi all, I'm working on RSS2 and namespace support for Radio's aggregator. (For any who don't already know, I work for UserLand.) In the code I have working...
... No - they should be dealt with by the script that deals with whatever namespace that <mySubElement> is in - but then the result should 'belong' in whatever...
Interesting comment Phil about Radio. However the psychology is not *exactly* as you say. If Sam wants us to stop everything and understand the "slash" module...
... I can expand on it a bit. While we're still working out all the details, but here's the basic idea: We have a place where we and our users can provide...
... Drool. Down my chin, soaking my shirt, drool. You just sold a copy. I only hope that this time I can manage to teach myself UserTalk. ... The only one I...
... No the current RSS generation in Radio8 is from a monolithic script. MovableType can give you the comment counts because it's storing them in the same...
... Rats. I think I even confused myself, trying to wink in one direction and nudge in another. If you think I was suggesting that Radio should support...
... For the last time, no. You asked for something that would help you find out when a thread you were tracking contained a new comment. I saw an existing...
For what it's worth I think it's fantastic that you're exploring modules in re RSS 2.0. As far as I'm concerned the air is clear. Keep on truckin. Dave ... ...
... considers <comments> and <slash:comments> It doesn't do that. Something to bear in mind, Radio is a SOAP client and server. That should give you some idea...
... So as a rough first hack at it, an extension script should return whatever it produces to whatever calls it, and only the main script should add stuff to...
... Phil, that'd be a valid point, maybe, if it were true. :-) Perhaps you are looking at http://slashdot.org/slashdot.rdf, which is an RSS 0.9 feed. We...
... the ... 1.0. ... Ah, my bad. I was looking at http://slashdot.org/code.shtml which only links to slashdot.rdf and slashdot.xml, not slashdot.rss. (When I...