Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:s:subscriber_role [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:s:subscriber_role [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Subscriber Role ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Subscriber Role identifies a Logical Node's responsibility for receiving information through a Logical Communication Endpoint. | ||
| + | |||
| + | The Subscriber Role supports information consumption without requiring the producing Logical Node to know the consuming Logical Node's internal implementation. The Logical Architecture identifies the endpoint, the expected information structure, and the Runtime Plane; later implementation profiles choose the communication mechanism. | ||
| + | |||
| + | A Logical Node performing a Subscriber Role receives Logical Data Structure Instances governed by a Logical Data Structure Definition and applies the responsibilities assigned to that Logical Node Role. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Specialization of Communication Endpoint and Node Role from Part 1, Sections 7.6 and 7.4; generalised from publish/ | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Subscriber Role does not require DDS, topic-based middleware, event streaming, or asynchronous communication. Implementation profiles realize subscription according to the selected communication approach. | ||
| + | |||
| + | |||
| + | [[dido: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||