Terminology

Ideas for ADC may be presented here for others to review and point out flaws or further improve the idea.
Forum rules
If you have an account on the wiki, remember to update the ADC Proposals page for new ideas.

http://dcbase.org/wiki/ADC_Proposals_list
Pretorian
Site Admin
Posts: 214
Joined: Tue Jul 21, 2009 10:21 am

Terminology

Post by Pretorian » Sun Jul 22, 2012 3:11 pm

A couple of people have pointed out that a terminology listing in the base document could be useful, especially if there's confusing or ambiguous terms. The following is a suggestion of a list, but it's not complete.
|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.
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)."

What other terms have people found difficult?

Who is online

Users browsing this forum: Google (Crawler) and 0 guests