<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/how_to_implemen.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2010:/1/tag:72.47.210.69,2003://1.4040-</id>
  <updated>2010-03-01T17:45:49Z</updated>
  <title>Comments for How to implement ENT into your Radio RSS feed</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>
  <entry>
    <id>tag:72.47.210.69,2003://1.4040</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/how_to_implemen.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=4040" title="How to implement ENT into your Radio RSS feed" />
    <published>2003-05-28T05:44:56Z</published>
    <updated>2007-12-16T23:15:27Z</updated>
    <title>How to implement ENT into your Radio RSS feed</title>
    <summary>After a few late nights, I&apos;ve successfully implemented Easy News Topics (ENT) tags to my Radio Userland RSS feed. It wasn&apos;t as easy as I thought it would be. It involved rooting around in the Radio.root file of my weblog and upskilling myself in UserTalk, Radio Userland&apos;s scripting language. But mostly I stood on the...</summary>
    <author>
      <name>Richard MacManus</name>
      <uri>http://www.readwriteweb.com</uri>
    </author>
    
    <category term="Publishing Services" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><P>After a few late nights, I've successfully implemented <A href="http://matt.blogs.it/specs/ENT/1.0/">Easy News Topics (ENT)</A> tags to my Radio Userland RSS feed. It wasn't as easy as I thought it would be. It involved rooting around in the Radio.root file of my weblog and upskilling myself in <A href="http://frontier.userland.com/manual/userTalk">UserTalk</A>, Radio Userland's scripting language. But mostly I stood on the shoulders of giants to get this done - <A href="http://www.scripting.com/">Dave Winer</A> and <A href="http://matt.blogs.it/">Matt Mower</A> in particular.</P> <P>ENT is an extension of the <A href="http://backend.userland.com/rss">RSS2.0 spec</A>. Its aim is to enable&nbsp;categorization of&nbsp;RSS items into topics. After reading about ENT and <A href="http://radio.weblogs.com/0105304/2003/04/28.html#a3">writing one of my first articles</A> about RSS topics, I decided I wanted to actually implement ENT into my weblog.&nbsp;After some initial searching, I came across an article by Dave Winer called <A href="http://backend.userland.com/stories/storyReader$210">"How to extend Radio's RSS&nbsp;generator"</A>. This introduced me to 3 new "callbacks" which enable Radio developers to modify their RSS feeds. The callbacks are: writeRssNamespace, writeRssChannelElement, writeRssItemElement. The first one I successfully implemented was the namespace. I did this as follows:</P> <P>1. Open up your Radio.root file.<BR>2.&nbsp;Drill down to user.radio.callbacks.<BR>3. Double-click on&nbsp;writeRssNamespace, then re-name "item #1" to "ent".<BR>4. Enter the&nbsp;script <A href="http://www.readwriteweb.com/images/screenshot_ent1.JPG">linked here</A>.<BR>5. Click "Compile".</P> <P>That was relatively&nbsp;easy. Implementing the item elements&nbsp;turned out to be&nbsp;trickier - particularly as the elements have&nbsp;attributes and&nbsp;are nested. It took me a while to get to grips with the UserTalk syntax, not being a programmer by trade. I bumbled around a bit and got to a stage where I juuuust about had the script right. Then I happened upon <A href="http://groups.yahoo.com/group/radio-dev/message/7752">Matt Mower's conversation with Dave Winer</A> and finally things fell into place. <A href="http://www.readwriteweb.com/images/screenshot_ent2.JPG">Here now is&nbsp;my code</A>&nbsp;for the writeRssItemElement script - same process as above.</P> <P>But wait, there's more. Because the ENT tags are nested, there is one more piece of&nbsp;scripting you need to do -&nbsp;&nbsp;modify writeRssFile.&nbsp;But luckily&nbsp;Matt Mower, one of the authors of ENT, has already done the work - <A href="http://matt.blogs.it/gems/workspace.writeRssFile.ftsc">right-click here to download&nbsp;the script</A>.&nbsp;Open this in&nbsp;your Radio app, and it will automatically save itself in the workspace&nbsp;area of Radio.root. Then you need to copy it across to the following location:<BR><STRONG>system.verbs.builtins.radio.weblog.writeRssfile</STRONG> </P> <P>btw&nbsp;as a sidenote, writeRssfile is just one of&nbsp;many very clever scripts built-in to Radio. It's amazing how much data there is in Radio.root, once you have a good&nbsp;poke around. It's a testament to the amount of work Dave Winer must have put in to build Radio Userland, so I do sympathise with his recent&nbsp;posts about software developers <A href="http://scriptingnews.userland.com/2003/05/26#whoWillPayPart2">gettin' paid</A>.</P> <P>Anyway&nbsp;that's basically it for stage 1 of implementing ENT into my Radio RSS feed. Stage 2 is to&nbsp;actually put&nbsp;some worthwhile data into my topic tags - currently I've just got dummy data in there. Ideally I want to dynamically generate a topic word or phrase for each weblog post, based on the contents of the post and/or the title. But I guess this is where <A href="http://k-collector.evectors.it">k-collector</A> comes in. So that's my next project, to find out about k-collector and&nbsp;put some meaningful data into my shiny new ENT tags :-)</P></p>]]>
      
    </content>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2003://1.4040-comment:35131</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2003://1.4040" type="text/html" href="http://www.readwriteweb.com/archives/how_to_implemen.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/how_to_implemen.php#c35131" />
    <title>Comment from M. Ford on 2003-05-29</title>
    <author>
        <name>M. Ford</name>
        <uri>http://radio.weblogs.com/0107233/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://radio.weblogs.com/0107233/">
        <![CDATA[<p>thank you very much. I have always wanted to do this. Too bad I hadn't implemented it from the very beginning. This one upgrade has the potential of improving the value of a weblog enormously. Now, if I only had your well-formed brain cells.... mine are a little dog-eared... this is brilliant! Radioland is a treasure-chest of possibility, limited only by the user's ability to harness it...</p>]]>
    </content>
    <published>2003-05-29T21:42:44Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2003://1.4040-comment:35132</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2003://1.4040" type="text/html" href="http://www.readwriteweb.com/archives/how_to_implemen.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/how_to_implemen.php#c35132" />
    <title>Comment from Richard MacManus on 2003-05-30</title>
    <author>
        <name>Richard MacManus</name>
        <uri>http://www.readwriteweb.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
        <![CDATA[<p>glad my post was helpful to you. It took me a few days to get ENT set up in Radio, so I figured I better document it so others can do it quicker :-) I agree about your comments on Radio. It is a fascinating product, sometimes frustrating but always innteresting :-)<br />
Cheers, Richard</p>]]>
    </content>
    <published>2003-05-30T09:02:34Z</published>
  </entry>

</feed>