| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000132 | CaseTalk Modeler | Transformation (GLR) | public | 2012-08-29 14:01 | 2026-06-07 14:34 |
| Reporter | Marco Wobben | Assigned To | Marco Wobben | ||
| Priority | normal | Severity | feature | Reproducibility | sometimes |
| Status | resolved | Resolution | fixed | ||
| Target Version | 15.0 | Fixed in Version | 15.0 | ||
| Summary | 0000132: Recursive structures must be doped | ||||
| Description | 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. | ||||
| Steps To Reproduce | E.g.: Implemented as table: This requires an automated step which introduces the artificial key and extra key which performs the self reference. | ||||
| Additional Information | Or as:
| ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | |||||
 |
All roles which have this recursion as a playedby otft, must be rerouted to the new artificial key. And the self reference must also be altered to refer to the artificial key. Naturally the logical keys must remain to make the references readable. |
|
|
Every parentid must exist in id (or path). |
|
|
The fact type which represents the parent-child relationship should be annotated with the new ring constraint to prevent illegal populations. |
|
|
The ring constraint should also be settable on the recursive OTFT before doping even happens. |
|
|
image.png (117,432 bytes) |
|
|
Model well formedness now warns the user instead of creating an error before Lexicalization needs to be applied. |
|
|
The rule now warns the user of recursive structures instead of rendering an error. This since GLR can dope. |
