View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005797 | CaseTalk Modeler | Generation (SQL, XML, etc) | public | 2026-07-25 21:45 | 2026-07-28 12:25 |
| Reporter | Marco Wobben | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Target Version | 15.0 | Fixed in Version | 15.0 | ||
| Summary | 0005797: Object types on a higher meta level are classified as kind | ||||
| Description | Object types placed on a higher meta level are generated with the same stereotype as ordinary object types, because the meta level is not taken into account when classifying them. A type whose instances are themselves types is a high order type and should be generated as such, which is currently not among the available class stereotypes. Expected: object types on meta level 2 or 3 are recognised as high order types in the generated OntoUML output. | ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | Corporate | ||||
| related to | 0005795 | resolved | Concept types are left unclassified when generating OntoUML stereotypes |
|
Object types and concepts on meta level 2 or 3 are now generated as high order types, with their own stereotype and colour, instead of appearing as ordinary object types. The link down to the type they classify is generated as an instantiation - see the related ticket. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-07-25 21:45 | Marco Wobben | New Issue | |
| 2026-07-25 21:57 | Marco Wobben | Relationship added | related to 0005795 |
| 2026-07-28 10:47 | Marco Wobben | Target Version | 15.x => 15.0 |
| 2026-07-28 10:47 | Marco Wobben | Note Added: 0008676 | |
| 2026-07-28 10:47 | Marco Wobben | Status | new => resolved |
| 2026-07-28 10:47 | Marco Wobben | Resolution | open => fixed |
| 2026-07-28 12:25 | Marco Wobben | Fixed in Version | => 15.0 |