Jena 2 Rules

100o blessing points to Leigh Dodds for writing a little showcase of the Jena 2 inference engine.

This one helped me today to get grip of the inference engine and some thoughts about forward chainer I had. At the moment I have to drill the engine up so that I can decide if it queries the local model or a SPARQL source, nasty work.

Extending this thing looks easy, but when you want to create more than one variable binding in a BuiltinRule… whatever, I hope I can blog the solution soon.

syncTunes

the endless problem and backdraw of using iTunes: it mingles up your file folders and contents.

  • when I drag a song into iTunes 2 times, there will be a copy of the song in it. Even when they are byte-identical. youaredoomed when importing the same folder twice. I think this is fixed in the latest version.
  • when I remove a song from itunes and FORGET to press that “delete it” button there will be corpses of unused songs in my iTunes library-graveyard.
  • when I have two, three, four computers (I have 5) then you can install iTunes only on one. All your playlists, ratings, songs will NOT be synchronised.
  • when two users on the same computer both use iTunes, their libraries are not synchronisable. DOOM when your wife wants to listen to the same music as you – you have to keep each mp3 twice (creepy). NO I want to use the “let itunes manage my library” function and I don’t want folders somewehre else.

so, the problem is to get the library in iTunes synchronised with the iTunes library on disk (iTunes claims to “manage your library” but I don’t see this “find corpses” button). Then I want to synchronise (not replicate, there is a differnce) two or more iTunes installations. I also want to use the same library and metadata on the same computer by different users. Again, both may open iTunes at the same time. As apple doesn’t care, a few solutions are available by others:

SPARQL has some use – Kendall Clark

Kendall Clark writes about WEB 2.0 and its relation to RDF and SPARQL, especially pointing out (to the wide world) that SPARQL is good for ATOM-like apps and can be a key feature.

Yes, thats right. Sparql will be the SQL of the next century. The nice hack he pointed out is to use XML/RPC and AJAX clients to integrate SPARQL features to websites. Boy, this idea is new and good. I think I ready implemented it last week in the gnowsis project and am right now in pimping up the CSS with dominik heim. More poeople will come up with similiar stuff and integrate RDF into html pages as active information.

In gnowsis_retrieval search engine we use the AJAX thing to “show related” information about an item. Ideal thing, this information is hard to get for many items, so loading it on demand is exact the thing we needed.

Funny that we are ahead, that’s what research is about, isn’t it?