-
Key: SYSML2-155
-
Status: closed
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
In 7.25.2 View Definitions and Usages, the third paragraph includes the parenthetical comment:
(Note that, in the textual notation, it is only possible to specify a view rendering using reference subsetting.)
This correctly reflects the following textual notation BNF in 8.2.2.25.1 View Definitions:
ViewRenderingMember : ViewRenderingMembership = MemberPrefix 'render' ownedRelatedElement += ViewRenderingUsage ViewRenderingUsage : RenderingUsage = ownedRelationship += OwnedReferenceSubsetting FeatureSpecializationPart? UsageBody
However, neither the abstract syntax (see 8.3.25) nor the semantics (see 8.4.21) of view rendering require this restriction. The textual notation should be updated to allow a more general declaration of a view rendering usage, consistent with what is representable in the abstract syntax.
-
Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:51 GMT
-
Disposition: Resolved — SysML 2.0b2
-
Disposition Summary:
Extend the textual notation for ViewRenderingUsage
The notation for a view rendering usage is extended to allow the rendering to be defined locally within the containing view, rather than just allowing rendering by reference. The new notation is exactly consistent with almost all the other current textual notations that also allow a special syntax for reference usage (e.g., exhibit state usages, perform action usages, assumed and required constraints of a requirement definition or usage, etc.).
render rendering name : Def [m] ... ;
The previous notation render r; then effectively becomes a shorthand for render rendering references r;.
-
Updated: Tue, 1 Jul 2025 14:47 GMT
SYSML2 — Limitation on specifying view renderings
- Key: SYSML2-155
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF