1 / 23

Tracking name patterns in OWL ontologies

Tracking name patterns in OWL ontologies. Ondřej Šváb and Vojtěch Svátek The University of Economics The Department of Information and Knowledge Engineering. Motivation of the research. Exploitation of the ‘ intentions of ontology designers ’ as implicit knowledge

terrymcnew
Download Presentation

Tracking name patterns in OWL ontologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tracking name patterns in OWL ontologies Ondřej Šváb and Vojtěch Svátek The University of Economics The Department of Information and Knowledge Engineering Tracking Name Patterns in OWL Ontologies

  2. Motivation of the research • Exploitation of the ‘intentions of ontology designers’ as implicit knowledge • They can be seen as patterns • Name patterns • Logical patterns (n-ary relation, classes as values) • Their combination Tracking Name Patterns in OWL Ontologies

  3. General Goal • Understanding of the structure of concepts in OWL ontologies, • Detecting modelling errors, • Assessing quality of OWL ontologies. Tracking Name Patterns in OWL Ontologies

  4. Current goal • name patterns in taxonomic paths in OWL ontologieswrt. our previous goals: • understanding of the structure of concepts in OWL ontologies, • detecting modelling errors, • assessing quality of OWL ontologies. Tracking Name Patterns in OWL Ontologies

  5. Assumptions for Name Patterns • naming policy • the intentions of the designers • self-explaining concept names • but, it also depends on domain... Tracking Name Patterns in OWL Ontologies

  6. Agenda for the rest of the talk • Atomic Name Patterns • Complex Name Patterns – incorporated in hypotheses • Experiments with real ontologies • Conclusions • Future work Tracking Name Patterns in OWL Ontologies

  7. Agenda for the rest of the talk • Atomic Name Patterns • Complex Name Patterns – incorporated in hypotheses • Experiments with real ontologies • Conclusions • Future work Tracking Name Patterns in OWL Ontologies

  8. Atomic Name Pattern 1 • at a token level • Token-level relationship: • Prefix extension • WrittenDocument, HandWrittenDocument • Infix extension • WrittenDocument, WrittenLegalDocument • Postfix extension • WrittenDocument,WrittenDocumentWithComments Tracking Name Patterns in OWL Ontologies

  9. Atomic Name Pattern 2 • Identification of the main term • Prefix extension • WrittenDocument = main term • HandWrittenDocument • Infix extension • WrittenDocument = main term • WrittenLegalDocument • Postfix extension • WrittenDocument = main term • WrittenDocumentWithComments • Technically, delimiters divide parts of terms • Underscore (Concept_name) • Hyphen (Concept-name) • Change of lowercase letter to uppercase letter (ConceptName) Tracking Name Patterns in OWL Ontologies

  10. Agenda for the rest of the talk • Atomic Name Patterns • Complex Name Patterns – incorporated in hypotheses • Experiments with real ontologies • Conclusions • Future work Tracking Name Patterns in OWL Ontologies

  11. Hypotheses • Hypotheses using complex name patterns • 1st hypothesis If the main term in the name of a class and themain term in the multiwordname of its immediate subclass do not correspond or agree then it is likely that there is aconceptual incoherence. Correspondence in terms of token-level relationship (name patterns) Tracking Name Patterns in OWL Ontologies

  12. 1st hypothesis • Example of pattern compliance Class: ATOMissionPlan Subclasses: IndividualLocationReconnaissanceRequestMission MissileWeaponAttackMission ‘Plan’ token missing. Other subclasses do have it. TP Tracking Name Patterns in OWL Ontologies

  13. 1st hypothesis • Example of pattern non-compliance Class: ATOMission Subclasses: AircraftRepositioning According to available comments, it means AircraftRepositioningMission. It is acceptable, though it is not a hyponym of ‘mission’ in WordNet. FP Tracking Name Patterns in OWL Ontologies

  14. 3rd hypothesis Concept with the same main term in theirnames should not occur inseparate taxonomic paths. An example of pattern compliance Three root classes which have token ‘Mission’ as the main term: ATOMission AirTankerMission AirliftMission It can be used as a hint to merge these branches of taxonomies. Tracking Name Patterns in OWL Ontologies

  15. 4th hypothesis If two taxonomy paths exist such that one containsa class X and itssubclass Y, and the other contains a class Z and its subclass W, such that the name ofX is a token-level extension of the name of Z, with a different main term, and the name ofY is a token-level extension of the name of W, with a different main term, then both pathsshould be linked with some property and the name pattern should probably apply forthe descendants of Y and W as well. Tracking Name Patterns in OWL Ontologies

  16. 4th hypothesis Example of pattern compliance: Taxonomic paths: Car (X) CarDriver (Z) CargoCar (Y) CargoCarDriver (W) Different main terms, but token extensions. Conceptually different, but related. Tracking Name Patterns in OWL Ontologies

  17. 4th hypothesis An example of pattern compliance Root classes that are a token-level extension: ATOMission AirMovementReSupplyMission ... ATOMissionPlan AirTankerCellMissionPlan ... It will identify the ‘parallel’ taxonomies of related entities, but they are conceptually different. Tracking Name Patterns in OWL Ontologies

  18. Agenda for the rest of the talk • Atomic Name Patterns • Complex Name Patterns – incorporated in hypotheses • Experiments with real ontologies • Conclusions • Future work Tracking Name Patterns in OWL Ontologies

  19. Experimental condition • Verification of the 1st hypothesis wrt. three OWL ontologies from public repositories • Tracking prefix, infix, postfix name patterns in taxonomic paths • For identifying coherence of the main terms, WordNet was employed Tracking Name Patterns in OWL Ontologies

  20. Conclusions Accuracy quite good in case of ‘ATO MM’ ontology. Coverage of patterns differs wrt. ontology. Tracking Name Patterns in OWL Ontologies

  21. Future Work • Automatic identification of patterns in ontologies and/or non-compliance parts of taxonomies • Make formal model for capturing name patterns and hypotheses • Focus also on other lexical items in ontologies – labels, comments, propertynames, domain of property and range of property Tracking Name Patterns in OWL Ontologies

  22. Future Work • Combine name patterns and logical patterns (n-ary relations, classes as values) and their automatic identification • Making implicit knowledge explicit via ontology refactoring, transformation • It can be a preprocessing step for further tasks like ontology mapping, merging Tracking Name Patterns in OWL Ontologies

  23. Thank you for your attention! Questions or comments? Tracking Name Patterns in OWL Ontologies

More Related