Skip to content

ST6RI-933 SysML 2.1 Ballot #2 - Model Library#758

Open
seidewitz wants to merge 4 commits into
masterfrom
ST6RI-933
Open

ST6RI-933 SysML 2.1 Ballot #2 - Model Library#758
seidewitz wants to merge 4 commits into
masterfrom
ST6RI-933

Conversation

@seidewitz

Copy link
Copy Markdown
Member

This PR updates several Systems and Domain Library models to correct minor errors, mostly in documentation comments, per the resolutions to the following issues approved on SysML 2.1 RTF Ballot 2.

  • SYSML21-26 Actions::DecisionAction descriptions are different
  • SYSML21-27 Actions::MergeAction descriptions are different
  • SYSML21-29 Actions::AcceptMessageAction has different descriptions
  • SYSML21-30 Actions::SendAction descriptions not the same
  • SYSML21-362 calc defs '[' for vector and tensor quantity values missing nonunique
  • SYSML21-370 Typo montonically in Time::Clock
  • SYSML21-526 SysML.sysml doc wrong

The resolution to the following issue also approved on Ballot 2 was already proactively implemented in PR #660 (ST6RI-855).

  • SYSML21-6 Remaining error in TradeStudies model

Models Changed

Systems Library

  • Actions.sysml
  • SysML.sysml

Quantities and Units Domain Library

  • VectorCalculations.sysml
  • TensorCalculations.sysml
  • Time.sysml

@seidewitz seidewitz added this to the 2026-05 milestone May 25, 2026
@seidewitz seidewitz self-assigned this May 25, 2026
@conradbock

conradbock commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

The library "code" changes look fine. About the doc changes to DecisionActon and MergeAction:

It is a DecisionPerformance that selects one outgoing HappensBeforeLink.

It is a MergePerformance that selects exactly one incoming HappensBeforeLink.

These performances constrain rather than select (ie, they ensure there's only one thing to "select from"), by identifying exactly one instance (link) of HappensBefore with the performance as source/target, which (when combined with the proper subsetting) is the only "value of" their usage's outgoing/incoming successions, ie, only one succession identifies a link.

How to say this in documentary style I'm not sure. Could be:

It is a DecisionPerformance, which identifies the one HappensBefore link from the Successions going out of its DecisionNode that has the performance as its source.

It is a MergePerformance, which identifies the one HappensBefore link from the Successions coming into its MergeNode that has the performance as its target.

I guess it's OK to remove the explanation about subsetting outgoing/incomingHBLink, since that's (hopefully) specified by OCL for Decision/MergeAction and explained in the corresponding spec clauses.

@seidewitz

Copy link
Copy Markdown
Member Author

@conradbock
Actually, the changes made in the is PR are as approved by issue resolutions in SYSML 2.1 RTF Ballot 2. The only thing to review is whether the PR changes follow the resolutions. If you think that the resolutions should be different, then you will need to file a new OMG issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants