-
Notifications
You must be signed in to change notification settings - Fork 48
Frequently Asked Questions
If the relation has a mandatory direction given by its stereotype and the related classes, this direction should be used. In case the direction is still unclear (e.g., no mandatory direction, custom or missing stereotype), the model but be interpreted and a direction must be chosen. Relation's labels and reading directions can be highly informative in this case.
Remember, however, to keep the original's reading direction of the relations at all times, as the reading direction and the relation's are not necessarily the same.
How do I interpret the ontological natures of non-sortals classes (i.e., «category», «phaseMixin», «roleMixin», «historicalRoleMixin», and «mixin») when documenting an ontology?
In 2018, changes were introduced to OntoUML allowing for non-sortal classes to have moments as instances. Therefore, if the model being documented was last updated prior to that, the instances of non-sortal classes should be assumed to be substantials (i.e., functional-complexes, collectives, or quantities), unless stated otherwise. You should also check the references of your source files, as they most likely incorporate these changes to OntoUML if they cite this paper or some other recent one.
Some stereotypes have been spelled in different ways throughout different publications, specially for concepts that were yet being developed. For consistency, document every stereotype like the presented in the original source files with the exception of the ones listed in the table below.
If you believe some other stereotype mapping should be included to this table, fell free to open an issue reporting your suggestion.
| Original Stereotype | Translation into Current Profile |
|---|---|
| «powertype» | «type» |
| «highordertype» | «type» |
| «hou» | «type» |
| «universal» | «type» |
Keep the diagrams as similar to the original ones as possible. The way that people build diagram also carries a lot of information that can be processed as well. Also, avoid applying automatic layouts as much as possible.