-
Key: SYSML21-19
-
Status: open
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
The constraints validateAttributeDefinitionFeatures and validateAttributeUsageFeatures require that all the features of an attribute definition or usage be referential (non-composite). However, there are a number of models in Domain Libraries that declare attribute definitions or usages with composite features.
- Analysis Domain Library
- SampledFunctions
- Constraint in SampledFunction
- StateSpaceRepresentation
- Constraint in StateDeriviative
- SampledFunctions
- Geometry Domain Library
- SpatialItems
- Item SpatialItem::componentNum::elements
- SpatialItems
- Metadata Domain Library
- RiskMetadata
- Constraint in Level
- RiskMetadata
- Quantities and Units Domain Library
- MeasurementReferences
- Constraint CoordinateTransformation::validSourceTargetDimensions
- Constraints in CoordinateFramePlacement
- Constraint AffineTransformationMatrix::validateSourceDimensions
- Constraint MeasurementUnit::hasValidUnitPowerFactors
- Quantities
- Constraints TensorQuantityValue::orderSum and TensorQuantityValu::boundMatch
- Time
- Calculation Iso8601DateTime::getElapsedTime
- Calculation Iso8601DateTimeStructure::getElapsedUticTime
- MeasurementReferences
- Analysis Domain Library
-
Reported: SysML 2.0b2 — Sun, 4 May 2025 18:54 GMT
-
Updated: Sat, 20 Sep 2025 06:51 GMT
SYSML21 — Some library model attribute definitions and usages have composite features
- Key: SYSML21-19
- OMG Task Force: Systems Modeling Language (SysML) 2.1 RTF