Oscar Corcho

Ability to remove from the documentation classes and properties from other ontologies

1

Sometimes it is a good practice, to facilitate the understanding of the ontology, to bring in into the OWL file the definition of a class or property from another ontology,...

Allow determining whether the terms that are not defined for the corresponding namespaces should be visualised or not

2

Whenever there are terms (concepts, data properties, object properties) that are coming from other ontologies (just referenced, but not imported), these terms appear in the documentation as classes and properties....

Not only when .owl files are updated, but also when configuration files are updated, the tool should get activated and process the existing owl files. This includes configuration files for...

I am thinking of something called mini-leaks that I have been requested about and where we have an opportunity to use our system. Just point somewhere, and allow people to...

It would be interesting to provide the possibility of specifying chains of properties as facets in the facets.ttl file. As an example, let's imagine that we have the following information:...

It would be nice to have the possibility of specifying several facets in the facets.ttl file, so that they could be considered in the facet selection area of the visualiser....

Currently datatype properties cannot be used as facets for the visualisation. If specified in the facets.ttl file, the result is that the visualisation does not include their potential values. It...

If I have a dataset with geolocated data according to our geolocation model, we should be able to allow people to submit the URI, or the RDF dataset, store it...