Extend Ecore with OWL by Ecore Annotations of OWL Axioms

Do you want more expressiveness than Ecore can offer?

In this video we show how to use an ecore textual language for annotating ecore metamodels with OWL axioms. Afterwards, you can use the OWLizer to transform metamodel and model into OWL.

OWL + Metamodel: Model Bridge

Model bridges connect software models and ontologies on the modeling layer M1. They are de fined in the metamodeling layer M2 between diff erent metamodels. The figure below exemplifies a model bridge.

Model Bridge

Integration bridges merge information of the models from the software modeling and from the ontology space. This allows the building of integrated models (on modeling layer M1) using constructs of both modeling languages in a combined way, e.g. to integrate UML class diagrams and OWL.

A transformation bridge describes a (physical) transformation between models in layer M1. The models are kept separately in both modeling spaces. The information is moved from one model to the model in the other modeling space according to the transformation bridge.

Ecore Models | Metamodels -> OWL Ontologies = OWLizer

We show how to use TwoUse's OWLizer to transform Ecore Models and Metamodels into OWL ontologies. In this example, the UML class diagram model elements are transformed into OWL individuals of the UML ontology and the UML metamodel classes are transformed into OWL classes.

UML + OWL Ontology and SPARQL

This demo of the TwoUse Toolkit shows UML class diagram, OWL ontology and SPARQL to dynamically classify instances at runtime. We model the variations of the class SalesOrder with the web ontology language, namely USSalesOrder and GermanSalesOrder. Later, we write a query operation that asks for the most specific type of the contextual object.

OWL ontology with UML Class Diagram Profile for OWL

How to create a simple OWL ontology using the OMG UML Profile for OWL with the TwoUse Toolkit.

Improving Software Design Patterns with UML, OWL and SPARQL

We deal with problems in common design patterns and proposes OWL to remedy these issues. We exploit the TwoUse approach, which integrates OWL and UML class diagrams to overcome drawbacks of the Strategy Pattern, that are also extensible to the Abstract Factory Pattern.

UML, OWL and SPARQL with TwoUse Toolkit - Demo

Since MDE and OWL provide complementary benefits, contemporary software development should make use of both approaches. This demo presented at the Sixth European Conference on Modeling Foundations and Applications enlightens the improvements from an integrated approach.

Filling the Gap between Semantic Web and Model Driven Engineering

Since model driven engineering and semantic web provide complementary benefits, contemporary software development and code generation should make use of both approaches. This talk enlightens the improvements on both fields from an integrated approach: the TwoUse approach.

Creating SWRL Rules with UML Class Diagram Profile for SWRL

Since it's already possible to create ontologies using the UML Profile for OWL , a new UML Profile for SWRL was developed to enhance ontologies with SWRL Rules. SWRL combines OWL (DL and Lite) and RuleML, so therefore the set of OWL Axioms will be extended to include Horn-like rules. It thus enables Horn-like rules to be combined with an OWL knowledge base, so that reasoning against those rules will be possible.

Example

This image depicts a sample UML diagram using the UML Profile for OWL .

This image depicts a sample UML diagram using both the UML Profile for OWL and UML Profile for SWRL .

This sample file is part of the offered examples when using the TwoUse Toolkit. More information on http://twouse.googlecode.com/