Unfortunately my area is not the OWL-part of our system, but I sit right
next to the guys that do use it. :-) We have been using Jena but are
replacing it with our own impl to minimize large external dependencies. I
would suggest you take a look at it; it has worked ok for us for the last
year.
Note that I think it is Jena that is packaged in a questionable manner -
they package core XML classes in their jar so you can easily get some ugly
ClassCastExceptions and funky VM errors if you are not careful. If you
have more in-depth questions, let me know and I can relay them.
mike
Arnaud Bailly <[EMAIL PROTECTED]> wrote on 08/17/2006 01:02:26 AM:
> Hello,
>
> > Sorry, we use a ton of OWL here and so I'm used to using it as a
synonym
> > for RDF.
>
> So I guess you could give me some advice on this idea as I have no
> practical experience using RDF/OWL tools :-)
>
> As I understand it, RDF graphs are just labelled directed graphs
> with OWL being a "grammar" for such graphs and with some predefined
> node and edges labels. The reporting API could just be a simple API
> for building an in-memory graph, with a specific plugin/component for
> transformation to suitable external RDF representation (N3, XML,
> whatever). But as one may need to query the graph, I think I need a
> real RDF API, so my question is: What is the right tool for starting
> the whole thing ? I know about Jena and Sesame.
>
> As I have a bit of spare time, I will try to hack a proof-of-concept
> into maven current codebase and post a patch.
>
> Thx
> --
> OQube < software engineering \ génie logiciel >
> Arnaud Bailly, Dr.
> \web> http://www.oqube.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
