View Issue Details

IDProjectCategoryView StatusLast Update
0005795CaseTalk ModelerGeneration (SQL, XML, etc)public2026-07-28 12:25
ReporterMarco Wobben Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Target Version15.0Fixed in Version15.0 
Summary0005795: Concept types are left unclassified when generating OntoUML stereotypes
Description

When a UML diagram or XMI export is generated with OntoUML stereotypes enabled, object types that were modelled top-down as concepts receive no stereotype at all, while types derived from fact types are classified normally.

This is the wrong way round: the top-down layer is exactly where the modeller is describing things directly, and where a classification such as kind, category or collective is most meaningful. Many of these types already carry a concept type that could drive the choice.

Expected: concepts are classified like other object types, falling back to a sensible default instead of being left blank.

TagsNo tags attached.
CaseTalk EditionCorporate

Relationships

related to 0005796 resolved Meta level classification links are labelled as material relations 
related to 0005797 resolved Object types on a higher meta level are classified as kind 
related to 0005800 resolved Fact types are labelled as material relations without evidence in the model 
related to 0005802 resolved Objectified fact types with one participant are classified as kind instead of an aspect 
related to 0005807 resolved Carry the OntoUML classification into all generated output, not only UML 

Activities

Marco Wobben

Marco Wobben

2026-07-28 10:47

administrator   ~0008678

Concepts are now classified like other object types instead of being left without a stereotype. They are read through the same rules - concept type, subtype, abstract supertype, aggregation - and fall back to kind where nothing more specific applies.

Across the reference models this classified 146 concepts that previously carried no stereotype at all, and left none blank.

Issue History

Date Modified Username Field Change
2026-07-25 21:40 Marco Wobben New Issue
2026-07-25 21:41 Marco Wobben Target Version => 15.x
2026-07-25 21:56 Marco Wobben Relationship added related to 0005796
2026-07-25 21:57 Marco Wobben Relationship added related to 0005797
2026-07-25 22:06 Marco Wobben Relationship added related to 0005800
2026-07-25 22:22 Marco Wobben Relationship added related to 0005802
2026-07-26 11:09 Marco Wobben Relationship added related to 0005807
2026-07-28 10:47 Marco Wobben Target Version 15.x => 15.0
2026-07-28 10:47 Marco Wobben Note Added: 0008678
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