Closed seidewitz closed 4 months ago
I do not know the detailed plan but exhibit state does not have a proper effective name. (SysML2_85).
Note that EXPAssociative
does not seem to work, and I guess it will be resolved later.
ExhibitStateUsage
and IncludeUseCaseUsage
specialize PerformActionUsage
, they should inherit the behavior of PerformActionUsage::namingFeature
. Unfortunately, the Impl
classes only singly-inherit from StateUsage
and UseCaseUsage
, respectively, not PerformActionUsage
. So namingFeature
needs to be re-implemented for each of them. This has now been done.Thank you. I confirmed exhibit state
has an effective name as well.
Also I confirmed the user defined keyword can be applied to enum value.
This PR implements resolutions of issues from SysML FTF Ballot 11 that called for updates to the SysML abstract and concrete syntax.
Resolutions of the following issues are implemented in this PR:
Note: The resolution to SYSML2-637 updated the SysML grammar so that user-defined keywords can be used on enumeration definitions. However, it did not update the grammar to allow such keywords on the enumerated value declarations within enumeration definitions. Nevertheless, the implementation in this PR does allow this, in the expectation that there will be a future FTF issue resolution to allow it formally. (Enumeration usage declarations other than for enumerated values already allowed user-defined keywords.)