Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OML to OWL relation translation #56

Open
HL-hud opened this issue Jul 19, 2022 · 1 comment
Open

OML to OWL relation translation #56

HL-hud opened this issue Jul 19, 2022 · 1 comment
Labels
Question Further information is requested

Comments

@HL-hud
Copy link

HL-hud commented Jul 19, 2022

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 HL-hud added the Question Further information is requested label Jul 19, 2022
@HL-hud HL-hud changed the title Multi-domain Multi-range relation OML to OWL relation translation Jul 19, 2022
@HL-hud
Copy link
Author

HL-hud commented Jul 28, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant