Publisher Role
Discussion
A Publisher Role identifies a Logical Node's responsibility for producing information through a Logical Communication Endpoint.
The Publisher Role supports information distribution without requiring direct coupling between the producing Logical Node and consuming Logical Nodes. The Logical Architecture identifies the endpoint and the information structure; later implementation profiles choose the communication mechanism.
A Logical Node performing a Publisher Role identifies the Logical Data Structure Instance it publishes, the Logical Data Structure Definition governing that instance, the Logical Runtime Plane of the exchange, and the traceability expectations associated with publication.
Definition
Communication Role responsible for producing information through a Logical Communication Endpoint.
Source
Specialization of Communication Endpoint and Node Role from Part 1, Sections 7.6 and 7.4; generalised from publish/subscribe and topic publication material in the original FX Demo Reference Architecture.
Note
A Publisher Role does not require DDS, topic-based middleware, event streaming, or one-to-many communication. Implementation profiles realize publication according to the selected communication approach.
Example
A logical Transaction Intake Node serves as a Publisher Role when it produces a transaction event via a logical transaction-event endpoint.