I am considering if we could not simply incorporate much of the need of a terminology listing into the rest of document text. For instance, FOURCC could be incorporated in "All messages begin with a four-letter word." as simply "All messages begin with a four-letter word (FOURCC)."|FOURCC |Four character code. This is the message type followed by the command, e.g. "ISTA", "BMSG" etc.
|Server |The hub is the 'server' in a client - hub context. The client receiving the incoming connection is the 'server' in a client - client context.
|Base32 |An encoding used by the protocol, see RFC 4648 for more information about Base32. Note that the Base32 implementation in ADC is never padded.
|Context |When a command states a context, e.g. "T" (To hub), it defines an expectance on the flow of traffic. A context may refer to one or multiple message types. For example, for the context 'T', the message types "B", "C", "D", "E", "F" and "H" are valid. Note that the context is not a restriction in any way, implementations may further extend a command's expected contexts.
What other terms have people found difficult?