Ko Terminology
tderz: Are you also sometimes confused how to describe a given situation precisely where it's clearly ko?
Having difficulties differing between 2-step kos and two-stage-kos? When does it become direct? For whom? Can you express it?
I herewith suggest to create a Notation for Kos, resp. ko terminology in acronyms and/or abbreviations,
which unambiguous, easily understandable and logical.
See also Think Like a Pro Pae for a list of types of ko.
/discussion?
Reasons, Incentives
There are many, many descriptors for possible ko situations around:
Please have a look here: /reasons
If I encounter ko situations in tsumeGo or other problem books, often they are in a foreign language which I do not understand properly (Chinese, Japanese, Korean).
Usually there are much fewer diagrams than there are possible paths, sometimes only one diagram is given.
When I go through problem books, I take my time and want to solve them thoroughly. Eventually, I also want to document my thoughts on the other solution/variation/wrong paths, which I encountered during that process.
- I am of the opinion, that the thought process is enhanced if one better understands the underly abstract modules.
Examples: you speak & write better if you learned the grammar of your own language; a DFK resp. any Go player improves by leaps, once s/he got explained/understood/applies the concept of Sente/gote. The dan player improves his/her play by knowing semeai rules and can, e.g. make the defensive move the last possible, most efficient moment (saving tempo, sentes, thinking time).
- Therefore, if the concepts are clear in our heads, we can think better; for a clear notation it just has to be shorter.
- Therefore I would like to list here all necessary Ko Terms?
However the space next to such diagrams is very limited, even if I write the notation + comments with a 0.5 mm pencil.
- Therefore I need acronyms.
List of Terms which should be covered:
... to be expanded (completed)
direct ko
Yose ko
ko threat
Double Ko, Triple Ko, Quadruple Ko, Multiple Ko
Hanami-ko
Moonshine Life
Half-point ko (minimal ko)
Ko Master
Ko Loser
Ko Monster
Game-deciding Ko
Requirements (concise, consistent, clear, logical)
- Acronyms resp. abbreviations;
- pref. 3 letters maximum + digits if necessary (is mnemonic possible)
examples:
- KT = ko threat
- K = Ko
- S = sente
- G = gote
- Y = Yose
- d = direct (small or capital letters?)
- 2SK = 2-stage Ko
- BBB = tally differences (see Charles Matthews 'setpiece Ko' on gobase)
etc., etc.
I just see (I'm not so frequent anymore on Senseis) that on page TwoStepKoTwoStageKoDiscussion something like what I had in mind started. However, I would like to have it very concise, consistent, clear and logical
- Consistency
The system should be consistent in itself, e.g. just for example, most basically ko should be abbreviated always with 'K'.
Secondly, one should keep only one expression, abbreviation for the same concept )see two-stage-ko).
- Logic
Logic should be ... now, logical and explained:
-
- 先手劫 - a ko in which the player makes the first capture;
- e.g. abbrev. PFC (player first capture)
- 后手劫 - a ko in which the opponent makes the first capture
- e.g. abbrev. OFC
- 黑先手劫 = 白后手劫 (opponent last capture)
- e.g. abbrev. PFC = OLC ,
- 先手劫 - a ko in which the player makes the first capture;
resp. PFC = OFC + sente.
2nd example: Direct Ko (DC) = Yose-ko (YK) with n approach moves + n moves becomes
- DC = 3-YK + 3 sente
I could imagine that some people say 'Just use the expressions with the Chinese characters', that's abbreviated enough (max. number = 4) and very precise. I would love to, but am not capable of it at the moment.
Process
I am aware that many people may find this idea utterly useless.
Be it so.
The more I ask those people for help, who have had similiar needs and ideas.
Above I have given only some examples, which should not be interpreted limiting or finalized. tderz 18.1.2006
Phelan: To get more feedback, you should link this page from a general page about ko, and/or your homepage. Right now this page has no incoming links, it's a WikiOrphan.
tderz: Did you do this already, Phelan?
Still, thank you for the hint.
Phelan: No, I hadn't done it then because I wasn't quite sure where to fit it. I see that you already did, so feel free to delete this discussion.
tderz: I see now, that there was about 3 years ago - in 2003 - already a serious, yet heated discussion about this subject. It was not my intention to start that one again.