Skip to content

2026-03 - SysML v2 Pilot Implementation

Latest

Choose a tag to compare

@seidewitz seidewitz released this 08 Apr 15:34
· 1 commit to master since this release

This is an incremental update to the 2026-02 release. It corresponds to Eclipse plugin version 0.58.0.

Language Features

None.

Model Libraries

None.

Backward Incompatibilities

  1. Filter expressions. Many examples of feature references in filter expressions currently use a qualified name notation, such as
    filter @Annotations::ApprovalAnnotation and
        Annotations::ApprovalAnnotation::approved and
        Annotations::ApprovalAnnotation::level > 1;
    
    However, the checkConnectorTypeFeaturing constraint is impossible to satisfy for the binding connectors implied by these feature references. The Pilot Implementation was not reporting this as an error, which was not conformant with the normative metamodel for KerML (and, so, SysML, too). Now that this nonconformity has been corrected, the above feature references will cause "Must be accessible feature" errors. To avoid such errors, the qualified names need to be changed to feature chains such as in the following:
    filter @Annotations::ApprovalAnnotation and
        (as Annotations::ApprovalAnnotation).approved and
        (as Annotations::ApprovalAnnotation).level > 1;
    
    [PR #743]

Issue Resolutions

This release proactively implements the resolution to the following issue, which the KerML 1.1 RTF has elevated to be a "blocker" issue.

[PR #749]

Jupyter

None.

Visualization (PlantUML)

None.

Technical Updates

None.

Bug Fixes

  1. Filter expressions. Removed code that suppressed violations of checkConnectorTypeFeaturing within feature references in filter expressions.
    [PR #743]
  2. Semantic metadata. Fixed a bug that could cause an incorrect name resolution when using semantic metadata.
    [PR #744]
  3. Adapters. Fixed bugs in TypeAdapter and AssignmentUsageAdapter.
    [PR #747]
  4. Derived property. Corrected the derivation computation for the property Feature::crossFeature so it takes implied CrossSubsetting into account.
    [PR #748]