-
Key: SYSML2-450
-
Status: closed
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
Clause 8.4.12.4 (Control Nodes), under the Join and Fork headings says:
validateJoinNodeIncomingSuccessions constraint requires that all incoming Successions to a JoinNode have source multiplicity 1..1.
validateForkNodeOutgoingSuccessions requires that all outgoing Successions from a ForkNode have target multiplicity 1..1.
but the validation rules are missing from 8.3.16.11 (JoinNode) and 8.3.16.8 (ForkNode), respectively.
-
Reported: SysML 2.0b1 — Tue, 12 Sep 2023 15:26 GMT
-
Disposition: Deferred — SysML 2.0b2
-
Disposition Summary:
Defer
This issue was submitted after the end of the comment period, and the FTF has decided to defer its consideration to a future FTF or RTF.
-
Updated: Tue, 1 Jul 2025 14:44 GMT
SYSML2 — Fork/JoinNode succession "other" end multiplicity validations missing
- Key: SYSML2-450
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF