Your SlideShare is downloading. ×
Combining ontology-enriched Domain-Specific Languages Workshop on Transforming and Weaving Ontologies in Model Driven Engi...
Objectives <ul><li>Motivation </li></ul><ul><ul><li>Scenario </li></ul></ul><ul><li>Foundations </li></ul><ul><ul><li>Meta...
Integration Scenarios BEDSL Metamodel OWL Metamodel transform BEDSL+OWLMetamodel + BEDSL+OWL Model BEDSL+PDDSL+OWL Model t...
Scenario 1 <ul><li>Integration of DSLs and ontology languages allows: </li></ul><ul><ul><li>Using the structural DSL to bu...
Scenario 2 <ul><li>Integration of ontology-enriched DSLs </li></ul><ul><ul><li>Combination of domain models </li></ul></ul...
Metamodel (BEDSL) <ul><li>BEDSL – Business Entity Domain Specific Language </li></ul><ul><li>BEDSL models (M1 layer) confo...
Metamodel (PDDSL) <ul><li>PDDSL – Physical Device Domain Specific Language </li></ul><ul><li>PDDSL models (M1 layer) confo...
Description Logics <ul><li>Description Logics (DLs) are logics designed to represent and reason on structured knowledge </...
Example (OWL2) <ul><li>Class: Device </li></ul><ul><li>Class: Cisco7603 </li></ul><ul><li>SubClassOf: Device,  </li></ul><...
Metamodel of OWL2 (Excerpt) M2 layer OWL2 Metamodel
Integration (BEDSL + OWL) <ul><li>Combine BEDSL  Entity  and OWL  Class </li></ul>M2 layer M1 layer conformsTo conformsTo
Integration (PDDSL + OWL) <ul><li>Combine PDDSL  Element  and OWL  Class </li></ul>M2 layer M1 layer conformsTo conformsTo
Combination of ontology-enriched DSLs  <ul><li>Combination of BEDSL+OWL language and PDDSL+OWL language </li></ul><ul><li>...
Transformation-based Integration <ul><ul><li>Transformation at M2 layer </li></ul></ul><ul><ul><li>Define which metamodel ...
Merge Transformation <ul><li>Merge Transformation </li></ul><ul><li>Merge of: </li></ul><ul><ul><li>metaconcepts  MA  and ...
Specialization Transformation <ul><li>Specialization Transformation </li></ul><ul><li>Create specialization relationship b...
Example (ok) <ul><li>Merge of BEDSL  Entity  and PDDSL  Element </li></ul><ul><li>Transformation at M2 layer: </li></ul><u...
Example (not ok) <ul><li>Merge of BEDSL  Entity  and PDDSL  Element </li></ul><ul><li>Transformation at M2 layer: </li></u...
Conclusion <ul><li>Combination of metamodels and domain models: Combining modeling languages with existing models and cons...
Finally <ul><li>Thanks for your attention </li></ul><ul><li>supported by </li></ul>www.most-project.eu
Upcoming SlideShare
Loading in...5
×

Combining ontology-enriched Domain-Specific Languages

773

Published on

Talk at the 2nd Workshop on Transforming and Weaving Ontologies in Model Driven Engineering (co-located with MoDELS 2009), 4 October 2009, Denver, United States.

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
773
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Enriching of languages Combining DSL metamodel and OWL2 metamodel Integrating ontology-enriched DSLs Combining DSL metamodels and DSL models
  • - Metamodel of BEDSL
  • - Metamodel of BEDSL
  • anpassen
  • Eventuell noch hasSupertype Association in M2 einfügen
  • Not possible with OCL OCL works on intsances (M0 layer)
  • Transcript of "Combining ontology-enriched Domain-Specific Languages"

    1. 1. Combining ontology-enriched Domain-Specific Languages Workshop on Transforming and Weaving Ontologies in Model Driven Engineering (TWOMDE) 04.10.2009, Denver, Colorado Tobias Walter Jürgen Ebert
    2. 2. Objectives <ul><li>Motivation </li></ul><ul><ul><li>Scenario </li></ul></ul><ul><li>Foundations </li></ul><ul><ul><li>Metamodels </li></ul></ul><ul><ul><li>Description Logics </li></ul></ul><ul><li>Integration </li></ul><ul><ul><li>enriching DSLs by ontology languages </li></ul></ul><ul><ul><li>combining ontology-enriched DSLs </li></ul></ul><ul><li>Conclusion </li></ul>
    3. 3. Integration Scenarios BEDSL Metamodel OWL Metamodel transform BEDSL+OWLMetamodel + BEDSL+OWL Model BEDSL+PDDSL+OWL Model transform BEDSL+PDDSL+OWL Metamodel PDDSL Metamodel OWL Metamodel PDDSL+OWLMetamodel + transform + PDDSL+OWL Model + Scenario 1 (WCDSL Paper) Scenario 2 (here)
    4. 4. Scenario 1 <ul><li>Integration of DSLs and ontology languages allows: </li></ul><ul><ul><li>Using the structural DSL to build domain models </li></ul></ul><ul><ul><li>Creating additional (local or global) annotations to define constraints and axioms to restrict the usage of concepts in the model and to allow reasoning </li></ul></ul>Comarch Domain Model:
    5. 5. Scenario 2 <ul><li>Integration of ontology-enriched DSLs </li></ul><ul><ul><li>Combination of domain models </li></ul></ul><ul><ul><li>Domain models contain concepts with instances </li></ul></ul><ul><ul><li>Combination constraints and semantics </li></ul></ul>merge model elements merge model elements + constraints Comarch Domain Model BEDSL model PDDSL model
    6. 6. Metamodel (BEDSL) <ul><li>BEDSL – Business Entity Domain Specific Language </li></ul><ul><li>BEDSL models (M1 layer) conform to metamodel (M2 layer) </li></ul>M2 layer M1 layer BEDSL Metamodel BEDSL Model conformsTo conformsTo
    7. 7. Metamodel (PDDSL) <ul><li>PDDSL – Physical Device Domain Specific Language </li></ul><ul><li>PDDSL models (M1 layer) conform to metamodel (M2 layer) </li></ul>M2 layer M1 layer PDDSL Metamodel PDDSL Model conformsTo conformsTo
    8. 8. Description Logics <ul><li>Description Logics (DLs) are logics designed to represent and reason on structured knowledge </li></ul><ul><li>The domain of interest is structured into ( TBox ): </li></ul><ul><ul><li>concepts, which correspond to classes, and denote sets of individuals </li></ul></ul><ul><ul><li>roles, which correspond to associations, and denote binary relations on individuals </li></ul></ul><ul><li>The knowledge is asserted through so-called assertions ( ABox ) </li></ul><ul><li>DLs provide the foundations for standard ontology languages, like OWL2 </li></ul>
    9. 9. Example (OWL2) <ul><li>Class: Device </li></ul><ul><li>Class: Cisco7603 </li></ul><ul><li>SubClassOf: Device, </li></ul><ul><li> hasConfiguration exactly 1 Configuration7603 </li></ul><ul><li>Class: Configuration </li></ul><ul><li>Class: Configuration7603 </li></ul><ul><li>SubClassOf: Configuration </li></ul><ul><li>ObjectProperty: hasConfiguration </li></ul><ul><li>Domain: Device </li></ul><ul><li>Range: Configuration </li></ul>M1 layer
    10. 10. Metamodel of OWL2 (Excerpt) M2 layer OWL2 Metamodel
    11. 11. Integration (BEDSL + OWL) <ul><li>Combine BEDSL Entity and OWL Class </li></ul>M2 layer M1 layer conformsTo conformsTo
    12. 12. Integration (PDDSL + OWL) <ul><li>Combine PDDSL Element and OWL Class </li></ul>M2 layer M1 layer conformsTo conformsTo
    13. 13. Combination of ontology-enriched DSLs <ul><li>Combination of BEDSL+OWL language and PDDSL+OWL language </li></ul><ul><li>Allows for multi-viewpoint modeling of business entities and device configurations </li></ul><ul><li>Integration of: </li></ul><ul><ul><li>Metamodels at M2 layer </li></ul></ul><ul><ul><li>Conforming models at M1 layer </li></ul></ul><ul><ul><li>Semantics and constraints of domain models </li></ul></ul><ul><li>Problem: </li></ul><ul><ul><li>How and when to combine domain model elements? </li></ul></ul><ul><ul><li>How to combine constraints and semantics? </li></ul></ul>
    14. 14. Transformation-based Integration <ul><ul><li>Transformation at M2 layer </li></ul></ul><ul><ul><li>Define which metamodel elements are combined </li></ul></ul><ul><ul><li>Corresponding Transformation at M1 layer </li></ul></ul><ul><li>Define which conforming model elements are transformed </li></ul><ul><li>Pre-condition of applying the transformation on A and B </li></ul><ul><li>Extracted from additional intensional semantics of domain model elements </li></ul><ul><li>(e.g. A and B are equivalent domain concepts and can be merged) </li></ul>
    15. 15. Merge Transformation <ul><li>Merge Transformation </li></ul><ul><li>Merge of: </li></ul><ul><ul><li>metaconcepts MA and MB to MC (at M2 layer) </li></ul></ul><ul><ul><li>concepts A and B to C , if the following pre-condition holds: </li></ul></ul><ul><li>Constraints of merged model elements are transformed with regard to the precondition </li></ul>Class: A EquivalentWith: B
    16. 16. Specialization Transformation <ul><li>Specialization Transformation </li></ul><ul><li>Create specialization relationship between metaconcepts MA and MB (at M2 layer) </li></ul><ul><li>Concepts A and B are transformed, if the following pre-condition holds: </li></ul><ul><li>Constraints of model element B are transformed with regard to the precondition </li></ul>Class: A SubClassOf: B
    17. 17. Example (ok) <ul><li>Merge of BEDSL Entity and PDDSL Element </li></ul><ul><li>Transformation at M2 layer: </li></ul><ul><li>Tranformation at M1 layer: </li></ul>1) merge model elements 2) merge constraints
    18. 18. Example (not ok) <ul><li>Merge of BEDSL Entity and PDDSL Element </li></ul><ul><li>Transformation at M2 layer: </li></ul><ul><li>Tranformation at M1 layer: </li></ul>1) merge model elements 2) merge constraints unsatisfiable class
    19. 19. Conclusion <ul><li>Combination of metamodels and domain models: Combining modeling languages with existing models and constraints </li></ul><ul><li>Integration at M2 layer: Transformations define how to combine metamodels </li></ul><ul><li>Integration at M1 layer: </li></ul><ul><ul><li>Transformations of model elements to target model </li></ul></ul><ul><ul><li>Transformation and recalculation of constraints of model elements in the target model </li></ul></ul><ul><li>Usage of reasoning technology to verify model correctness </li></ul>
    20. 20. Finally <ul><li>Thanks for your attention </li></ul><ul><li>supported by </li></ul>www.most-project.eu

    ×