SYSML2_ — Inconsistencies in the graphical notation for "expose"

1. In 7.25.1 Views and Viewpoints Overview, Table 23. Views and Viewpoints – Representative Notation, the example for "Expose" renders the expose relationship using a dashed arrow. However, in 8.2.3.25 Views and Viewpoints Graphical Notation, the graphical BNF production expose-relationship shows the arrow as being solid.
2. An expose relationship is a kind of import and, as such, can expose a single membership or the content of a namespace, and can optionally be recursive. The textual BNF production Expose in 8.2.2.25.2 View Usages allows all these options, as does the graphical BNF production expose-compartment-element (for showing an expose declaration in a compartment) in 8.2.3.25 Views and Viewpoints Graphical Notation. However, the graphical graphical BNF production expose-relationship does not.
3. The textual BNF production Expose allows a VisibilityIndicator on an expose declaration, as does the graphical BNF production expose-compartment-element. However, the graphical BNF production expose-relationship does not.

Update the graphical BNF

1. The BNF production should show the arrow as dashed.
2. 8.2.3.5 Namespace and Package Graphical Notation has three productions for import, top-level-import and recursive-import. There should be a similar set of productions for expose.
3. The resolution to SYSML2_-207 makes it mandatory to show visibility for import relationships in the textual and graphical notation, consistent with the updates made for KerML in the resolution to KERML_-74. However, it seems unlikely that a modeler every really expects an expose on a view usage to make the exposed elements visible members outside the view usage. As updated for KERML_-74, the default visibility for an expose, as a kind of import, would be private. However, it also seems reasonable that the exposed elements of a view usage be visible to the specializations of that view usage, which would require a visibility of protected. So, this resolution proposes mandating that the visibility of an expose relationship always be protected, in which case there is no need to show it explicitly in the concrete syntax notations.