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
Is your feature request related to a problem? Please describe.
Whenever I have a look at your (otherwise very good) gUFO documentation, particularly on Object Properties, the characteristics of the property are not always mentioned explicitly. I consider this a shortcoming of the documentation, since it requires the user to look that up in the gufo.ttl file, which is unwieldy.
Describe the solution you'd like
Please add the characteristics, i.e., (inverse)functional, transitive, symmetric, asymmetric, reflexive, irreflexive, to each property in the documentation. This could be done in a similar fashion as in the Protégé documentation, an example shown below:
Describe alternatives you've considered
As indicated, this information indeed is available in the gufo.ttl specification. However, I consider that not the right location to search for information.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Whenever I have a look at your (otherwise very good) gUFO documentation, particularly on Object Properties, the characteristics of the property are not always mentioned explicitly. I consider this a shortcoming of the documentation, since it requires the user to look that up in the gufo.ttl file, which is unwieldy.
Describe the solution you'd like
Please add the characteristics, i.e., (inverse)functional, transitive, symmetric, asymmetric, reflexive, irreflexive, to each property in the documentation. This could be done in a similar fashion as in the Protégé documentation, an example shown below:
Describe alternatives you've considered
As indicated, this information indeed is available in the gufo.ttl specification. However, I consider that not the right location to search for information.
The text was updated successfully, but these errors were encountered: