-
Key: SYSML21-658
-
Status: open
-
Source: Dassault Systemes ( Mr. Andrius Armonas)
-
Summary:
Currently ConjugatedPortDefinition has a redefinition for effectiveName operation; effective name of conjugated port definition is computed a by prepending the '~' character to the effectiveName of parent port definition.
The analogous arrangement should be done (but is currently missing) for the short names as well.
I.e. The effectiveShortName operation should be redefined for conjugated port definitions (chapter 8.3.12.2); something along the lines:effectiveShortName() : String [0..1] {redefines effectiveShortName} If the shortName of the originalPortDefinition is non-empty, then return that with the character ~ prepended. body: let originalShortName : String = originalPortDefinition.shortName in if originalShortName = null then null else '~' + originalShortName endif
Correspondingly, the diagram in Figure 17 shall be updated - showing effectiveShortName() redefined;
and the sentence in the 8.3.12.2 chapter header shall be updated, e.g. like this:Every PortDefinition (that is not itself a ConjugatedPortDefinition) has
exactly one corresponding ConjugatedPortDefinition, whose effective name is the name of the
originalPortDefinition, with the character ~ prepended. Ditto for the effective short name. -
Reported: SysML 2.0 — Mon, 20 Jul 2026 13:39 GMT
-
Updated: Mon, 20 Jul 2026 13:48 GMT
SYSML21 — ConjugatedPortDefinition should have the effectiveShortName redefined
- Key: SYSML21-658
- OMG Task Force: Systems Modeling Language (SysML) 2.1 RTF