Sesame, OWL, and so forth
Once more I'm trying to collate my thoughts as to which Semantic Web backend I'm looking for. Not easy, as I've previously mentioned, and they do all seem to be in Java (bah).However, I noted a few interesting
Issueson the Sesame Issue Tracker: OWL support in Sesame; Enhanced inferencing using SWI prolog backend*; Make system configuration RDF-based; Aggregate functions in SeRQL (count, minimum, etc.). Seems other people want some of the things I do!
I've also noticed something about query languages. It seems there are two classes: end-point ones, which typically have a SQL-style syntax, and return values or other unstructured results, and ones that could support chaining more easily, where the query and its results are Semantic Web languages. E.g. RDQL:
SELECT * WHERE (?x, ?y, ?z); OWL-QL: a standard OWL knowledge base, with variables, wrapped up in a SOAP message. Perhaps due to different paradigms: one is intended to be a programmatic interface to the knowledge base (indeed, Jena's RDQL strings are an alternative to the programmatic form), while the other is meant to be a communication protocol for agents.
Of course, OWL-QL is a damn sight more powerful (though I like some of the features of SeRQL…).
Enough rambling!
* Interesting… Sesame currently just deduces the entire set of consequences from a KB, using that to answer queries. This proposal suggest using SWI Prolog as the backend to do backward-chaining.
Posted at 2004-04-22 07:51:44 by Richard • Link to Sesame, OWL, and s…
Comments, trackbacks.






