ISSUE: SysMLv2.0 spec Annex example and multiple SysMLv2 PILOT GitHub samples: Inconsistent use of subsetted ISQ «attribute» (has multiplicity [*] in Cameo) without explicit multiplicity. According to SysML2.0 spec. rules would inherit multiplicity [*].

This analysis assumes that an ISQ quantity «attribute» has multiplicity [*] as it does in the Cameo SysMLv2 Plugin model libraries.

There are numerous examples in the SysMLv2 Annex example and the SysMLv2 PILOT GitHub samples of an «attribute» subsetting an ISQ quantity «attribute» but NOT providing an explicit multiplicity. The following are from the main Vehicle Example but there are many other similar ones:

part def Vehicle {
    attribute mass :> ISQ::mass;
    attribute dryMass:>ISQ::mass;
    attribute cargoMass:>ISQ::mass;
    attribute position:>ISQ::length;
    attribute velocity:>ISQ::speed;
    attribute acceleration:>ISQ::acceleration;
    attribute electricalPower:>ISQ::power;

That these are intended to have multiplicity [1..1] is suggested from how they are used elsewhere:

constraint {electricalPower<=500[W]}

Note there are other cases that DO provide an explicit multiplicity:

attribute elapseTime[1] :> ISQ::time;
attribute position[1] :> ISQ::distance;

The cases that don't provide a multiplicity seem to be relying on this rule:

But they do not in fact meet those extra conditions:

Since they DO subset an ISQ quantity «attribute» with an explicitly declared multiplicity [*] (at least in Cameo) they inherit the explicitly declared multiplicity [*].

And they don't meet the other conditions anyway:

Maybe this part is supposed to offer a loophole:

But that does not apply, taken literally, because there is an explicitly declared multiplicity [*] to inherit (even if [*] and [0..*] are the same).

Webel's advice is:

1. Prefer using feature typing by an ISQ «attribute def» (noting the available ISQ «attribute» versions don’t cover all cases anyway).
2. If you do use subsetting of an ISQ «attribute» always state the multiplicity!