SysMLv1: CAUTION: The notation and recommended use for PropertySpecificType changed significantly between SysMLv1.2 and SysMLv1.7. And the spec itself does not seem to use the new notation (which is also not supported by Cameo Systems Modeler v2024x)

This page identifies a possible issue, inconsistency, concern, error, or bug!
One of the ways Webel IT Australia helps promote tools, technologies, and languages is by donating a lot of time identifying, tracking, and reporting potential issues, in order to help vendors and developers improve the tools and technologies. In some cases, we also offer workarounds and advice for users. All issues tracked on our public site are offered most constructively and with sincerest gratitude to the tool vendors and technology developers.
DISCLAIMER: Vendors do not officially endorse issue analysis by Webel IT Australia.
Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
Policy level
Specification keywords
SysMLv1.x keywords
Keywords
Click on the image to view it full size
Compare these extracts (visit the links for the full quotes):

Note the change from square brackets [...] in early SysMLv1.2 to parentheses (..) by SysMLv1.7.

Neither the SysMLv1.7 Figure 8.23. Property-specific types in facility example nor Figure 8.24. Changes in classification over time due to property-specific types seem to use the recommended notation.

And the recommended SysMLv1.7 notation is also not explicitly supported by Magic Cyber-Systems Engineer ® (Cameo Systems Modeler®) (v2024x).

You may be able to HACK the notation into your tool.

Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)