We have Subject ID, which defines the kind of information exchanged using messages, and we have Service ID, which defines the kind of information exchanged using RPC. We need a new term that can refer either or both to Subjects and Services. Initially, I thought that Endpoint would be the way to go, but then I realized that it doesn’t work well if one were to view the network as a computational graph, where subjects are edges and nodes are, well, nodes, because the name implies that there is a point-to-point connection whereas the truth is that we can have a MIMO connection.
How do you describe the point where an edge is connected to a node? Anchor?
I like “Subject Port” and “Service Port”, it even sounds better than “Subject ID” and “Service ID”. If we choose port we could refrain from using ID in the specification. When we speak of a concrete number we could call it “Subject Port number” or “Port Number”.