Component v1 §5.2 (as of PR #31) deliberately records this as undecided: a PUBLIC TCP/UDP endpoint publishes a host:port edge address, but §6.1's two platformDefault sources both derive from a URL and no third source exists, so a document has no way to reference the edge address.
The platform ships the capability today (an allocated edge port surfaced as tcpEdgePort on the endpoint resource), so the question has a live consumer: a component whose sibling needs the broker/database edge address at install time currently cannot express it in the document.
Options to weigh: a third platformDefault source (e.g. PUBLIC_ADDRESS), a self.publicAddress. reference namespace, or an explicit decision to keep it out of the contract (documented as such).
Filed per the platform's spec PR #31 alignment pass; no urgency — the divergence-free state holds either way.
Component v1 §5.2 (as of PR #31) deliberately records this as undecided: a PUBLIC TCP/UDP endpoint publishes a host:port edge address, but §6.1's two platformDefault sources both derive from a URL and no third source exists, so a document has no way to reference the edge address.
The platform ships the capability today (an allocated edge port surfaced as tcpEdgePort on the endpoint resource), so the question has a live consumer: a component whose sibling needs the broker/database edge address at install time currently cannot express it in the document.
Options to weigh: a third platformDefault source (e.g. PUBLIC_ADDRESS), a self.publicAddress. reference namespace, or an explicit decision to keep it out of the contract (documented as such).
Filed per the platform's spec PR #31 alignment pass; no urgency — the divergence-free state holds either way.