Ecore2OWL

Tool to transform Ecore (Meta-)Models into OWL Ontologies.

Please, also look at our documentation, especially the mapping.

Installation

Currently, this is still work in progress and checking out the repository and importing it to your eclipse workspace (also see Development). However, there is a preliminary (nightly) updatesite available at https://kit-sdq.github.io/Ecore2OWL/updatesite/. Add this site in your eclipse to install it (via Help->Install New Software->Add). Keep in mind that the provided version of Ecore2OWL might be broken.

How to use

When the tool is installed, you can access it via the run configuration menu (Run->Run Configuration). In there, there is the Ecore2OWL Application. Create a (new) configuration for it and add the necessary information about the (ecore) model-files and where the output should be saved to. You have two options: First, the meta-models will be loaded from your installed meta-models in the eclipse instance. Second, you can select the meta-models that shall be used for the resource resolution. This step is needed to figure out the corresponding meta-models for your models.

You can select multiple models that are all processed and transformed into a single OWL-file.

Development

First, install the needed development plugins from the update site or the external deps updatesite.

Building this project can simply be done with the following command utilizing maven tycho to build the eclipse plugins:

mvn clean package

For development, check out this repo and import all projects into your eclipse workspace via Import->Existing Projects into Workspace and then selecting the folder where you checked out this repository. Make sure to tick the option to Search for nested projects. With the projects in your workspace, you can test the plugins by starting a "inner eclipse" that also loads the plugins in development within your workspace. For this, add a run configuration (Run->Run Configuration) as Eclipse Application. Make sure that the execution environment is properly set und that the it runs a product (not an application). Also, it is usually best to run with all plug-ins, but you can also only select the plug-ins that you actually want and need.

Here is an overview of the different projects and what they do:

• bundles/edu.kit.ipd.are.ecore2owl.core: Core logic for the transformation.
• bundles/edu.kit.ipd.are.ecore2owl.ui: Code for the integration into the eclipse UI (as run configuration).
• features/* : Feature definitions
• releng/* : Release Engineering including configuration for the updatesite as well as a (basic) configuration, i.e., parent-pom
• tests/* : Contains the tests

Adding new (non eclipse) dependencies

To add new dependencies (or new versions of dependencies), simply modify the external.p2 pom.xml. The CI will deploy the actual development dependencies to external deps updatesite.