> > Jeremy you brought up the comment that Jena was designed more for > > analysis type applications as opposed to ontology editing > > applications.
I would want to distinguish between the Jena API, and the Jena triple stores. The Jena API was designed to be pretty neutral with respect to the application, and does not have predesigined into it any task specific optimizations like first write, then read .... The Jena triple stores implement the API, but when we had to make trade-offs between one way of doing things or another, we would make the judgment based on our sense of where most RDF apps would be. TBC supports many different triple stores, which implement the Jena API. The designers of these triple stores, will have seen the world differently, and made different trade offs from the Jena team, so for some applications one would expect a non-Jena implementation of the Jena API to be superior. [In fact, given the different business goals of the different teams involved, one would expect this perhaps even for most applications] Jeremy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
