Terminology: 'Protocol' vs. 'Binding' vs. 'Solution' vs. 'Interaction Sequence'

[sebbader]

To enable an efficient discussion (and writing), we need to agree on the right words. Please put your points in here, and then agree on what we actually mean when talking about each of the above terms.

Target: Add the right definitions to the IDS-G Glossary

[sebbader-sap]

My view:
(Internet communication) protocol: A communication protocol is a system of rules that allows two or more entities of a communications system to transmit information via any kind of variation of a physical quantity. The protocol defines the rules, syntax, semantics and synchronization of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both. In particular however, I see HTTP, TCP, UDP, MQTT etc. as protocols, in contrast to business workflows.

Transport protocol: TCP/IP and other protocols on the same or close OSI layers.

Binding is used for instance in the broker readme or IDS REST describes the details of an interaction sequence for an application layer protocol (like HTTP). Examples could be OData, the FIWARE NGSI-LD definitions, or the AAS API Operations.

Interaction sequence: Stateful, synchronous or asynchronous sequence of exchanged messages. Examples: OAuth message flow, IDS policy negotiation.

Solution: I know this term more in the direction of an implementation technology, e.g., 'my Java SpringBoot-based server is a solution following the IDS Metadata Broker specification'.