description logics for information modelling and access
play

(Description) Logics for Information Modelling and Access - or - - PowerPoint PPT Presentation

(Description) Logics for Information Modelling and Access - or - How to Use an Ontology Enrico Franconi franconi@inf.unibz.it http://www.inf.unibz.it/franconi Faculty of Computer Science, Free University of Bozen-Bolzano (1/31) Summary


  1. (Description) Logics for Information Modelling and Access - or - How to Use an Ontology Enrico Franconi franconi@inf.unibz.it http://www.inf.unibz.it/˜franconi Faculty of Computer Science, Free University of Bozen-Bolzano (1/31)

  2. Summary • What is an Ontology • Description Logics for Conceptual Modelling • Queries with an Ontology (2/31)

  3. What is an Ontology • An ontology is a formal conceptualisation of the world: a conceptual schema. (3/31)

  4. What is an Ontology • An ontology is a formal conceptualisation of the world: a conceptual schema. • An ontology specifies a set of constraints, which declare what should necessarily hold in any possible world. (3/31)

  5. What is an Ontology • An ontology is a formal conceptualisation of the world: a conceptual schema. • An ontology specifies a set of constraints, which declare what should necessarily hold in any possible world. • Any possible world should conform to the constraints expressed by the ontology. (3/31)

  6. What is an Ontology • An ontology is a formal conceptualisation of the world: a conceptual schema. • An ontology specifies a set of constraints, which declare what should necessarily hold in any possible world. • Any possible world should conform to the constraints expressed by the ontology. • Given an ontology, a legal world description is a finite possible world satisfying the constraints. (3/31)

  7. Ontology languages and Conceptual Data Models • An ontology language usually introduces concepts (aka classes, entities), properties of concepts (aka slots, attributes, roles), relationships between concepts (aka associations), and additional constraints. (4/31)

  8. Ontology languages and Conceptual Data Models • An ontology language usually introduces concepts (aka classes, entities), properties of concepts (aka slots, attributes, roles), relationships between concepts (aka associations), and additional constraints. • Ontology languages may be simple (e.g., having only concepts and taxonomies), frame-based (having only concepts and properties), or logic-based (e.g. Ontolingua, DAML+OIL, OWL). (4/31)

  9. Ontology languages and Conceptual Data Models • An ontology language usually introduces concepts (aka classes, entities), properties of concepts (aka slots, attributes, roles), relationships between concepts (aka associations), and additional constraints. • Ontology languages may be simple (e.g., having only concepts and taxonomies), frame-based (having only concepts and properties), or logic-based (e.g. Ontolingua, DAML+OIL, OWL). • Ontology languages are typically expressed by means of diagrams. (4/31)

  10. Ontology languages and Conceptual Data Models • An ontology language usually introduces concepts (aka classes, entities), properties of concepts (aka slots, attributes, roles), relationships between concepts (aka associations), and additional constraints. • Ontology languages may be simple (e.g., having only concepts and taxonomies), frame-based (having only concepts and properties), or logic-based (e.g. Ontolingua, DAML+OIL, OWL). • Ontology languages are typically expressed by means of diagrams. • Entity-Relationship schemas and UML class diagrams can be considered as ontologies. (4/31)

  11. UML Class Diagram Employee Works-for PaySlipNumber:Integer Salary:Integer 1.. ⋆ Project Manager ProjectCode:String 1..1 { disjoint,complete } Manages AreaManager TopManager 1..1 (5/31)

  12. Entity-Relationship Schema PaySlipNumber(Integer) Salary(Integer) Employee Works-for (1,n) ProjectCode(String) Manager Project × (1,1) (1,1) AreaManager TopManager Manages (6/31)

  13. The role of a Conceptual Schema Conceptual Schema Logical Schema Data Store (7/31)

  14. The role of a Conceptual Schema Constraints Conceptual Schema Logical Schema Data Store (7/31)

  15. The role of a Conceptual Schema Constraints Conceptual Schema Logical Query Result Schema Data Store (7/31)

  16. The role of a Conceptual Schema Deduction Constraints Conceptual Schema Logical Query Result Schema Data Store (7/31)

  17. The role of a Conceptual Schema Deduction Constraints Conceptual Schema Logical Query Result Schema Data Store (7/31)

  18. Reasoning with Ontologies Employee Works-for PaySlipNumber:Integer Salary:Integer 1.. ⋆ Project Manager ProjectCode:String 1..1 { disjoint,complete } Manages AreaManager TopManager 1..1 • Managers do not work for a project (she/he just manages it): ∀ x . Manager ( x ) → ∀ y . ¬ WORKS - FOR ( x, y ) (8/31)

  19. Reasoning with Ontologies Employee Works-for PaySlipNumber:Integer 1.. ⋆ Salary:Integer 1.. ⋆ Project Manager ProjectCode:String 1..1 { disjoint,complete } Manages AreaManager TopManager 1..1 • Managers do not work for a project (she/he just manages it): ∀ x . Manager ( x ) → ∀ y . ¬ WORKS - FOR ( x, y ) • If the minimum cardinality for the participation of employees to the works-for relationship is increased, then . . . (8/31)

  20. Summary • Logic and Conceptual Modelling • Description Logics for Conceptual Modelling • Queries with an Ontology (9/31)

  21. Encoding ontologies in Description Logics • Object-oriented data models (e.g., UML and ODMG) • Semantic data models (e.g., EER and ORM) • Frame-based and web ontology languages (e.g., DAML+OIL and OWL) (10/31)

  22. Encoding ontologies in Description Logics • Object-oriented data models (e.g., UML and ODMG) • Semantic data models (e.g., EER and ORM) • Frame-based and web ontology languages (e.g., DAML+OIL and OWL) • Theorems prove that an ontology and its encoding as DL knowledge bases constrain every world description in the same way – i.e., the models of the DL theory correspond to the legal world descriptions of the ontology, and vice-versa. (10/31)

  23. Employee Works-for PaySlipNumber:Integer Salary:Integer 1.. ⋆ Project Manager ProjectCode:String 1..1 { disjoint,complete } Manages AreaManager TopManager 1..1 ⊑ emp / 2 : Employee ⊓ act / 2 : Project Works - for ⊑ man / 2 : TopManager ⊓ prj / 2 : Project Manages ∃ = 1 [ worker ]( PaySlipNumber ⊓ num / 2 : Integer ) ⊓ ⊑ Employee ∃ = 1 [ payee ]( Salary ⊓ amount / 2 : Integer ) ∃ ≤ 1 [ num ]( PaySlipNumber ⊓ worker / 2 : Employee ) ⊤ ⊑ ⊑ Employee ⊓ ( AreaManager ⊔ TopManager ) Manager ⊑ Manager ⊓ ¬ TopManager AreaManager Manager ⊓ ∃ = 1 [ man ] Manages ⊑ TopManager ∃ ≥ 1 [ act ] Works - for ⊓ ∃ = 1 [ prj ] Manages ⊑ Project · · · (11/31)

  24. Deducing constraints Employee Works-for PaySlipNumber:Integer Salary:Integer 1.. ⋆ Project Manager ProjectCode:String 1..1 { disjoint,complete } Manages AreaManager TopManager 1..1 Managers are employees who do not work for a project (she/he just manages it): Employee ⊓ ¬ ( ∃ ≥ 1 [ emp ] Works - for ) ⊑ Manager , Manager ⊑ ¬ ( ∃ ≥ 1 [ emp ] Works - for ) (12/31)

  25. Deducing constraints Employee Works-for PaySlipNumber:Integer Salary:Integer 1.. ⋆ Project Manager ProjectCode:String 1..1 { disjoint,complete } Manages AreaManager TopManager 1..1 Managers are employees who do not work for a project (she/he just manages it): Employee ⊓ ¬ ( ∃ ≥ 1 [ emp ] Works - for ) ⊑ Manager , Manager ⊑ ¬ ( ∃ ≥ 1 [ emp ] Works - for ) | For every project, there is at least one employee who is not a manager: = Project ⊑ ∃ ≥ 1 [ act ]( Works - for ⊓ emp : ¬ Manager ) (12/31)

  26. i • com : Intelligent Conceptual Modelling tool • i • com allows for the specification of multiple EER (or UML) diagrams and inter- and intra-schema constraints; • Complete logical reasoning is employed by the tool using a hidden underlying DLR inference engine; • i • com verifies the specification, infers implicit facts and stricter constraints, and manifests any inconsistencies during the conceptual modelling phase. (13/31)

  27. Summary • Logic and Conceptual Modelling • Description Logics for Conceptual Modelling • Queries with an Ontology (14/31)

  28. The role of a Conceptual Schema – revisited Conceptual Schema Logical Schema Data Store (15/31)

  29. The role of a Conceptual Schema – revisited Constraints Conceptual Schema Logical Schema Data Store (15/31)

  30. The role of a Conceptual Schema – revisited Constraints Conceptual Schema Logical Query Result Schema Data Store (15/31)

  31. The role of a Conceptual Schema – revisited Deduction Constraints Conceptual Schema Logical Query Result Schema Data Store (15/31)

  32. The role of a Conceptual Schema – revisited Deduction Constraints Conceptual Schema Logical Query Result Schema Data Store (15/31)

  33. The role of a Conceptual Schema – revisited Deduction Constraints Conceptual Schema Logical Query Result Schema Data Store (15/31)

  34. The role of a Conceptual Schema – revisited Deduction Constraints Conceptual Query Result Schema Logical Query Result Schema Data Store (15/31)

  35. The role of a Conceptual Schema – revisited Deduction Deduction Constraints Conceptual Query Result Schema Logical Query Result Schema Data Store (15/31)

  36. The role of a Conceptual Schema – revisited Deduction Deduction Constraints Conceptual Query Result Schema Logical Query Result Schema Data Store (15/31)

Recommend


More recommend