View Issue Details

IDProjectCategoryView StatusLast Update
0005805CaseTalk ModelerGeneration (SQL, XML, etc)public2026-07-28 12:25
ReporterMarco Wobben Assigned To 
PrioritynormalSeveritytweakReproducibilityhave not tried
Status resolvedResolutionfixed 
Target Version15.0Fixed in Version15.0 
Summary0005805: Kind classification does not check whether the type has its own identification
Description

The documented rule for classifying an object type as an independent type is that it has its own identification, on its own label types. In practice any object type that matches none of the earlier rules is classified as independent, whether or not it is identified through other types.

The check exists and is used elsewhere in the classification, but not at the point where this decision is made, so documentation and behaviour disagree.

Expected: the documented rule is applied, so that an object type is only presented as independent when it carries its own identification.

TagsNo tags attached.
CaseTalk EditionCorporate

Relationships

related to 0005802 resolved Objectified fact types with one participant are classified as kind instead of an aspect 
related to 0005804 resolved Label types are classified as aspects regardless of their data type 

Activities

Marco Wobben

Marco Wobben

2026-07-27 17:01

administrator   ~0008656

An object type is now only presented as independent when it carries its own identification, on its own label types, as the documentation describes.

Where the identification is borrowed from other types, the object type is classified by what identifies it: identified through a single other type it is an aspect of that type, identified through two or more it is a relationship between them. This matches the familiar distinction between a strong entity, a weak entity and an associative entity.

An object type for which no identification has been recorded yet is left as it was, since the model does not yet say what identifies it.

The documentation and the behaviour now agree.

Issue History

Date Modified Username Field Change
2026-07-25 22:27 Marco Wobben New Issue
2026-07-25 22:28 Marco Wobben Relationship added related to 0005802
2026-07-25 22:28 Marco Wobben Relationship added related to 0005804
2026-07-27 17:00 Marco Wobben Target Version 15.x => 15.0
2026-07-27 17:01 Marco Wobben Note Added: 0008656
2026-07-27 17:01 Marco Wobben Status new => resolved
2026-07-27 17:01 Marco Wobben Resolution open => fixed
2026-07-28 12:25 Marco Wobben Fixed in Version => 15.0