If `Req Id` is empty then it should have same value as `declaredShortName`

[alexfournie]

Environment :

• Windows
• Firefox
• Chrome
• 2026.1.0

Expected behavior:

• From specification :
  • If a requirement definition or usage is declared with a short name (see 7.2 ), then this is also
    considered to be its requirement ID.
  • An optional modeler-specified identifier for this RequirementDefinition (used, e.g., to link it to an original
    requirement text in some source document), which is the declaredShortName for the
    RequirementDefinition.
• So from my understanding the behavior should be :
  • by default Req Id is equal to declaredShortName
  • then if the user changes the value of declaredShortName then Req Id value is updated in regards
  • then if the user changes Req Id with a non empty value then Req Id and declaredShortName values will be keep different
  • then if the user clears the value of Req Id then Req Id recovers the declaredShortName value

Actual behavior:

• Req Id is independent from declaredShortName

[AxelRICHARD]

From my understanding, it is a little bit different.
From 8.3.21.8 RequirementDefinition and 8.3.21.9 RequirementUsage chapters of the SysMLv2 specification, reqId is an optional identifier for the RequirementDefinition/RequirementUsage (used, e.g., to link it to an original
requirement text in some source document), which is the declaredShortName for the RequirementDefinition/RequirementUsage. It also says reqId : String [0..1] {redefines declaredShortName} which means, in the metamodel, that get or set declaredShortName property on a RequirementDefinition/RequirementUsage will get/set the reqId property instead.