RE: [TaxoCoP] OWL2 Engines
Thanks for the list of triple stores. I will have a look.
We tried Jena but found its transaction model difficult to integrate with our “parent” transaction – eg: we need to do some operations in the CMS and in the triple store in the same transaction (would rather not use 2 phase commit). As well, Jena does not cleanly model the first class objects of OWL2 – classes,individuals,properties. It was not obvious how to update the ontology aside from loading an updated file. File imports did not support the OWL2 Functional Language. As well, inference is used to determine class descendancy whereas a cached graph is more straight forward.
So agreed, a triple store does the work underneath, but we need a clean API on top of that with good plugin transaction support.
We are thinking of just writing one – we see it as about 6 tables to start.