-
Key: KERML11-210
-
Status: open
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
7.2.5.1 (Namespaces Overview) says
Normally, name resolution begins by searching in the local namespace containing the qualified name reference. If local name resolution is not successful, the search proceeds outwards to successive containing namespaces ...
Applied to this example:
class A { feature x; feature y; feature z { feature u unions x, y; }}references to x and y under z are resolved as A::x and A::y, respectively. The interpretation of u is exactly the union of interpretations of x and y, per semantic constraint 3 in Clause 8.4.3.2 (Types Semantics). This means for x or y to have interpretations (values), which is probably intended at least sometimes, then all the interpretations of x and y must be triples (to "navigate" through a value of z). This omits the minimal interpretations (pairs of them in this case) needed to make the triples valid, per semantic constraint 3 in Clause 8.4.3.4 (Features Semantics). For example, for the triple (a1, z1, x1) to be an interpretation of x, the pair (a1, x1) must be also, but this cannot be a interpretation of u, because it's missing the middle "step in navigation" through z.
Modelers can address the problem with that :
class A { feature x; feature y; feature z { feature thatA : A = that; feature u unions thatA.x, thatA.y; }}because the interpretations of u can be triples without preventing pairs as interpretations of x and y. The specification does not explain this or provide a math/modeled semantics to make it unnecesary.
-
Reported: KerML 1.0b2 — Wed, 16 Sep 2026 18:07 GMT
-
Updated: Wed, 4 Nov 2026 14:44 GMT
KERML11 — Lexical scoping, semantics
- Key: KERML11-210
- OMG Task Force: Kernel Modeling Language (KerML) 1.1 RTF