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
Currently, I can create a profile P1 of a Class C1.
However, I cannot say that the class profile P1 is also profile of another class C2, which should be possible.
It could be done by adding a "profile of" relationship to relationship and generalization in the Create connection dialog:
Additionally, in this scenario, dsv:inheritedProperties makes no sense (it is unclear from which class the values should be inherited), and therefore should not be used - the values should explicitly be copied, leaving it up to the user to change them accordingly.
The text was updated successfully, but these errors were encountered:
Apparently, "usageOf" supports only one value at the moment @sstenchlak . Changing it can therefore break things - this should be thought through. The fact remains, that we need this to be able to say that we have a data instance of multiple classes at once, without actually defining and intersection class.
Currently, I can create a profile P1 of a Class C1.
However, I cannot say that the class profile P1 is also profile of another class C2, which should be possible.
It could be done by adding a "profile of" relationship to relationship and generalization in the Create connection dialog:
Additionally, in this scenario,
dsv:inheritedProperties
makes no sense (it is unclear from which class the values should be inherited), and therefore should not be used - the values should explicitly be copied, leaving it up to the user to change them accordingly.The text was updated successfully, but these errors were encountered: