P@ Sunglasses

« Learning Ruby: a few... | Main | Link: Making CAPTCHA... »

20050131 e hënë janar 31, 2005

Re:Syndication model convergence and RDF

Cool, Danny Ayers discovered our little java-syndication group and wrote a thoughtful blog entry with a proposal for something that we want to solve: Syndication model convergence and RDF.

2 weeks ago Alejandro and I (from ROME) went to San Francisco to have lunch with Kevin Burton and Brad Neuberg from Feedparser and discussed potential areas of collaboration, and our joint submission at JavaOne. One of the ideas that came up (from Brad if I remember) was to build ROME-like beans on top of a Feedparser-like event driven API. We also agreed that the first thing we could collaborate on was on specifications for the mapping. After lunch I suggested that we could eventually move the mapping logic (in ROME terms, how you map a format specific WireFeed to an abstract SyndFeed) to a declarative representation, so that instead of having written specs we could generate code. But I didn't elaborate much more: I was not sure it would be necessary if we build one parser on top of the other. Most of the logic would migrate in feedparser, to generate the Synd level event, and ROME would just listen to these events to build beans.

What I had in the back of my mind when suggesting that was linked to my recent dabbings in Ruby. A quick look at the Ruby Application Archive showed 3 syndication libraries:

If I write my next system in Ruby I'll need a ROME-like library, except if I run on top of a VM and use JRuby. I thought it would be a waste of time to completely recreate ROME in Ruby. If the mapping rules expressed in ROME source code were expressed declaratively I could rewrite ROME by parsing and interpreting it, as a test case for the description. Then Feedparser could do the same, but more importantly syndication libraries written in other languages such as Ruby could do the same: as a programmer, you could go from one system to the other and still work with the same object model for feeds, entries and modules.

I had not started thinking about which format to use for this description, but Henry Story's work on mapping Atom to OWL (continuing the work Danny had started) leapt to my mind (he presented it at the october 21st ossgtp in Paris). Danny fills in the blanks in his post! I wanted to spend a bit more time looking at alternative formats and tools for this description (RelaxNG, XMLSchema?) before starting on that, but this application seems to me like an excellent real world use case of RDF/OWL.

( Jan 31 2005, 09:55:44 PD PST ) Permalink Chat about it Technorati cosmos Tagsurf It

Comments:

Post a Comment:

Comments are closed for this entry.

Valid HTML! Valid CSS!

This is a personal weblog, I do not speak for my employer.