Tuesday, January 29, 2002

New tool: Easy Images from the Desktop. Praise Murphy!  [Scripting News] 5:43:52 AM

Beta: fileSystem Upstream Driver. "It's perfect for people who have a static HTTP server nearby."  [Scripting News] 5:43:12 AM

Dean has a new Radio graphic.  Cool. [John Robb's Radio Weblog] 5:42:34 AM

Yaay! Mikel Maron has released a categorized News tool for Radio. [Garth Kidd: DBS - On Radio] 5:41:56 AM

The Web and Radio; what a rich medium; add Mac OS X and iTunes and you have the utilmate web music machine. Currently listening to Sheryl Crow performing Bob Dylan's "Mississippi" from The Globe Sessions CD. Blogging and grooving to good tunes, what a way to work! [Radio X Neophyte] 5:41:17 AM

Radio reviewed. Comprehensive, well-written, enthusiastic WinPlanet review of Radio UserLand by blogger Eric Grevstad. [Jonathon Delacour Unplugged] 5:40:32 AM

Are you a Radio user? Burningbird's writing a review of Radio 8 for O'Reilly Networks and is "looking for feedback from the user community about your experiences with the product." You can probably work through her list of questions pretty quickly. [Jonathon Delacour Unplugged] 5:39:52 AM

Yesterday I talked about the problem with RSS overload. Today it's search engines. What are some of he problems with search engines and searching databases in general? I'm glad you asked. Things I don't like: Each search engine has its own query syntax Each search engine returns results in a slightly different HTML format You have to search each engine via its own web form. OK, some site offer to search a number of engines for you through a single interface but problems 1. And 2. Still apply. I can't incorporate search results into my own content management system. Don't even mention page scrapes. What's the point. What do all search engines do? They search their own databases for internet resources that match a keyword you specify. They return the resulting 'hit's as an HTML page of resources, usually pages, comprising title, link and a brief description of the page culled from the page itself. That result format, remind you of anything? What if search engines returned their results as an RSS file. It's be structured in a way you could expect and rely upon so that you could incorporate the resulting data into whatever system you liked. Repurpose it using your own content management system for example. Why limit this critique to internet search engines? What if all database searches returned results in this way? What if you could bolt together search interfaces in a plug-and-play kind of way to any database and have the results all returned, aggregated even, in a consistent portable format that can be incorporated into content management systems? You wouldn't have to worry about what platform they were running on, what database was being used at the back end, what query structure they used and more importantly, what format the results would come back as. Show us the way David, what are you on about? Here's how I've adapted my RSS aggregator to search for teaching and learning resources. These resources, or rather their descriptors and place holders, held in databases that search engines couldn't index, interoperate with whatever content management system you're using just so long as it's XML-friendly. http://medweb5.bham.ac.uk/databases/interop/mcqs More later. [David Davies' Radio Weblog] 5:39:01 AM