Hi Gregor, Thanks for your useful advice. I'm dealing with a fairly small ontology file (just over 200 owl:classes), which may get larger if I merge other ontologies into it. I was simply looking to display the .owl file in a tree in the first instance.
I think as you suggest rightly it would be much better to let the server do the work. I will look into Sesame and Jena. Thanks again for your help and quick response, Ed 2009/1/28 gregor <greg.power...@googlemail.com> > > Hi Ed, > > Are you talking about just a smallish ontology (i.e. the class > definitions etc) which you want to display/edit (e.g. for schema > design purposes), or are you talking about processing a lot of data > from/defined in an OWL source (e.g. navigation/search purposes)? > > I don't use OWL sources, but I use RDF/RDFS data quite a lot. I load > RDF files into a Sesame memory store on server and fire SeRQL queries > against it from GWT RPC servlets. This works pretty well. Jenna is an > alternative. > > I would think writing a client side OWL browser/editor is non-trivial, > and not helped by the limitations of GWT JRE Emulation. A lot easier I > would think to let Sesame/Jenna do the work on the server, and ship > the results in small chunks to the client. For example I use one RDF > source that defines about 3500 classes and subclasses. I use a lazy > load Tree widget for one view of this (i.e get the top layer, get next > layers if/when user clicks to open branch). This is very quick (Sesame > does the queries in about 16-32ms). > > If you need to edit the ontology itself, that's another matter. > > regards > gregor > > On Jan 27, 11:42 pm, "eoc...@googlemail.com" <eoc...@googlemail.com> > wrote: > > Hi, > > > > I have a web ontology file (.owl) that I have parsed into a string > > using the RequestBuilder and was wondering how I can access all of the > > individual owl:classes and their subclasses on the client, then build > > a tree from this hierarchy as the xmlparser/dom does not work for this > > purpose (though as you might expect it has worked on a test xml case). > > > > An alternative would be to use the OWL api on the server and return a > > hashmap of all the owl:class,sub:class values, then construct the tree > > from the hashmap. > > > > I was just wondering whether its possible to do it on the client. Any > > help on this matter would be greatly appreciated! > > > > Thanks in advance, > > > > Ed > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
