SYSML17 — SysML's PrimitiveValueTypes library is missing "value" properties everywhere

For SysML 1.3, has anyone tried to specify the value of a SysML::ValueType ?

If you haven't done so, please try to do this carefully – i.e., don't just assume that Real x = "42.0" is enough!

You'll realize then that the SysML 1.3 spec doesn't provide the capability to specify the actual value for any of the SysML::Libraries::PrimitiveValueTypes

SysML::Libraries::PrimitiveValueTypes::Boolean
SysML::Libraries::PrimitiveValueTypes::Integer
SysML::Libraries::PrimitiveValueTypes::Real
SysML::Libraries::PrimitiveValueTypes::String

Since we can't specify the actual real value of a SysML Real, we can't specify the realPart or the imaginaryPart of a SysML Complex number either!

SysML::Libraries::PrimitiveValueTypes::Complex::realPart :
SysML::Libraries::PrimitiveValueTypes::Complex::imaginaryPart

What is missing is an actual "value" attribute whose type then must be from the UML PrimitiveTypes library since it's the only capability in UML/SysML we have to specify an actual "value" via the Literal[X] metaclasses in UML.

SysML::Libraries::PrimitiveValueTypes::Boolean::value : PrimitiveTypes::Boolean – an actual value can be specified as a UML::LiteralBoolean
SysML::Libraries::PrimitiveValueTypes::Integer::value : PrimitiveTypes::Integer – an actual value can be specified as a UML::LiteralInteger
SysML::Libraries::PrimitiveValueTypes::Real::value : PrimitiveTypes::Real – an actual value can be specified as a UML::LiteralReal
SysML::Libraries::PrimitiveValueTypes::String::value : PrimitiveTypes::String – an actual value can be specified as a UML::LiteralString

SysML::Libraries::PrimitiveValueTypes::Complex can remain as-is since it inherits the capability
to specify an actual value for its realPart & imaginaryPart attributes thanks to SysML::Libraries::PrimitiveValueTypes::Real::value : PrimitiveTypes::Real

I also realized that the QUDV library inconsistently uses in a few places SysML::Libraries::PrimitiveValueTypes when in fact it should use UML's PrimitiveTypes.

I believe that this is a new issue for SysML 1.3.

Duplicate of SYSML17-52 and SYSML17-234

Duplicate of SYSML17-52 and SYSML17-234