Difference between revisions of "LogMap: Logic-based and Scalable Ontology Matching"
| Line 40: | Line 40: | ||
|Description=No data available now. | |Description=No data available now. | ||
|Dimensions=Accuracy | |Dimensions=Accuracy | ||
| − | |Benchmark= | + | |Benchmark=OAEI 2010 |
|Results=No data available now. | |Results=No data available now. | ||
}} | }} | ||
Latest revision as of 13:16, 12 July 2018
| LogMap: Logic-based and Scalable Ontology Matching | |
|---|---|
LogMap: Logic-based and Scalable Ontology Matching
| |
| Bibliographical Metadata | |
| Subject: | Ontology Matching |
| Year: | 2011 |
| Authors: | Ernesto Jimenez-Ruiz, Bernardo Cuenca Grau |
| Venue | ISWC |
| Content Metadata | |
| Problem: | Link Discovery |
| Approach: | No data available now. |
| Implementation: | LogMap |
| Evaluation: | Accuracy Evaluation |
Contents
Abstract
In this paper, we present LogMap, a highly scalable ontology matching system with built-in reasoning and diagnosis capabilities. To the best of our knowledge, LogMap is the only matching system that can deal with semantically rich ontologies containing tens (and even hun-dreds) of thousands of classes. In contrast to most existing tools, LogMap also implements algorithms for on the fly unsatisability detection and repair. Our experiments with the ontologies NCI, FMA and SNOMEDCT confirm that our system can efficiently match even the largest existing bio-medical ontologies. Furthermore, LogMap is able to produce a `clean' set of output mappings in many cases, in the sense that the ontology obtained by integrating LogMap's output mappings with the input ontologies is consistent and does not contain unsatisable classes.
Conclusion
In this paper, we have presented LogMap, a highly scalable ontology matching tool with built-in reasoning and diagnosis capabilities. LogMap's features and scalability behaviour make it well-suited for matching large-scale ontologies. LogMap, however, is still an early-stage prototype and there is plenty of room for improvement.
Future work
We are currently working on further optimizations, and in the near future, we are planning to integrate LogMap with a Protege-based front-end, such as the one implemented in our tool ContentMap.
Approach
Positive Aspects: No data available now.
Negative Aspects: No data available now.
Limitations: No data available now.
Challenges: No data available now.
Proposes Algorithm: No data available now.
Methodology: No data available now.
Requirements: No data available now.
Limitations: No data available now.
Implementations
Download-page: http://www.cs.ox.ac.uk/isg/projects/LogMap/
Access API: No data available now.
Information Representation: No data available now.
Data Catalogue: -
Runs on OS: No data available now.
Vendor: No data available now.
Uses Framework: No data available now.
Has Documentation URL: No data available now.
Programming Language: Java
Version: No data available now.
Platform: No data available now.
Toolbox: No data available now.
GUI: No
Research Problem
Subproblem of: No data available now.
RelatedProblem: No data available now.
Motivation: No data available now.
Evaluation
Experiment Setup: No data available now.
Evaluation Method : Use four ontologies from OAEI 2010 benchmark, calculating the classification time for these ontologies.
Hypothesis: No data available now.
Description: No data available now.
Dimensions: Accuracy
Benchmark used: OAEI 2010
Results: No data available now.
| Access API | No data available now. + |
| Event in series | ISWC + |
| Has Benchmark | OAEI 2010 + |
| Has Challenges | No data available now. + |
| Has DataCatalouge | - + |
| Has Description | No data available now. + |
| Has Dimensions | Accuracy + |
| Has DocumentationURL | http://No data available now. + |
| Has Downloadpage | http://www.cs.ox.ac.uk/isg/projects/LogMap/ + |
| Has Evaluation | Accuracy Evaluation + |
| Has EvaluationMethod | Use four ontologies from OAEI 2010 benchmark, calculating the classification time for these ontologies. + |
| Has ExperimentSetup | No data available now. + |
| Has GUI | No + |
| Has Hypothesis | No data available now. + |
| Has Implementation | LogMap + |
| Has InfoRepresentation | No data available now. + |
| Has Limitations | No data available now. + |
| Has NegativeAspects | No data available now. + |
| Has PositiveAspects | No data available now. + |
| Has Requirements | No data available now. + |
| Has Results | No data available now. + |
| Has Subproblem | No data available now. + |
| Has Version | No data available now. + |
| Has abstract | In this paper, we present LogMap, a highly … In this paper, we present LogMap, a highly scalable ontology matching system with built-in reasoning and diagnosis capabilities. To the best of our knowledge, LogMap is the only matching system that can deal with semantically rich ontologies containing tens (and even hun-dreds) of thousands of classes. In contrast to most existing tools, LogMap also implements algorithms for on the fly unsatisability detection and repair. Our experiments with the ontologies NCI, FMA and SNOMEDCT confirm that our system can efficiently match even the largest existing bio-medical ontologies. Furthermore, LogMap is able to produce a `clean' set of output mappings in many cases, in the sense that the ontology obtained by integrating LogMap's output mappings with the input ontologies is consistent and does not contain unsatisable classes. and does not contain unsatisable classes. + |
| Has approach | No data available now. + |
| Has authors | Ernesto Jimenez-Ruiz + and Bernardo Cuenca Grau + |
| Has conclusion | In this paper, we have presented LogMap, a … In this paper, we have presented LogMap, a highly scalable ontology matching tool with built-in reasoning and diagnosis capabilities. LogMap's features and scalability behaviour make it well-suited for matching large-scale ontologies. LogMap, however, is still an early-stage prototype and there is plenty of room for improvement. d there is plenty of room for improvement. + |
| Has future work | We are currently working on further optimizations, and in the near future, we are planning to integrate LogMap with a Protege-based front-end, such as the one implemented in our tool ContentMap. + |
| Has motivation | No data available now. + |
| Has platform | No data available now. + |
| Has problem | Link Discovery + |
| Has relatedProblem | No data available now. + |
| Has subject | Ontology Matching + |
| Has vendor | No data available now. + |
| Has year | 2011 + |
| ImplementedIn ProgLang | Java + |
| Proposes Algorithm | No data available now. + |
| RunsOn OS | No data available now. + |
| Title | LogMap: Logic-based and Scalable Ontology Matching + |
| Uses Framework | No data available now. + |
| Uses Methodology | No data available now. + |
| Uses Toolbox | No data available now. + |
