Ports notation: selected source-unit audit

This audit inspects all four labeled cells of Table 10 and all 20 declaration occurrences in §8.2.3.12. It identifies displayed alternatives and their restrictions; an audited source unit may still have every rendering alternative deferred. It is not a claim of complete SysML graphical coverage, parser acceptance, model validity or renderer conformance.

The pinned source is OMG SysML 2.0 Language, formal/2026-03-02, SHA-256 46e6c0476a6f1f34f367d57e039d56659bff75e41d2e4b3d37ca4cadea84a83a, verified against data/source-manifest.json. PDF pages 94, 95, 239 and 242–246 were rendered and visually inspected; extracted text was used to locate declarations. The section continues through PDF 246 / printed 214, not merely PDF 245.

What the source actually permits

A port definition has a sharp-corner rectangular full-node form; a port usage has a rounded rectangular full-node form. Both can carry a compartment stack and repeated boundary ports on all four sides. Their respective headers use DefinitionPrefix with the port-definition keyword and definition-name-with-alias, or OccurrenceUsagePrefix with the port keyword and usage-name-with-alias. These dependencies require more than substituting an arbitrary label into a rectangle. Table 10, PDF 94 / printed 62, §8.2.3.12, PDF 242–243 / printed 210–211.

Each left, right, top and bottom boundary production shows four alternatives: a solid small rounded glyph; a reference glyph with a broken outline; an elongated rounded glyph carrying nested ports on its corresponding side; and a proxy alternative. Left/right forms contain a horizontal direction indication (pdh), and top/bottom forms contain a vertical indication (pdv). Those direction productions each show three alternatives: both directions and either individual direction. The current undirected port-glyph component supplies reusable geometry, but does not alone instantiate any complete displayed boundary production. PDF 243–245 / printed 211–213.

The small left/right forms position their labels outside and above, toward the corresponding side. The top form puts its external label above-left; the bottom form puts it below-right. Elongated left/right forms carry vertical labels inside and their repeated nested ports on the corresponding edge. Elongated top/bottom forms carry horizontal labels inside and nested ports on the corresponding top/bottom edge. Position is a layout responsibility; rotating a whole SVG also rotates its text and does not reproduce these alternatives. PDF 244–245 / printed 212–213.

The source explicitly restricts broken-outline reference ports to nested ports. It restricts the proxy option to a part usage within an interconnection view. Vertical proxies show a filled dot across a vertical boundary and a label on either side; horizontal proxies show a dot across a horizontal boundary and a label on either side. These are context restrictions, not assumptions that screen nesting automatically establishes model ownership. PDF 246 / printed 214.

proxy-label is resolved outside the selected ports section: §8.2.3.9 defines it as an optional leading dot followed by FeatureChainMember. It is not undefined merely because no declaration occurs in §8.2.3.12. The selected ports source refers to that name without a separate cross-reference. Existing research descriptions that call this dependency unresolved should be updated. PDF 239 / printed 207.

Compartments and conjugation

The ports compartment comprises a heading, repeated entries and optional trailing ellipsis. Its entry rule composes optional el-prefix, OccurrenceUsagePrefix and usage-cp. Table 10 illustrates inherited-member marking; multiplicity and ordered/nonunique modifiers; word and symbolic redefinition/subsetting forms; value notation; a referential entry; a name-only entry; a conjugated type; and elision. These examples do not establish an exhaustive cross-product of all prefix combinations. Table 10, PDF 94 / printed 62, grammar PDF 243 / printed 211.

The directed-features cell demonstrates in, out and inout for both attribute and item entries, with an optional ellipsis. Its graphical productions are in the preceding parts section, not among the 20 ports declarations. Their contents use repeated elements and optional elision; the element references el-prefix, FeatureDirection and Definition-Body-Item. Table 10, PDF 94 / printed 62, §8.2.3.11, PDF 242 / printed 210.

Conjugation reverses in and out, leaving inout unchanged. A conjugated port-usage type can use the original type name preceded by ~; this denotes the corresponding nested conjugated definition. Table 10 shows that shorthand in a compartment entry. A boundary port-label, however, is printed as a qualified name with an optional colon and qualified type name; this audit does not silently extend that production to accept every compartment syntax. Likewise, a direction glyph alone is insufficient evidence for choosing an arrow from an arbitrary set of exchanged features. §7.12.3, PDF 95 / printed 63, boundary label PDF 246 / printed 214.

Ports are occurrences and can themselves contain nested ports. Other features of a port definition or usage must be referential rather than composite. This semantic restriction matters when explaining a port's nested contents; it does not mean every item exchanged through the port is a composed child of it. §7.12.1, PDF 93 / printed 61, §7.12.2, PDF 95 / printed 63.

Source-unit disposition

The working ledger the published ledger contains 24 units and 61 descriptive alternative records, with geometry, labels, context, source pages, dependencies and either a limited asset match or explicit deferral. These are audit bookkeeping counts, not 61 unique symbols or a total number of required SVGs. The following index makes every selected source unit explicit.

Each row's original source is the pinned OMG PDF; use its PDF page number in #page= links. Units remain distinct even where a table and production describe related alternatives.

Safe asset additions and remaining ambiguity

The immediate safe gap is a minimal port-definition SVG: reuse the established sharp-corner definition template with the port-definition keyword, editable name, original metadata and anchors. It should explicitly exclude compartments, aliases, prefix combinations and boundary/nested ports. A conjugated full-usage example can use the existing editable label slot as a demonstrator; that does not add parsing support for conjugated types.

Direction-arrow primitives could be added without asserting model semantics, but complete boundary-port components also require side-specific labels, containment restrictions, nested layout and direction-selection rules. Reference/proxy drawing should remain deferred until those responsibilities have an explicit interface. A compartment renderer needs its own row/layout contract rather than a flattened text field.

The original §8.2.3.12 extension says interconnection-element =| port-def | port, while the full usage production in this section is named port-usage. This audit records the mismatch and does not substitute one identifier for the other. The extension operator =| is also preserved as printed; it must not be normalized to ordinary = in extraction. PDF 243 / printed 211.

Implementation reconciliation

The descriptions above record the initial source-review findings. The current per-alternative ledger is authoritative for asset/deferral status after implementation: it includes minimal PortDefinition, selected two-row compartment nodes and direction-bearing boundary glyphs. Broader layouts and imported grammar are still deferred as recorded there. See the connected reference and SVG library.