<entry id="2205109" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>1215770</ent_seq>
<k_ele>
<keb>関</keb>
<ke_pri>news1</ke_pri>
<ke_pri>nf02</ke_pri>
</k_ele>
<r_ele>
<reb>せき</reb>
<re_pri>news1</re_pri>
<re_pri>nf02</re_pri>
</r_ele>
<r_ele>
<reb>セキ</reb>
<re_nokanji/>
</r_ele>
<sense>
<stagr>せき</stagr>
<pos>&n;</pos>
<pos>&n-suf;</pos>
<gloss>barrier</gloss>
<gloss>gate</gloss>
</sense>
<sense>
<pos>&n;</pos>
<field>&go;</field>
<s_inf>usu. セキ</s_inf>
<gloss>seki</gloss>
<gloss>mutual life</gloss>
</sense>
<info>
<audit time="2016-03-14 15:32:16" stat="A" unap="true">
<upd_name>Scott</upd_name>
<upd_detl>Eij has stalemate but doesn't seem accurate</upd_detl>
<upd_refs>https://en.wikipedia.org/wiki/List_of_Go_terms
http://senseis.xmp.net/?Seki</upd_refs>
<upd_diff>@@ -19,0 +20,5 @@
+&lt;sense&gt;
+&lt;pos&gt;&amp;n;&lt;/pos&gt;
+&lt;gloss&gt;mutual life (Go)&lt;/gloss&gt;
+&lt;gloss&gt;seki&lt;/gloss&gt;
+&lt;/sense&gt;</upd_diff>
</audit>
<audit time="2016-03-14 19:19:54" stat="A" unap="true">
<upd_name>Johan Råde</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>In Japanese go books this is usually written セキ.
Most technical go terms are in fact written with katakana.</upd_detl>
</audit>
<audit time="2016-03-14 21:36:12" stat="A" unap="true">
<upd_name>Scott</upd_name>
<upd_detl>Not sure if possible to specify [関 and せき only] for [1].</upd_detl>
<upd_diff>@@ -12,0 +13,4 @@
+&lt;/r_ele&gt;
+&lt;r_ele&gt;
+&lt;reb&gt;セキ&lt;/reb&gt;
+&lt;re_nokanji/&gt;</upd_diff>
</audit>
<audit time="2016-03-15 06:02:33" stat="A" unap="true">
<upd_name>Johan Råde</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>It would be it bit messy.
There are lots of go terms that will create such problems.
For instance:
閉まり シマリ corner enclosure
置き オキ placement move
滑り スベリ sliding move
etc etc
Maybe they should be kept as separate entries (if we are to include them at all).</upd_detl>
</audit>
<audit time="2016-03-15 13:26:12" stat="A" unap="true">
<upd_name>Scott</upd_name>
<upd_detl>I think that we should include them. We have plenty of specialized vocabulary from other fields. It might make more sense to have them as a separate entry. They share one and a half elements: the kanji and half the reading. Technically, that would be two out of three if you round up... 

Anyway, it seems like a fairly good idea to me to separate them out.</upd_detl>
</audit>
<audit time="2016-03-19 06:45:45" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I think this pattern will work.</upd_detl>
<upd_diff>@@ -18,0 +19 @@
+&lt;stagr&gt;せき&lt;/stagr&gt;
@@ -26 +27,2 @@
-&lt;gloss&gt;mutual life (Go)&lt;/gloss&gt;
+&lt;s_inf&gt;usu. セキ&lt;/s_inf&gt;
+&lt;gloss&gt;mutual life (in go)&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2016-03-19 09:08:22" stat="A">
<upd_uid>johan</upd_uid>
<upd_name>Johan Råde</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>tidying up a bit</upd_detl>
<upd_diff>@@ -28,2 +28,2 @@
-&lt;gloss&gt;mutual life (in go)&lt;/gloss&gt;
-&lt;gloss&gt;seki&lt;/gloss&gt;
+&lt;gloss&gt;seki (in go)&lt;/gloss&gt;
+&lt;gloss&gt;mutual life&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2022-08-20 02:41:53" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_diff>@@ -26,0 +27 @@
+&lt;field&gt;&amp;go;&lt;/field&gt;
@@ -28 +29 @@
-&lt;gloss&gt;seki (in go)&lt;/gloss&gt;
+&lt;gloss&gt;seki&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2022-08-20 03:47:46" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
</info>
</entry>