Discrepancy in multiplicity between textual notation import and UI creation

[aroberts8833]

The multiplicity [0..*] gets created differently depending on whether you import/create a part usage from textual notation or if you set the multiplicity by adding it to the name compartment in the graphical representation. Using the textual notation it creates the multiplicityRange with a nested OperatorExpression while adding it in the name compartment creates a multiplicityRange with a nested LiteralInteger with value of 0 and a LiteralInfinity.

How is the multiplicity supposed to be implemented? This seems to be an issue with the textual notation import.

[AxelRICHARD]

Hello,

Thank you for raising this problem.

We rely on SysIDE for the import from textual SysMLv2 files.
If SysIDE parses the textual SysMLv2 to produce an OperatorExpression, then we import it as an OperatorExpression.

The question is: is it allowed to do that? In other words, is there many ways to model the same multiplicity range in SysMLv2?
We'll have to find it the specification and fix SysON accordingly if needed.

Regards,