January 21st, 2006
The post on BB today reminded me of MusicBrainz. I’m still patiently waiting for MusicBrainz to add support for arbitrary, user-contributed, emergent flat classification. (i.e. what the rest of us calling “tagging”, but that term is overloaded for audio files.)
My original desire was driven by the desire to build playlists by mood, or theme (‘electronic’, ‘sensual’, ‘dark’), but since then Pandora has launched and showed us another set of axes to explore (‘mild rhythmic syncopation’, ‘extensive vamping’).
I think the ability to hang a variety of arbitrary data off of the MusicBrainz model would kill CDDB deader then a stake through the heart, and at the same time creating a platform where its easier to collaborate in public then in silos. Tagging is just the first, easiest to under form that might take. Got to use all that lovely RDF to some purpose!
Tom’s Phonetags is useful prior art.
May 21st, 2005
Nothing quite like spending an afternoon sketching out database schemas for lists of heterogeneous, extensible objects to give you that familiar, sinking feeling of re-inventing RDF…badly. And nothing quite like surveying the state of RDF for scripting languages to convince you to grimly knuckle down to your schemas.
If I were a Semantic Web booster, looking for a project to hack on/fund, I’d pour some resources into making a replacement for ActiveRecord.rb to make it simple to build Ruby on Rails apps with a triple store back end. Catch the wave of hype/buzz, appeal to a community consisting of some of the savviest, most cutting edge web developers, and maybe pick up a few hints along the way about making tools developer friendly. Done well, it would be a very compelling alternative to LAMP(R). Call it R-Cubed, or maybe Triple-R.
August 12th, 2004
Life has a been a little crazy (diagnosis: monomaniacal) of late. If I haven’t gotten back to you since around June 25th it isn’t personal, if I have, you’ve been lucky.
Among the many items piling up in my inbox, have been RSS/Magpie/RDF links. Here is a dump.
rss2jabber is a wicked cool script for sending out RSS updates over Jabber. Haven’t played with it extensively, but the possibles uses boggle the mind.
RSS-WML is a RSS feed viewer (aggregator) for WAP devices. Requires PHP, and MagpieRSS.
Jo wins the “making RDF accessible” award of late with Class::RDF, a CDBI based triplestore, and RDF::Simple. I think there must be something about England that encourages Perl coding, be it climate, or culture.
The “much anticipated” XML::RSS 1.05 should hit CPAN in the next few hours. There is also a chance it will be going to better caretaker soon. I just don’t have what it takes to drag this beast into the modern era. (but I’ll happily chatter on about what is wrong with it, if anyone cares)
In the Magpie coming soon (I promise, really) department, Steve’s character encoding patches, a patch from Glen Davies adding support for fetching RSS via authenticated proxies , improved documentation courtesy of firetrap, and an update of the recycle code to work with the latest and greatest FoF from Ernie Oporto.
July 29th, 2004
I didn’t realize DOAP wasn’t out when Jo was proselytizing it at the Aspiration convergence earlier this month. If I’d know that I’d have jumped on it, you know be one of those early mover cool kids. Now it is released, with a web page, and a OSCON session + Danny O’Brien write up.
My initial feedback is that we’ve got to stop being so damned cute with our naming if this stuff is going to get wide adoption, FOAF, LOAF, DOAP, come on!
Still, Magpie DOAP (hmm, have to see if I can use .htaccess to force proper content-type), courtesy of the DOAP-a-matic. Really Sourceforge should spit this out automatically, in the mean time it would be a trivial hack to write a Sourceforge RSS to DOAP converter. (that was a hint)
June 29th, 2003
You know the one persistent meme in all these RSS debates is that RSS 1.0 is somehow a “RDF technology” and therefore complicated and hard. I never understood that. I’ll be the first to admit I don’t entirely grok the RDF/Semantic Web big picture, and even less the processing model for working with RDF, but so what. RSS 1.0 is just XML, how its hard to parse, or hard to produce I can’t imagine. At one point in the debate RSS 1.0 was supposedly difficult because of the namespaces, and I grant you that supporting namespaces well is harder then not supporting them. But if someone could explain to me what makes RSS 1.0 harder then RSS 2.0 I would dearly love to know.