RobertJasiek wrote:There are terms for which
a) I strongly believe my definition to be correct (ko),
b) I have not seen one counter-example since I have written my definition (thickness, if understood to be generalised to include also inside thickness),
c) I try to be a bit better than a random go dictionary entry, but I am aware that more study and quite likely changes to the definition are needed (aji, if understood to be used for the bad possibility variety of the term).
For (a) and (b), counter-examples can be provided, if they exist at all. For (c), a pretty broad discussion is possible easily.
Definitions do never stand on their own, but persue a specific purpose.
In my understanding, definitions are used in general like
"
For the following, J-Thickness shall be understood as ..."
with its most important element highlighted. Please note that this is
NOT "J-Thickness", NEITHER what follows the "as" !!!
The "
following" is a closed system (e.g. a book, or a theory), so
a) follows from your internal attitude that the results of your work have to meet your very high-level requirements. This means that one can be sure that your definitions are well thought-out, and reliable. This also means that "correct" has to be understood as "consistent" inside the "
following".
So,
a) is NOT the problem !!!
b) follows immediately out of
a). It is very unlikely -- and will happen only by accident -- that you will overlook a tiny detail within your work. This also is a result of your very high-level requirements, concerning the results of your work.
So,
b) in NOT the problem !!!
The main problem is
c) !!!
Your statement includes that you compare the result of your work with something OUTSIDE the "
following". But what is the basis to do this ???
Have the "usual" readers of a "usual" Go dictionary complained en masse that the Go dictionary does not fulfil their needs at all ?
If so, how should another explanation help that is valid only INSIDE the "
following" ?
In addition, there might be no need to have an extended, more "precise" definition of a very special subject.
Let me try to explain this using "thickness" as example, which seems to have lost parts of its meaning during its journey from Japanese to English. Please be aware that the majority of the English-speaking Go community has absolute no idea that the ship has lost some containers around Cape of Good Hope. So they do not miss anything.
An "unsettled" group that is surrounded by "already settled" ones, may be called "weak" or -- better fitting here -- "thin". It will be part of "common knowledge" that such a "thin" group is very likely to become much of a burden during the rest of the game, as well as an attractive aim for the opponent.
Let us assume that the opponent has just played the move, which settled the last of his surrounding groups.
Does it contribute much to the understanding of the position to call this -- somewhat special application of a -- move a "thick" one ?
If so, why should it contribute much to the general understanding of the game to try to develop a "generalization" of what we have just seen ? Just because it is a matter of course that -- if you wanted to have "settled" groups -- you would have to "settle" your groups.