🚀 go-pugleaf

>> Especially when speaking verbally, when "sink" and  "synch" 
>> (as  in  synchronization)  can  become confused.

Hmm.  Good point.

>> The problem with using "source" and "sink" is that they are used
>> in many other ways, and can quickly confuse the issue.

Actually, it is the use of "source coding" in telecommunications that
inspired my terms, and it is consistent with that usage (as I understand
it).  However, "redundancy coding" and "relevancy coding", while longer,
are probably ok.   I'm not sure though that "redundancy" captures all
that encompasses lossless coding.  Though it could be argued that entropy
coding is redundancy coding, I tend to separate redundancy coding from
entropy coding.  In my mind, you first find and identify the redundancy
using some model, and then you generically code the output of that using
entropy coding of some sort.

Anyway, yes, it is all just semantics.  However, it can be important to
clarify the concepts for newcomers to the field.  Especially if they are
looking as something like JPEG where the source and sink ..., excuse me,
redundancy and relevancy coding are inextricably intertwined, but
fundamentally different.

mark