Page unresponsive on chrome

[ghost]

Hi ,

Firstly thanks for wonderful work on webvowl and we are using it for ontology visualization. We are facing a curious problem. We are trying to load a RDF file which has 25000 triples and roughly 3.5 MB in size. Chrome is killing the page because the page has become un-responsive. We tried reducing the size iteratively to 4000 triples and 400 KB and it loads just fine (so its not an issue with the format).

Is there any option we can turn on to make it load our complete ontology?

If not, are there any plans to add a paging capability to the ontology visualizer ? For example, we can have a 1,2,3,4... kind of bread crumb to progressively load ontologies (which along with search should serve just fine)? Please guide us so we can move past this issue.

Regards Ram

[steffen-l]

The public instance of WebVOWL available at http://vowl.visualdataweb.org limits the file size of the ontologies that can be uploaded (maximal size is roughly 1MB). If you would like to use WebVOWL with larger ontology files, you need to download OWL2VOWL+WebVOWL and run it on your machine.

Having said that, there is still some limit in the max. ontology size that can reasonable be visualized with the current WebVOWL version. The visualizing of (very) large ontologies with WebVOWL is challenging, as scalability needs to be addressed on several dimensions (visual scalability, memory capacities, transmitting, performance issues, etc.). The chosen SVG-based implementation has some limitations in this regard. We are aware of it and have it on our list (currently working on an improved visual scalability), but I don't see that WebVOWL will soon be capable to visualize very large ontologies, as this requires quite some research and development. For now, you can only try to load and visualize the complete ontology at once on some good hardware - the automatic collapsing feature helps a bit at least (as only a limited set of elements are rendered initially).

[ghost]

Hi Steffen

I forgot to mention that we carried out the tests on local hardware on a locally running machine with has around 4GB of RAM and i5 chipset.

Will you be open to admit a patch that allows paging through large ontologies? Of course, we may have to split the OWL on server side.

Regards Ram

[steffen-l]

Paging is not planned and I am not a fan of this idea to be honest, but would favor some better (i.e. less specific, cumbersome but more user-oriented) solution. I am open to good arguments though ;-)

In any case, it would help if you could provide a little more information of what error message or exception you get in your case and how you got around it. This could be valauable input to discuss possible options. Still, I think the visualization of (very) large ontologies is a major issue that requires more thought and research.

[anupam1050]

HI,

We are using the webPRotege as an editor and exploring the way to load the edited ontology to WebVOWL from Webprotege? is there any way to do the same?

Thanks Anupam