The paper presents the OWLOOP API, which addresses the challenges of mapping OWL axioms and OOP object hierarchies. OWL ontologies encode knowledge through hierarchies that can change at runtime due to reasoning, whereas OOP hierarchies are typically static.
The key aspects of the OWLOOP API are:
It implements a passive OWL to OOP mapping strategy, which does not limit the reasoning capabilities of the ontology. This is achieved by using the factory design pattern to decouple the OWL and OOP hierarchies.
OWLOOP provides an abstraction layer on top of the factory pattern to offer an OOP-like interface for manipulating ontological knowledge. This includes methods for reading, writing, and building OOP descriptors that represent OWL axioms.
The descriptors in OWLOOP encapsulate OWL entities (classes, properties, individuals) and expressions, and provide an OOP-based way to access and modify the ontological knowledge.
OWLOOP defines primitive descriptors for different OWL semantics, which can be aggregated to create compound descriptors. This allows software components to customize the amount of ontological knowledge they need to interface with.
The paper demonstrates the benefits of OWLOOP through examples involving a robot navigating a smart environment. It shows how OWLOOP enables dynamic mapping of OWL knowledge into OOP attributes, synchronization between the ontology and software components, and polymorphic extension of OOP objects based on ontological relationships.
Overall, OWLOOP aims to improve the modularity and flexibility of software architectures that leverage ontological reasoning, by providing an intuitive OOP-based interface to the ontology.
To Another Language
from source content
arxiv.org
Key Insights Distilled From
by Luca Buoncom... at arxiv.org 04-16-2024
https://arxiv.org/pdf/2404.09305.pdfDeeper Inquiries