A View of OWL From the Field: Use-cases and Experiences

Aaron Kershenbaum, Achille Fokoue, Chintan Patel, Christopher A. Welty, Edith Schonberg, James J. Cimino, Li Ma, Kavitha Srinivas, Robert J. Schloss, J. William MurdockOWLED 2006 · OpenReview

Abstract

While the Web Ontology Language (OWL) offers a powerful suite of logical tools, many real-world applications utilize it only for basic taxonomies. This paper bridges the "usability gap" by presenting four diverse case studies—ranging from medical dictionaries to software engineering—where the adoption of OWL’s full expressivity, including negation and automated reasoning, yielded significant benefits. These include identifying critical modeling errors, improving clinical trial matching, and automatically cleaning noisy datasets.

Introduction

In the early 2000s, a significant gap emerged between the theoretical capabilities of OWL and its practical application. While researchers developed rich logical constructs, practitioners often built massive ontologies, such as SNOMED-CT, that functioned primarily as simple "is-a" trees. This hesitation often stems from the perceived costs of complexity and computational overhead. This paper provides concrete evidence that the benefits of migrating from simple taxonomies to expressive OWL ontologies—specifically through Description Logic (DL) reasoning—far outweigh these costs.

Case Studies in OWL Expressivity

1. Automated Classification in Medical Terminologies

Using the Medical Entities Dictionary (MED), the authors transformed frame-based laboratory concepts into OWL. By defining tests based on the substance measured and the sample used, DL reasoning was employed to automatically re-classify the hierarchy, uncovering missing relationships and inconsistencies that manual review had overlooked.

2. Clinical Trial Matching via Negation

Modeling clinical trial criteria requires more than simple taxonomies; it necessitates the ability to define what a patient must not have. By representing inclusion and exclusion criteria as ABox (Assertional Box) queries, the authors utilized negation to ensure medical safety and trial integrity. Simple taxonomies struggle to define these complex "exclusion" boundaries essential for patient safety.

Mapping clinical trial inclusion and exclusion criteria to complex OWL expressions.

3. Semantic Constraint Checking in Text Mining

In automated text analysis (using the UIMA framework), OWL constraints like disjointness were used to validate annotator output. For instance, if an entity was labeled as both a "Person" and an "Organization," the ontology flagged a logical inconsistency. This allowed for the automatic identification and removal of over 34,000 incorrect inferences in a large-scale dataset.

Inconsistent annotations across different annotators for the same entity instance.

4. Software Traceability and TBox Refinement

In software engineering, the authors increased TBox (Terminological Box) expressiveness by defining classes as complements of others. This allowed for the detection of data inconsistencies, such as a naming bug in a Java analysis tool that failed to distinguish between nested and top-level classes.

Key Insights and Results

The application of OWL reasoning across these domains provided several critical advantages:

  • Error Detection: In the MED study, the reasoner identified 44 new relationships. While 26 were correct, the "false positives" were arguably more valuable, as they revealed systematic human modeling errors where logic was applied inconsistently.
  • Data Cleaning: In a dataset of nearly 2 million triples from automated text mining, OWL constraints identified and discarded 34,490 incorrect inferences, cleaning the knowledge base without manual intervention.
  • Scalability: The studies demonstrated that modern DL reasoners can handle large-scale ontologies (10,000+ concepts) and massive triple sets, providing actionable insights that manual review cannot achieve.

Conclusion

While a "real cost" exists in terms of specialized training and logic design, the transition to expressive OWL ontologies provides essential capabilities for modern data-driven fields. Future work will focus on expanding this library of use cases to further encourage industry adoption of the full Semantic Web stack.

Summary updated

BibTeX
@inproceedings{kershenbaum2006view,
  author = {Aaron Kershenbaum and Achille Fokoue and Chintan Patel and Christopher A. Welty and Edith Schonberg and James J. Cimino and Li Ma and Kavitha Srinivas and Robert J. Schloss and J. William Murdock},
  title = {{A View of OWL From the Field: Use-cases and Experiences}},
  booktitle = {OWLED},
  year = {2006},
  url = {https://openreview.net/forum?id=zxzG4wL0td},
}
Figure