-
Key: SYSML2-68
-
Status: closed
-
Source: DEKonsult ( Mr. Hans Peter de Koning)
-
Summary:
According to the Graphical BNF, the notation for a nested reference usage is now a white diamond in the upper-right hand corner of the usage shape (or optionally a black diamond for a non-reference usage, which is the default). In the Graphical BNF productions this is represented by rd = (reference-diamond)? as defined in clause 8.2.3.6. This is a change from the previous dashed-outline shape as also used in SysML v1.
There are arguments pro and con for which notation might be the more usable, including the affinity of the white diamond with a feature membership, but also continuity with SysML v1 and its visibility of the distinction around the whole shape.
The new notation was proposed primarily to avoid the practical difficulties providing dashed-outline versions of every usage shape in the BNF, but the notation should be properly decided on its own merits, not to make things easier for the BNF. An informal comment could be provided in the BNF simply stating that a dashed-outline version is available for each shape according to whether it is a reference usage. An additional alternative is to use dotted-outline, with the advantage that it more closely follows non-right-angled shapes, such as rounded rectangles used for usages.
After discussion the Graphical Specification WG recommends to replace the upper-right-hand corner reference-diamond notation with a dotted-outline for reference usage, and stay with a solid-outline for composite usage.
-
Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:16 GMT
-
Disposition: Resolved — SysML 2.0b2
-
Disposition Summary:
Graphical notation for nested reference usage needs resolution
The revised text reflects the usage of dashed boxes or ref <kind> keywords instead of hollow diamond adornments to denote referential usages. The dashed boxes are used in context of interconnection views, action flow and state flow views. It also removes erroneous inclusion of definition nodes in interconnection views. It is noted that dashed node notations are also used for namespace imports, however since reference nodes and imported nodes are specified in disjoint views, we regard this as a minor issue.
The motivation for this issue and its resolution is that the proposed dashed notation for referential usages is more visually prominent on diagrams and is consistence with the SysML v1 notation for reference properties. The general consensus of the FTF is that it was a mistake to introduce a significantly different notation than SysML v1 for purely technical reasons (as described in the issue description).
-
Updated: Tue, 1 Jul 2025 14:50 GMT
-
Attachments:
- sysml2-354-0.jpg 22 kB (image/jpeg)
- sysml2-354-1.jpg 27 kB (image/jpeg)
- sysml2-354-2.jpg 27 kB (image/jpeg)
- sysml2-354-3.jpg 29 kB (image/jpeg)
- sysml2-354-4.jpg 25 kB (image/jpeg)
- sysml2-354-5.jpg 24 kB (image/jpeg)
- sysml2-354-6.jpg 19 kB (image/jpeg)
- sysml2-354-7.jpg 14 kB (image/jpeg)
- sysml2-354-8.jpg 5 kB (image/jpeg)
- sysml2-354-aref.jpg 21 kB (image/jpeg)
- sysml2-354-b.jpg 7 kB (image/jpeg)
- sysml2-354-r.jpg 7 kB (image/jpeg)
- sysml2-354-t.jpg 7 kB (image/jpeg)
SYSML2 — Graphical notation for nested reference usage needs resolution
- Key: SYSML2-68
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF