-
Key: KERML11-138
-
Status: open
-
Source: Ansys Government Initiatives ( Mr. Richard Page)
-
Summary:
In KerML 9.2.4.2.13 Occurrence, the documentation for isDispatch says
isDispatch : Boolean
Determines whether the same incoming transfer can be accepted more than once by StatePerformances
composed under dispatchScope. It defaults to true for Performances, and false for other Occurrences
(including Objects).However, this is potentially misleading compared to the definition of isDispatch in 9.2.11.1 State Performances Overview, which says:
isDispatch being true prevents the same Transfer from being accepted more than once by StatePerformances composed under dispatchScope, and prevents from being accepted at all any acceptable Transfers that are not accepted and are higher in incomingTransferSort order than the one that is. It defaults to true for Performances, including StatePerformances, and false for other Occurrences, while dispatchScope defaults to thisPerformance for StatePerformances, the top Performance (indirectly) composing the StatePerformance (see 9.2.6.2.14 ), and self for other Occurrences (see 9.2.2.1 ).
We should correct this to be consistent.
The wording in section 9.2.4.2.13 Occurrences seems to indicate that isDispatch=true would indicate transfers "can be accepted more than once" in contradiction with 9.2.11.1
-
Reported: KerML 1.0b2 — Mon, 10 Nov 2025 18:37 GMT
-
Updated: Tue, 11 Nov 2025 23:27 GMT
KERML11 — Occurrence isDispatch English misleading
- Key: KERML11-138
- OMG Task Force: Kernel Modeling Language (KerML) 1.1 RTF