Modeling OWL with Rules: The ROWL Protege Plugin
In our experience, some ontology users find it much easier to convey logical statements using rules rather than OWL (or description logic) axioms. Based on recent theoretical developments on transformations between rules and description logics, we develop ROWL, a Protege plugin that allows users to enter OWL axioms by way of rules; the plugin then automatically converts these rules into OWL DL axioms if possible, and prompts the user in case such a conversion is not possible without weakening the semantics of the rule.
Code (0)
등록된 구현이 없습니다.
Similar Papers 제목 키워드 기반
Rule-based OWL Modeling with ROWLTab Protege Plugin
It has been argued that it is much easier to convey logical statements using rules rather than OWL (or description logic (DL)) axioms. Based on recent theoretical developments on transformations between rules and DLs, we…
OWLAx: A Protege Plugin to Support Ontology Axiomatization through Diagramming
Once the conceptual overview, in terms of a somewhat informal class diagram, has been designed in the course of engineering an ontology, the process of adding many of the appropriate logical axioms is mostly a routine ta…
DeFind: A Protege Plugin for Computing Concept Definitions in EL Ontologies
We introduce an extension to the Protege ontology editor, which allows for discovering concept definitions, which are not explicitly present in axioms, but are logically implied by an ontology. The plugin supports ontolo…
Toward an NLG System for Bantu languages: first steps with Runyankore (demo)
There are many domain-specific and language-specific NLG systems, of which it may be possible to adapt to related domains and languages. The languages in the Bantu language family have their own set of features distinct …
Text GenerationTest-Driven Development of ontologies (extended version)
Emerging ontology authoring methods to add knowledge to an ontology focus on ameliorating the validation bottleneck. The verification of the newly added axiom is still one of trying and seeing what the reasoner says, bec…
test driven development