finally a bnode with a uri

Finally browsing

Adding browsing functionality to OWLchestra's RDF Store
Yesterday, I finished a first version of an RDF browser on top of OWLchestra's RDF store. This means that I am finally getting close to the relaunch (at least as far as my components are concerned). I still have to implement a SPARQLing query builder and some other stuff, but with an editor and browser in place the portal's base functionality is there.

My concept for the browser included supporting facet restrictions but given that a) I'm behind schedule, b) funding ended in 12/2004, c) /me is heading towards insolvency, and d) the API to my RDF store is still very basic, I decided to better start with something simple. And as displaying the retrieved information is still complicated enough, I happily focused on the front-end stuff.

(Unfortunately, DERI seems to have problems with the beta version server at the moment. It was offline for 3 days and my FTP account is still gone. It might take some time before I can upload the browser, so I 'm going to annoy you with my clumsy screenshots once again...)

In order to reduce the result set even without selectable facets, I implemented a low-end fulltext search on potential resource labels and the possibility to restrict the resource type as well as the time of resource description modification:

rdf browser restrictions
Clicking on one of the result list's entries...
rdf browser result list
...will show a resource summary (and hide the list for reduced server load):
rdf browser summary

Depending on the type of related resources and the existence of resource descriptions, a couple of icons are displayed next to each entry. In the image above we can see that there is a summary available for Danny's weblog.

The blog summary shows an RDF import icon next to an rdfs:seeAlso link:
rdf browser summary
(I plan to offer resource description discovery for any URI but I still have to program the client to do MGETs, interpret headers, follow redirects etc., so at the moment, imports are only possible on "probably RDF/XML" links.)

Ok, what happens if I click the import link?
First, the script checks if the source is already known, otherwise it creates an entry in the system's list of RDF sources. Then, an ARC parser instance retrieves the RDF document and adds the parsed triples to the RDF store. In case the source has been crawled before, the database will only be updated if the document changed.

rdf browser import
Switching the resource filter to rss:item now and searching for "danny" returns a list of 10 current entries, of course I can't resist watching the latest SPARQL photo:
rdf browser summary
Next thing to do is to create custom templates for selected resource types, e.g. a nice profile page for foaf:Persons or an aggregated view for rss:channels. The mechanism is already activated, but I needed a little break, and browsing-importing-browsing-importing was too much fun to directly continue coding.

Hm, and perhaps I should write a smusher first...

Comments are disabled for this post.


No Posts found