Tickets.CaseTalk - Issues

0005617: Popup menu on diagrams does not paint

Thu, 14 May 2026 19:46:25 +0200

The menu pops up with a right-click, but the items do not show until hovered by the mouse.

0005615: Crash on mouse hover in diagram (highlight relations)

Wed, 13 May 2026 09:34:51 +0200

The application crashes with an access violation while moving the mouse over an element in a diagram. The crash happens during the highlight of related roles/lex path that runs in response to the mouse-move, so a quick hover over a fact, nom-fact, or concept while the diagram is still settling can take the application down.

0005613: Investigate why diagram file export fails while internal save renders bitmaps

Wed, 13 May 2026 09:34:31 +0200

There is an inconsistency between two diagram-rendering paths:

- Saving a project renders diagram bitmaps successfully (used for thumbnails / embedded preview).
- Exporting a diagram to a file fails.

Both paths ultimately render the same diagram, so a working save proves the rendering pipeline is reachable. The export path must be diverging somewhere (different canvas, different target surface, missing parent, different DPI/scaling, output stream handling, ...).

Action:
- Compare the two code paths side by side and identify where they diverge.
- Establish whether the export failure is silent or raises; capture the failure mode.
- Fix the export path so it produces the same bitmap as the save path (or document why it intentionally differs).

0005612: Modernise OWL/RDF export against RDF 1.2 for FCOIM-aligned output

Tue, 12 May 2026 09:49:53 +0200

Research whether the current OWL/RDF export can be improved by adopting RDF 1.2 features for a more natural, FCOIM-aligned serialisation.

Reference: RDF 1.2 Primer - [url=https://www.w3.org/TR/rdf12-primer/" rel="noopener,nofollow]https://www.w3.org/TR/rdf12-primer/[/url]

Scope:
- Audit what the current export emits and where it falls short of expressing FCOIM concepts cleanly.
- Identify RDF 1.2 features (e.g. triple terms / first-class statements, base direction on literals, named-graph semantics) that map well onto FCOIM constructs.
- Propose targeted improvements to the export so the output reads more naturally to downstream OWL/RDF consumers.

Outcome: a short design note plus a focused set of follow-up tickets for the actual export changes.

0005614: Consolidate Turtle export templates and adopt RDF 1.2 idioms

Tue, 12 May 2026 09:40:23 +0200

The codebase ships two overlapping Turtle export templates under develop/modules/templates/:

- ttl.ini ("Turtle (TTL)", 442 lines): rich metadata, PROV-O, VoID, Schema.org alignment heuristics, annotation-property declarations. Bare ":hasArtificialKey"-style predicate naming. Has a few template-syntax bugs (unbalanced parens in the Schema.org alignment block; "@(schema.Tables).Count" emitted mid-Turtle as a literal).

- ig_turtle_export.ini ("Turtle Export", 352 lines): more modest ontology section but adds SHACL shapes, per-table instance file, and SPARQL query examples. Uses a dedicated tmg: namespace ([url=http://casetalk.com/tmg/schema#" rel="noopener]http://casetalk.com/tmg/schema#[/url]) for CaseTalk-specific predicates - much cleaner design.

Goal:
1. Merge into a single canonical Turtle/RDF export template:
- Keep ig_turtle_export.ini's tmg: namespace design for CaseTalk predicates.
- Fold in ttl.ini's PROV-O / VoID / annotation-property declaration blocks.
- Keep the SHACL + SPARQL + per-table-instance outputs from ig_turtle_export.ini.
- Fix the template-syntax bugs noted above.
- Retire the now-duplicate template.
2. Adopt RDF 1.2 idioms in the consolidated template (Turtle is the natural vehicle - triple terms have no idiomatic RDF/XML):
- Replace the synthetic :factExpressions / :businessRules string annotations with RDF 1.2 triple terms (<<:Customer :hasReading "Customer places Order">> :assertedBy :CaseTalk).
- Stop hard-coding "@en"; emit the actual locale from database.Locale or table.Locale.
- Emit rdf:dirLangString and base direction for RTL locales.

Out of scope: the OwlUnit RDF/XML conceptual-model exporter stays as-is for OTFT-level export. This ticket is about the schema-level Turtle path only.

Parent context: see 0005612 for the broader RDF 1.2 / OwlUnit audit.

0005609: Support modeling unknowns: 'gap' concept or container shape

Mon, 11 May 2026 16:31:42 +0200

When modeling, there is currently no concept that represents what we do not yet know. A modeler often needs to sketch a silhouette of a missing piece and show how it connects to known facts.

Proposed enhancement:
- Add support for an Object/Fact Type carrying a 'gap' element concept (e.g. otft[concept] with elm concept 'gap'), so the modeler can mark an OTFT as representing an unknown.
- Alternatively, introduce a dedicated container shape with curved/sketchy outlines that surrounds connected OTFTs and visually signals the gap.

This would allow modelers to communicate uncertainty and incomplete knowledge directly inside the diagram instead of working around it.

0005608: Review PlantUML changes for potential integration updates

Mon, 11 May 2026 15:59:29 +0200

PlantUML has released changes that should be reviewed to see if any apply to CaseTalk's PlantUML diagram generation.

Reference: [url=https://plantuml.com/changes" rel="noopener,nofollow]https://plantuml.com/changes[/url]

Action: review the changelog and evaluate whether any new syntax, features, or fixes warrant updates to CaseTalk's PlantUML export.

0005483: Verify TypeDB INI template supports TypeQL at IG and/or IGG level

Sat, 09 May 2026 12:44:30 +0200

Check whether the INI template for TypeDB (Class1/TypeDB) correctly supports TypeQL output at the IG level and/or IGG level.

Reference: [url=https://typedb.com/docs/core-concepts/typeql/entities-relations-attributes/" rel="noopener,nofollow]https://typedb.com/docs/core-concepts/typeql/entities-relations-attributes/[/url]

The template should generate valid TypeQL define/insert statements for entity types, relation types, and attribute types.

Requested by: Marco Wobben (2026-03-25)

0005607: LLM chatting needs reminding of CaseTalk MCP

Sat, 09 May 2026 12:14:22 +0200

The LLM chatting sometimes answers from training data, and skips the model in casetalk itself, until told to use it. This initial prompt could be better initialized so the user does not have to instruct the LLM about it.

0005606: Fact bleeding in population editor

Sat, 09 May 2026 11:38:13 +0200

The population editor renders related fact expressions to the tuple, but seems to bleed in some unrelated facts there.

0005605: Data Catalog Mapping swaps schema and catalog

Sat, 09 May 2026 10:11:44 +0200

Sometimes the schema and catalog information gets swapped. Making a mapping shows correct, but then a refresh/redraw happens and it shows the other way around.

0005595: Add canvas templates from modelstorming.com

Sat, 09 May 2026 10:09:57 +0200

Add canvas templates from modelstorming.com/templates to the canvas collection in the web canvas gallery.

0005603: Research Microsoft Context IQ and APM

Sat, 09 May 2026 10:09:23 +0200

Investigate Microsoft Context IQ and Microsoft APM (Application Portfolio Management) for potential relevance to CaseTalk product direction.

0005601: Data flow / business process visualization on fact models

Tue, 05 May 2026 10:44:50 +0200

Support visualizing data flows or business processes on top of the fact model. The concept is walking across the fact model and visualizing the routes taken, showing how data or process steps traverse the conceptual model elements.

0005596: Upgrade memory manager

Fri, 01 May 2026 15:58:41 +0200

FastMM5 version 5.07 is out with critical fixes.

0004024: For your eyes only - classifications

Thu, 30 Apr 2026 20:46:33 +0200

According to a post on LinkedIn this makes sense for modeling (artifacts).

[url=https://www.linkedin.com/feed/update/urn:li:activity:7084824295603884032" rel="noopener,nofollow]https://www.linkedin.com/feed/update/urn:li:activity:7084824295603884032[/url]

0005545: Support for OntoUML stereotypes in UML diagrams

Thu, 30 Apr 2026 20:06:55 +0200

As a modeler, I would like CaseTalk to show OntoUML stereotypes on the UML class diagram, so I can see the ontological classification of my model elements.\n\nOntoUML is a well-established ontology-driven conceptual modeling language that classifies entities (kind, subkind, role, phase, relator, mode, quality, category, mixin, etc.) and relationships (material, mediation, characterization, derivation, etc.).\n\nRequested behavior:\n- Entities in the UML diagram display their inferred OntoUML class stereotype (e.g. <>, <>, <>)\n- Associations display their inferred relationship stereotype (e.g. <>, <>)\n- Color coding per stereotype category for visual distinction\n- A style toggle so existing diagrams are not affected

0005583: Organogram Canvas: Custom Attribute Types for Department, Role, Person

Thu, 30 Apr 2026 19:44:56 +0200

Allow model elements (OFTypes, expressions, etc.) to be tagged with organizational ownership using custom attribute picklist types sourced from organogram canvas files. Three new attribute types are needed: Department, Role, and Person. When an organogram canvas is present in the project, these attributes should offer a dropdown populated with the relevant positions from the organogram. This connects the conceptual model to the organizational context — e.g. 'this fact type is owned by the Sales department' or 'this concept is maintained by Brigitte Krause'.

0000132: Recursive structures must be doped

Thu, 30 Apr 2026 16:27:21 +0200

Doping a recursive structure in FCO-IM is required to generate a database table for it. This is to be done manually, however could be automated using an artificial key.

0005591: Naming Conventions editable in Tools > Preferences

Thu, 30 Apr 2026 14:28:53 +0200

Naming conventions (case, whitespace, punctuation for object/fact names, labels, and expressions) can currently only be configured when running the Naming Conventions Wizard or from the GLR Options dialog — both of which immediately apply changes to the model. There is no way to set naming convention preferences independently without triggering a model-wide rename.

Add a 'Naming Conventions' section to Tools > Preferences so users can configure their preferred conventions at any time. The settings persist across sessions and are used as defaults when creating new elements or running the wizard.

0005592: SKOS export conforms to NL-SBB standard

Thu, 30 Apr 2026 14:02:13 +0200

The SKOS Turtle export now includes all predicates required by the Dutch NL-SBB standard (Standaard voor het Beschrijven van Begrippen). No profile-specific logic was needed — all additions (Dublin Core metadata, ISO 25964 typed hierarchies, namespace-based foaf:page, top concept derivation) are universal linked data best practices.

0005590: Range check error when saving model after deriving datatypes

Thu, 30 Apr 2026 08:26:26 +0200

Saving a model file after running Derive Datatypes causes a range check error, preventing the file from being saved. The error occurs when a label type has its datatype length reset during derivation. A dialog reports the file did not get saved, but no further details are shown.

0005588: Create fact type on selected elements

Wed, 29 Apr 2026 17:57:58 +0200

Create fact type on selected elements, cannot work if one of the selected elements is a fact type itself. This should be possible by simply generating an object type expression for it first.

0002870: Support custom names for temporal aspects

Wed, 29 Apr 2026 17:55:45 +0200

Temporal annotations (and transitional, localization, artificial key) are in need of semantics. The OTFT should allow for overriding globaly defined names.

0004574: Change file extensions

Wed, 29 Apr 2026 17:39:11 +0200

The casetalk project files are *.prj, but many products have this extension. Perhaps a '.casetalk' would be more appropriate.

Als being able to associate *.ig with opening in CaseTalk (and a specific version of CaseTalk) would be nice.