kit-sdq / ecore2owl Goto Github PK

URIs are currently formed in a way that the name of the class is used. Same applies to Enums (the values are used in the URIs). Some names, especially ones that containt multiple number signs (#) will break URIs.

Possible solution: Use names only with rdfs:label and use (generated) IDs for the URI.

Hi -

INFO] ------------------------------------------------------------------------
INFO] Reactor Summary for ecore2owl.parent 1.0.0-SNAPSHOT:
INFO]
INFO] ecore2owl.parent ................................... SUCCESS [ 0.112 s]
INFO] ecore2owl.bundles .................................. SUCCESS [ 0.027 s]
INFO] Ecore2OWL Dependencies Collector ................... SUCCESS [ 25.426 s]
INFO] ecore2owl.dependencies-provider .................... SUCCESS [ 2.914 s]
INFO] ecore2owl.OntologyAccess ........................... SUCCESS [ 1.314 s]
INFO] ecore2owl.core ..................................... FAILURE [ 0.320 s]
INFO] ecore2owl.ui ....................................... SKIPPED
INFO] ecore2owl.features ................................. SKIPPED
INFO] edu.kit.ipd.are.ecore2owl.feature .................. SKIPPED
INFO] ecore2owl.tests .................................... SKIPPED
INFO] ecore2owl.releng ................................... SKIPPED
INFO] Ecore2OWL Update Site .............................. SKIPPED
INFO] ------------------------------------------------------------------------
INFO] BUILD FAILURE
INFO] ------------------------------------------------------------------------
INFO] Total time: 01:39 min
INFO] Finished at: 2020-04-01T08:02:32+01:00
INFO] ------------------------------------------------------------------------
ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.5.1:compile (default-compile) on project ecore2
wl.core: Compilation failure: Compilation failure:
ERROR] F:\GitHub\Ecore2OWL\bundles\edu.kit.ipd.are.ecore2owl.core\src\edu\kit\ipd\are\ecore2owl\core\Ecore2OWLTransform
r.java:[260]
ERROR] .collect(Collectors.toUnmodifiableList());
ERROR] ^^^^^^^^^^^^^^^^^^
ERROR] The method toUnmodifiableList() is undefined for the type Collectors
ERROR] F:\GitHub\Ecore2OWL\bundles\edu.kit.ipd.are.ecore2owl.core\src\edu\kit\ipd\are\ecore2owl\core\Ecore2OWLTransform
r.java:[667]
ERROR] ontologyAccess.addDataPropertyToIndividual(optIndividual.get(), optDataProperty.orElseThrow(),
ERROR] ^^^^^^^^^^^
ERROR] The method orElseThrow(Supplier<? extends X>) in the type Optional is not applicable for the a
guments ()
ERROR] 2 problems (2 errors)
ERROR] -> [Help 1]
ERROR]
ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
ERROR] Re-run Maven using the -X switch to enable full debug logging.
ERROR]
ERROR] For more information about the errors and possible solutions, please read the following articles:
ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
ERROR]
ERROR] After correcting the problems, you can resume the build with the command
ERROR] mvn -rf :ecore2owl.core

Currently, there is a limited amount of datatypes that are supported. This list have to be reviewed and a workaround for unsupported datatypes should be found.

To make the usage of this tool easier for everyone, an updatesite should be created, so that people can add the tool as plugin via the eclipse plugin manager.

Right now, the performance for bigger models is getting worse and the tool scales rather bad. This needs to be improved.

My current (educated) guess is that certain elements (individuals, classes, properties) are queried by name each time instead of using the URI/IRI. This was already detected in another project to be rather imperformant when the ontology gets bigger. Here, querying using the URI/IRI should be preferred.

Moreover, one can think about other methods like parallelizing some parts. However, this needs changes to the current algorithm.

Lastly, on the long run one can exchange the local ontology connector with https://github.com/InFormALin/Ontology-Connector. There are some performance tweaks and other improvements

Gibt es die Möglichkeit mit deinem Tool aus OWL Ecore Modelle zu erzeugen?