| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:p:protocol_buffers [2026/07/18 12:33] – external edit 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:p:protocol_buffers [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| | Protocol Buffers over custom sockets | Application-defined topology | | | Protocol Buffers over custom sockets | Application-defined topology | |
| |
| In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, Protocol Buffers belong to implementation and platform-specific mapping concerns. Protocol Buffers do not define logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns. | In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, Protocol Buffers belong to implementation and platform-specific mapping concerns. Protocol Buffers do not define logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns. |
| |
| An implementation profile maps selected logical information structures and selected exchange mechanisms to Protocol Buffers definitions, generated language bindings, runtime libraries, and serialised data when Protocol Buffers serve as the selected data serialisation technology. | An implementation profile maps selected logical information structures and selected exchange mechanisms to Protocol Buffers definitions, generated language bindings, runtime libraries, and serialised data when Protocol Buffers serve as the selected data serialisation technology. |
| ===== Note ===== | ===== Note ===== |
| |
| Protocol Buffers are not a transport, communication middleware, logical information structure, logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], DDS Topic, DDS Domain, message bus, programming language, deployment environment, governance model, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] model. | Protocol Buffers are not a transport, communication middleware, logical information structure, logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], DDS Topic, DDS Domain, message bus, programming language, deployment environment, governance model, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] model. |
| |
| ===== Example ===== | ===== Example ===== |