SysML 2.0b3 FTF Avatar
  1. OMG Issue

SYSML2_ — Ordering of guards and accepts in transitions is inconsistent

  • Key: SYSML2_-246
  • Status: open  
  • Source: Commonwealth Center for Advanced Manufacturing ( Nicholas Thompson)
  • Summary:

    The fourth and sixth rows of "Table 16. States – Representative Notation" each give an example of a transition statement that contains both an if statement and an accept statement, with the accept before the if.

    Unable to find source-code formatter for language: text. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml
    ...
    transition
       first state1
       accept trigger1
       if guard1
    ...
    

    However, page 110 and the subsequent examples seem to contradict this:

    A transition usage can also have an accepter, which is an accept action usage use to trigger the transition. The

    accepter action for a transition usage is placed after the guard expression and notated using the accept keyword,
    with its payload and receiver parameters specified exactly as discussed in 7.16.8 .

    If an accept before an if has a different meaning than an if before accept, the specification document does not make this obvious.
    The Jupyter Kernel in release 2024-05 of the SysML-v2-Release repository treats an if before an accept as a syntax error.

  • Reported: SysML 2.0b2 — Thu, 11 Jul 2024 14:42 GMT
  • Updated: Fri, 12 Jul 2024 19:59 GMT