search

opencaesar / owl-adapter

The OML adapter for OWL
Apache License 2.0
0 stars 2 forks source link

OML to OWL relation translation #56

Open HL-hud opened 2 years ago

HL-hud commented 2 years ago

Hi,

I am testing OML and I have a question about the way it is translated to OWL. Using one additional abstraction layer to represent a "Multi-domain Multi-range relation" relation (or maybe multiple in one side only) can be accepted under the hat of "correct by construction" where it is not allowed under OML. However, I can't see why a relation is translated to an OWL class rather than an object property directly when now attributes or additional information are specified for the relation.

exp6

exp2

The object property part_of seems to not have any link to the added class Part_of. I can remove the relation classes under OWL but the reasoner within OML looks to be using this translation. image

Examples of relations such as affects and characterizes in your tutorials

exp3 exp4

At the end, what is the point behind adding the hasSource and hasTarget relations when generating the OWL file? I am just refering to the vocabulary specification and mainly interested in sharing knowledge as OWL ontology in addition to descriptions. Thanks in advance for your clarifications

exp5
HL-hud commented 2 years ago

I suggest the following:

When definning an ontology, we usually want to share the vocabulary (not only provide a tool) So, if we can have an option to generate the OWL vocabulary file with : 1- relations translated to object properties only unless the relation includes attributes 2- have the option to translate it as it is now to enable the description definition and end user interface Thanks