Hi Nick if you *really* need DL reasoning SwiftOWLIM and Sesame's APIs are not for you. I am emphasizing *really* because there are plenty of people who chose DL being influenced by something and afterwards get surprised by the specific constraints that it requires
As a general comment, the completeness of the reasoning is not determined by the API (i.e. the interface definitions), but rather from the implementation that you will choose. For instance, one can provide results of a sound and complete inference through Sesame's interfaces (OWLIM could have been doing this, if it was a tableau reasoner) and another one could provide shallow or incomplete inference through DIG (yo u have to look at this, if you are into DL reasoning) Regards Naso ---------------------------------------------------------- Atanas Kiryakov CEO of Ontotext AD, http://www.ontotext.com Sirma Group Corp, http://www.sirma.bg Phone: (+359 2) 8091 555; Fax: 8090 404 ---------------------------------------------------------- ----- Original Message ----- From: Nick Khamis To: [email protected] Sent: Saturday, March 21, 2009 3:11 PM Subject: [tbc-users] Re: Best of Breed OWL API Hey Atanas, Thank you so much for your response. Basically we are looking to implement an application that automatedly generates OWL-DL Ontologies that have axioms, individuals and also make use a tableau reasoner, as well as store them in a repository. That being said I understand that SwiftOWLIM is one of the fastest reasoners out there, however; as you know it is not a full OWL-DL tableau reasoner and cannot deduce things such as disjointness. That being said we are looking for an OWL API (OO Style would be nice) that is complete in the sense that it will allow for the CRD of "complete" OWL-DL KBs. I think "The OWL API at http://owlapi.sourceforge.net/"; is just what the doctor ordered, has anyone here used the API is it any good (easy to use, somewhat complete, well documented, supported)? Best Regards, Ninus. On Sat, Mar 21, 2009 at 7:10 AM, Atanas Kiryakov <[email protected]> wrote: Dear Nick, what you refer as "GATE OWL API" is probably the API of Sesame 1.2. Actually GATE integrates SwiftOWLIM 2.9.1 as part of its standard distribution (the same holds for TBC, as far as I know). OWLIM in general provides storage and reasoning backend through the Sesame APIs Speaking of APIs, Sesame's main APIs allow manipulation of RDF store. One can CRD RDF triples (updating RDF triple is a non-sense). Thus you can assert: C1 rdfs:subClassOf C2 or delete this statement or ask for any statements paterns (e.g. C1 rdfs:subClassOf ?x). And evaluate queries, of course. This is obviously a low-level RDF API, that is designed for maximum efficiency when it comes to moving around large volumes of data in RDF (plenty of public benchmark results prove it is the best for this). If you want to use OO-style API, where you deal with classes and objects (instead of triples), you can look at the Graph API of Sesame (www.openrdf.org) and Elmo. There is also a simple OO-style API as part of GATE Finally, there are APIs which allow one to deal with OWL definitions and primitives (e.g. having specific programmatic support for owl:minCardinality), e.g. http://owlapi.sourceforge.net/. It's my personal opinoin that most of the users and applications (other than ontology enditors) usually do not need such APIs - people edit ontologies in editors as TBC, then only load them programatically (as RDF files) into repositories such as Sesame. Of course, there are plenty of different ways to get the same job done, depending on your application and environment. Regards, Naso ---------------------------------------------------------- Atanas Kiryakov CEO of Ontotext AD, http://www.ontotext.com Sirma Group Corp, http://www.sirma.bg Phone: (+359 2) 8091 555; Fax: 8090 404 ---------------------------------------------------------- ----- Original Message ----- From: Nick Khamis To: [email protected] ; GATE ML Sent: Saturday, March 21, 2009 5:13 AM Subject: [tbc-users] Best of Breed OWL API Hello Everyone, We are currently considering one of the following (jena.jar, gate.jar, protege.jar) libraries to assist in CRUD (Create, Read, Update, Delete) operations of ontologies. We will be using triple stores such as (jenadb, sdb, rdfcrm). I am trying to learn from your experiences regarding this issue and what your advice (pros and cons) is in terms of using the listed libraries. We are also open to recommendations of other APIs that I have not listed. Regards, Ninus. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
