View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005807 | CaseTalk Modeler | Generation (SQL, XML, etc) | public | 2026-07-26 11:07 | 2026-07-29 10:39 |
| Reporter | Marco Wobben | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Target Version | 15.0 | Fixed in Version | 15.0 | ||
| Summary | 0005807: Carry the OntoUML classification into all generated output, not only UML | ||||
| Description | The OntoUML classification of types and relationships is only visible in UML output today. Every other artifact generated from the same model - SQL, XSD, JSON, OWL/RDF, SKOS, ERD, documentation - says nothing about whether a type stands for an independent thing, a relationship, an aspect of something else, or an event. That is the information a receiving system needs in order to understand what a model actually commits to. Two systems can be built on the same model while assuming quite different things about it, and nothing in the exported artifacts reveals the difference. Carrying the classification along makes the assumption explicit wherever the model travels. Expected: each export states the classification in the way that is native to its format. Where the format has a proper mechanism, use it rather than a comment; where it has none, a comment or annotation is enough. Preferably switchable per export, and only once the classification itself is right (see related tickets). | ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | Corporate | ||||
| related to | 0005800 | resolved | Fact types are labelled as material relations without evidence in the model | |
| related to | 0005799 | resolved | Roles of an objectified fact type are labelled material instead of mediation | |
| related to | 0005795 | resolved | Concept types are left unclassified when generating OntoUML stereotypes |
|
The OntoUML classification is now carried into generated output beyond UML, each format stating it in its own native way: gUFO types in OWL/RDF, a note in SKOS, xs:appinfo in XSD, an x-ontouml keyword in JSON Table Schema, COMMENT ON in SQL DDL across twelve dialects, and a classification line in the documentation export. The classification always comes from the conceptual model, resolved back to it from the generated artifact. Anything the transformation introduced itself - a split table, a generated key - carries no classification rather than one inferred from its shape. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-07-26 11:07 | Marco Wobben | New Issue | |
| 2026-07-26 11:08 | Marco Wobben | Relationship added | related to 0005800 |
| 2026-07-26 11:08 | Marco Wobben | Relationship added | related to 0005799 |
| 2026-07-26 11:09 | Marco Wobben | Relationship added | related to 0005795 |
| 2026-07-29 10:39 | Marco Wobben | Fixed in Version | => 15.0 |
| 2026-07-29 10:39 | Marco Wobben | Target Version | 15.x => 15.0 |
| 2026-07-29 10:39 | Marco Wobben | Note Added: 0008704 | |
| 2026-07-29 10:39 | Marco Wobben | Status | new => resolved |
| 2026-07-29 10:39 | Marco Wobben | Resolution | open => fixed |