You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Examples of relations such as affects and characterizes in your tutorials
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
The text was updated successfully, but these errors were encountered:
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
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.
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.
Examples of relations such as affects and characterizes in your tutorials
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
The text was updated successfully, but these errors were encountered: