F.18:5.6 - Relation, Slot, Interface, Port, and Signature Names
If a name touches relation, slot, interface, port, boundary, protocol, API, or signature wording, use A.6.RSIR and subject patterns.
- Use A.6.5 for relation slot discipline and
SlotSpecdeclarations. - Use A.6.0 for signatures and law-defined declarations.
A.6.Mand architecture patterns define or constrain module interfaces and architecture interfaces.A.6.F, transformation, and architecture patterns define or constrain functional ports and functional structures.A.6.C, protocol, service-access, and commitment patterns define or constrain API, protocol, and service-access cases.- Use C.2.1 for the identity and content of a claim-bearing interface-description episteme.
- Use E.17 for a multi-view publication face or form.
- Use E.24.PUB for availability of the selected edition and for the separate form-expression and carrier-bearing relations.
Before naming a relation-facing object, keep these settlements distinct:
| Object to name | Required prior settlement |
|---|---|
| reusable predicate-definition episteme | An A.6.RCD result records a reusable definition and C.2.1 gives it one truthful exact EntityOfConcern; the name denotes the definition, not a relation kind |
| derived or primitive relation kind | A.6.RCD, E.24, and E.24.UK have admitted the kind and its direct subject pattern states obtaining, applicability, and occurrence identity |
| one obtaining relation occurrence | the subject pattern establishes obtaining and A.6.REL applies the admitted kind’s identity rule |
| formula, query, path, graph, diagram, or other representation element | C.29 states what it represents and the relevant correspondence; its name does not name the represented relation by default |
| designator or reference | the exact designation or reference relation resolves to the already settled object under its reference scheme |
One token may be reused only where the reference scheme and local sense preserve these distinctions; it cannot collapse definition, kind, occurrence, representation, and designator into one object.
F.18 can settle a durable name for the recovered value. It does not decide which value the interface word names, create a public row, or make that row available.
Words such as member, membership, belongs to, and in do not by themselves identify one reusable relation. First use E.10 to recover whether the sentence concerns mathematical inclusion, kind classification, relation participation, collection belonging, or constructive parthood. For a collection, an ordinary sentence such as “this edition belongs to this product series” is enough unless another use needs a reusable relation name. Name a reusable predicate only under the pattern that states who or what may belong, what makes belonging begin and end, and how recurrence and past belonging are handled. Do not create a NameCard or public name for generic MemberOf merely to abbreviate the ordinary sentence.