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
mw.data.representation could allow easier property definition #501
Comments
I don't understand what you mean with "later" and the formatting is screwed, so your pull request shows all lines as changed and it's not easy to see what you have changed. If you mean, after the ontology is registered, maybe even by a different module: Actually, this was very much intended! If by "later" you mean directly after one method call (e.g. 0.2 sec "later"), you can use
However, for convenience, the method definitions can also be changed to return the this-object instead of void to allow for multiple calls in one line, like you said: |
This exactly what the pull request imlpements (sorry for the format) I agree with you in the sense of the model being fixed; and I understand the rationale. However, because in OWL property definitions are at the same level as Class definitions, you can extend also properties in other ontologies, just as you extend classes. This is just a feature of OWL, of course it should not be used, and I do not intend to use it; but I was just wondering how it would mat to uAAL |
->
The Ontology class has methods for createNewOntClassInfo(..) AND extendExistingOntClassInfo(..). The second method allows to add more semantic info to an existing class. Formally, the only difference between the 2 methods is that the createNewOntClassInfo-methods add the triple The same applies to properties; there should also be methods to extendExistingXXProperty; those are currently missing. |
when adding an objectProteprty or a dataProperty, adding PropertyExpressions is difficult.
The ObjectPropertySetup can not later be retrieved.
all Property Axioms (such as
setAssymetric()
, orsetFunctional()
) return void, thus one cannot easily express more than one (eg:oci.addObjectProperty(PROP).setAssymetric().setFunctional()
).The text was updated successfully, but these errors were encountered: