Multi-Level Conceptual Modeling and OWL

Transcription

1 Multi-Level Conceptual Modeling and OWL Bernd Neumayr, Michael Schrefl Department of Business Informatics. Data & Knowledge Engineering, Johannes Kepler University Linz, Austria The Joint International Workshop on Metamodels, Ontologies, Semantic Technologies, and Information Systems for the Semantic Web, th International Conference on Conceptual Modeling - GRAMADO, BRAZIL 1

2 Intro Ontological Metamodeling vs. Linguistic Metamodeling Conceptual Metamodeling domain concepts with members at different abstraction levels Powertypes Materialization Deep Instantiation ti ti M-Objects and M-Relationships Metamodeling in OWL use one symbol as identifier of a class as well as of an individual undecideable in OWL Full restricted in OWL 2: Punning 2

3 Intro Contribution Transfer ideas from conceptual modeling to OWL via semantic-preserving mappings from M-Objects/M- Relationships to OWL augmented with integrity constraints (Motik et al., 2009) Motivation 1. provide querying facilities and decideable consistency checking for multi-level conceptual modeling 2. provide pattern for ontological metamodeling within decideable fragment of OWL 2 3

4 Produc ct Catalo og Product :catalog -desc:string ='Our Products' -taxrate : Integer -listprice : Float -serialnr : String M-Objects Example Product Model Physic cal Ent tity Pr roduct Cat egory 4

5 Produc ct Catalo og Product :catalog -desc:string ='Our Products' -taxrate : Integer -listprice : Float -serialnr : String M-Objects Example Pr roduct Cat egory Book -taxrate = 15 -author : String Product Model HarryPotter4 -listprice = author = 'J.K.Rowling' Physic cal Ent tity mycopyofhp4 -serialnr = 'A121212' 5

6 Produc ct Catalo og Product :catalog -desc:string ='Our Products' -taxrate : Integer -listprice : Float -serialnr : String M-Objects Example Pr roduct Cat egory Book -taxrate = 15 -author : String -taxrate = 20 -marketlaunch : Date :brand -maxspeed : Integer -mileage:integer Bra nd Porsche911 :brand -marketlaunch = porsche911club : Boolean Product Model HarryPotter4 -listprice = author = 'J.K.Rowling' Porsche911reraS -listprice = maxspeed = 293 km/h Porsche911GT3 -listprice = maxspeed = 310 km/h Physic cal Ent tity mycopyofhp4 -serialnr = 'A121212' myporsche911reras -serialnr = 'C ' -mileage = porsche911club = true 6

7 Product :catalog Company :root M-Relationships Example :brand Porsche911 :brand producedby :industrialsector :enterprise :factory Manufacturer :industrialsector :enterprise PorscheLtd :factory :enterprise :factory A m-relationship describes relationships between m-objects at multiple levels of abstraction expresses multi-level referential integrity constraints is identified by its name and related m-objects e.g. Product-producedBy- Company Porsche911reraS myporsche911reras PorscheZuffenhausen :factory 7

8 Product :catalog Company :root M-Relationships Example producedby :brand producedby db Porsche911 :brand Porsche911reraS producedby :industrialsector :enterprise :factory Manufacturer :industrialsector :enterprise PorscheLtd :factory :enterprise :factory A m-relationship describes relationships between m-objects at multiple levels of abstraction expresses multi-level referential integrity constraints is identified by its name and related m-objects e.g. Product-producedBy- Company may be concretized (expresses instantiation and/or specialization) abstracts each level of a m-relationship recursively over several levels myporsche911reras producedby PorscheZuffenhausen :factory 8

9 Sets and Subsets of M-Objects Product Category Brand Porsche911 Model Porsche911reraS Physical Entity 9

10 Sets and Subsets of M-Objects Product Category Brand Porsche911 Model Porsche911reraS Physical Entity 10

11 Sets and Subsets of M-Objects Product Category Brand Porsche911 Model Porsche911reraS Physical Entity 11

12 Sets and Subsets of M-Objects Product Category Company Brand Industrial Sector Model Enterprise Physical Entity Factory 12

13 Sets and Subsets of M-Relationships producedby Product Category-IndustrialSector Category Company Brand Model-Enterprise Industrial Sector Model PhysicalEntity-Factory Enterprise Physical Entity Factory 13

14 Mapping M-Objects to OWL Product each m-object as individual, each abstraction level as class concretization hierarchy by property concretize concretize is functional, concretize_tt is transitive closure of concretize Category 1 concretize concretize concretize_t concretize_tt concretize concretize_tt Brand Porsche911 Model Porsche911reraS Physical Entity 14

15 Mapping M-Objects to OWL Product use transitive property concretize_t and Nominals to identify anonymous classes as entry points for queries to define extensional constraints to define and refine common characteristics of its members Category Brand Porsche911 Model Physical Entity concretize_t. Product Model concretize_t. Model concretize_t. Porsche911 Model concretize_t. Product Model concretize_t. t M Model concretize_t. Porsche911 Model concretize_t. Porsche911reraS Model 15

16 Mapping M-Objects to OWL each m-object as individual each abstraction level as primitive class each m-object assigned to abstraction level by class assertion each m-object connected with its parent Category concretize, Product -taxrate = 20 -marketlaunch : Date :brand -maxspeed : Integer -mileage:integer 16

17 Mapping M-Objects to OWL assign values of top-level attributes by property assertions -taxrate = 20 -marketlaunch : Date :brand -maxspeed : Integer -mileage:integer Category concretize, Product taxrate, 20 17

18 Mapping M-Objects to OWL common characteristics of members of certain levels of an m-object defined by subclass axioms use integrity constraints with closed world semantics in order to preserve m-object semantics Category concretize, Product taxrate, 20 IC: concretize_t. Brand marketlaunch.date 1 marketlaunch. -taxrate = 20 IC: concretize_t. Model maxspeed.integer 1 maxspeed. -marketlaunch :Date :brand IC: concretize_t. t PhysicalEntity mileage.integer 1 mileage. -maxspeed : Integer -mileage:integer 18

19 Mapping M-Objects to OWL each attribute is inducted at only one level of one m-object = domain of attribute interprete subclass axioms as integrity constraints in order to avoid unwanted inferences Category concretize, Product taxrate, 20 IC: concretize_t. Brand marketlaunch.date 1 marketlaunch. -taxrate = 20 IC: concretize_t. Model maxspeed.integer 1 maxspeed. -marketlaunch :Date :brand IC: concretize_t. t PhysicalEntity mileage.integer 1 mileage. -maxspeed : Integer -mileage:integer IC: IC: marketlaunch. concretize_t. Brand IC: maxspeed. concretize_t. Model mileage. concretize_t. PhysicalEntity 19

20 Mapping M-Objects to OWL A level l of an m-object ensures that concretization at lower levels concretize this level l, this allows stable upward navigation. Ensured for each newly introduced level. avoid unwanted inferences Category concretize, Product taxrate, 20 IC: concretize_t. Brand marketlaunch.date 1 marketlaunch. -taxrate = 20 IC: concretize_t. Model maxspeed.integer 1 maxspeed. -marketlaunch : Date :brand IC: concretize_t. t PhysicalEntity mileage.integer 1 mileage. -maxspeed : Integer -mileage:integer IC: IC: marketlaunch. concretize_t. Brand IC: maxspeed. concretize_t. Model mileage. concretize_t. PhysicalEntity IC: concretize_t. Model concretize_t. concretize_t. Brand 20

21 Mapping M-Objects to OWL each level is inducted at exactly one m-object avoid unwanted inferences Category concretize, Product taxrate, 20 IC: concretize_t. Brand marketlaunch.date 1 marketlaunch. -taxrate = 20 IC: concretize_t. Model maxspeed.integer 1 maxspeed. -marketlaunch : Date :brand IC: concretize_t. t PhysicalEntity mileage.integer 1 mileage. -maxspeed : Integer -mileage:integer IC: IC: marketlaunch. concretize_t. Brand IC: maxspeed. concretize_t. Model mileage. concretize_t. PhysicalEntity IC: concretize_t. Model concretize_t. concretize_t. Brand IC: Brand concretize_t. 21

22 Mapping M-Objects to OWL An m-object cannot belong to more than one abstraction level, thus abstraction levels are pairwise disjoint. Category concretize, Product taxrate, 20 IC: concretize_t. Brand marketlaunch.date 1 marketlaunch. -taxrate = 20 IC: concretize_t. Model maxspeed.integer 1 maxspeed. -marketlaunch : Date :brand IC: concretize_t. t PhysicalEntity mileage.integer 1 mileage. -maxspeed : Integer -mileage:integer IC: IC: marketlaunch. concretize_t. Brand IC: maxspeed. concretize_t. Model mileage. concretize_t. PhysicalEntity IC: concretize_t. Model concretize_t. concretize_t. Brand IC: Brand concretize_t. Brand Category, Brand Model,... 22

23 Mapping M-Objects to OWL The m-object approach makes the Unique Name Assumption. Thus each pair of m-objects is member of the inequality predicate. Category concretize, Product taxrate, 20 IC: concretize_t. Brand marketlaunch.date 1 marketlaunch. -taxrate = 20 IC: concretize_t. Model maxspeed.integer 1 maxspeed. -marketlaunch : Date :brand IC: concretize_t. t PhysicalEntity mileage.integer 1 mileage. -maxspeed : Integer -mileage:integer IC: IC: marketlaunch. concretize_t. Brand IC: maxspeed. concretize_t. Model mileage. concretize_t. PhysicalEntity IC: concretize_t. Model concretize_t. concretize_t. Brand IC: Brand concretize_t. Brand Category, Brand Model,... Product, Book, Porsche911,... 23

24 Mapping M-Relationships to OWL Every m-relationship as named individual connected with its parent m-relationship and its source and target, source and target t are functional: 1 source 1 target Product-producedBy-Company Product -producedby-manufacturer Category Company Brand Industrial Sector Model Enterprise Physical Entity Factory

25 Mapping M-Relationships to OWL Connection levels as anonymous classes, based on level of source and target Use transitive property concretize_t and nominals to identify extensions of an m- relationship Product-producedBy-Company Product -producedby-manufacturer concretize_t. producedby Manufacturer source.model target.enterprise Category Company Brand Porsche911-producedBy-PorscheLtd Industrial Sector Model Enterprise Physical Entity concretize_t. producedby Manufacturer source.physicalentity target.factory Factory

26 Mapping M-Relationships to OWL m-relationship as named individual connected with its parent m- relationship and its source and target :brand producedby Manufacturer :industrialsector :enterprise t d ith it t :factory 1. concretize producedby Manufacturer, Product producedby Company 2. source producedby Manufacturer, 3. target producedby Manufacturer, Manufacturer 26

27 Mapping M-Relationships to OWL in a concretization, source or target must be concretized IC to avoid unwanted inferences Manufacturer :industrialsector :brand producedby :enterprise IC t id t d :factory 1. concretize producedby Manufacturer, Product producedby Company 2. source producedby Manufacturer, 3. target producedby Manufacturer, Manufacturer 4. IC: concretize_t. r producedby Manufacturer Manufacturer source. concretize_t. target. concretize_t. Manufacturer source. concretize_t. target. concretize_t. Manufacturer Manufacturer 27

28 Mapping M-Relationships to OWL stable upward navigation for m- relationships ICs to avoid unwanted inferences Manufacturer :industrialsector :brand producedby :enterprise IC t id t d :factory 1. concretize producedby Manufacturer, Product producedby Company 2. source producedby Manufacturer, 3. target producedby Manufacturer, Manufacturer 4. IC: concretize_t. r producedby Manufacturer Manufacturer source. concretize_t. target. concretize_t. Manufacturer source. concretize_t. target. concretize_t. Manufacturer Manufacturer 5. IC: concretize_t. producedby Manufacturer source. concretize_t.model target. concretize_t.enterprise i concretize_t. concretize_t. producedby Manufacturer source.model target.enterprise 6. IC: concretize_t. producedby Manufacturer source. concretize_t.physicalentity target. concretize_t.factory concretize_t. concretize_t. producedby Manufacturer source.physicalentity target.factory 28

29 Mapping M-Relationships to OWL Unique Name Assumption :brand producedby Manufacturer :industrialsector :enterprise :factory 1. concretize producedby Manufacturer, Product producedby Company 2. source producedby Manufacturer, 3. target producedby Manufacturer, Manufacturer 4. IC: concretize_t. r producedby Manufacturer Manufacturer source. concretize_t. target. concretize_t. Manufacturer source. concretize_t. target. concretize_t. Manufacturer Manufacturer 5. IC: concretize_t. producedby Manufacturer source. concretize_t.model target. concretize_t.enterprise i concretize_t. concretize_t. producedby Manufacturer source.model target.enterprise 6. IC: concretize_t. producedby Manufacturer source. concretize_t.physicalentity target. concretize_t.factory concretize_t. concretize_t. producedby Manufacturer source.physicalentity target.factory 7. producedby Manufacturer Product producedby Company 8. producedby Manufacturer Porsche911reraS producedby PorscheLtd

30 Summary and Future Work Contribution A mapping from m-objects and m-relationships to OWL Tool-Support: (sorry, not finished yet) M-Objects and M-Relationships are modeled in Protégé Frames Export-Plugin, using OWL API M-Objects and M-Relationships can then be used in Protégé 4 Future Work Performance Studies Extended mapping based on extended m-object model (Neumayr, Schrefl, 2010) Optimized Reasoning 30

31 References Boris Motik, Ian Horrocks, Ulrike Sattler: Bridging the gap between OWL and relational databases. J. Web Sem. (WS) 7(2):74-89 (2009) Bernd Neumayr, Katharina Grün, Michael Schrefl: Multi-Level Domain Modeling with M-Objects and M-Relationships. APCCM 2009: Bernd Neumayr, Michael Schrefl, Bernhard Thalheim: Hetero- Homogeneous Hierarchies in Data Warehouses. APCCM