<entry id="2159187" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>1035370</ent_seq>
<r_ele>
<reb>オポジションパーティー</reb>
</r_ele>
<r_ele>
<reb>オポジション・パーティー</reb>
</r_ele>
<sense>
<pos>&n;</pos>
<xref type="see" seq="1537580">野党</xref>
<misc>&rare;</misc>
<gloss>opposition party</gloss>
</sense>
<info>
<audit time="2013-05-11 06:58:37" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Added additional dotted reading(s) via batch update.Added additional dotted reading(s) via batch update.
-*- via bulkupd.py -*-</upd_detl>
<upd_diff>@@ -6,0 +6,3 @@
+&lt;/r_ele&gt;
+&lt;r_ele&gt;
+&lt;reb&gt;オポジション・パーティー&lt;/reb&gt;</upd_diff>
</audit>
<audit time="2021-11-06 21:29:49" stat="A" unap="true">
<upd_name>Tsuchida</upd_name>
<upd_detl>I randomly came across this and I started wondering. What is it that justifies a word like this being in the dictionary? Isn’t this just plain English? 
The Japanese language sure is very creative with foreign words, but I don’t think that means there should be an entry for every English word 
rendered into katakana. When you search “opposition party” on Jisho.org for instance, obviously “野党” (the translation the searcher is probably 
looking for) will pop up, but this 
entry does too. I think that entries like this one can be quite misleading for language learners and I think we should only create entries if the 
word is actually used regularly in Japanese (and not just because one guy at one point used it). This is just my personal opinion; I wonder how 
others feel about this.</upd_detl>
</audit>
<audit time="2021-11-16 11:02:11" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>It'gets a little use and it's a sub-entry in ルミナス. Best to keep it and tag it as not common.</upd_detl>
<upd_refs>ルミナス
0 n-grams</upd_refs>
<upd_diff>@@ -11,0 +12 @@
+&lt;misc&gt;&amp;obsc;&lt;/misc&gt;
@@ -12,0 +14 @@
+&lt;gloss&gt;the opposition&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2021-11-16 11:43:15" stat="A">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>It's also in 現代人のカタカナ語辞典 and mentioned 
in daijs' オポジション entry. To try and answer 
Tsuchida's question: we don't add words like 
this unless there's some evidence they're 
being used or appear in some other dictionary 
or work of reference. We don't avoid obscure 
or outdated words if their usage is well-
documented.

More commonly as xref</upd_detl>
<upd_diff>@@ -11,0 +12 @@
+&lt;xref type="see" seq="1537580"&gt;野党&lt;/xref&gt;</upd_diff>
</audit>
<audit time="2021-11-17 10:16:27" stat="A" unap="true">
<upd_name>Tsuchida</upd_name>
<upd_detl>Thank you for the reactions. I understand the notion of including obscure terms as long as they’re well-documented. However, in that case, 
wouldn’t it be a good idea to try and more actively add cross references if it’s an obscure katakana entry, in order to avoid learner confusion as 
I described in my previous comment? I’m not saying every katakana term has a “Japanese” equivalent; katakana terms are very much Japanese 
themselves and they can have different nuances than their “equivalent”, so a cross reference would not always be in place. But again I’m trying 
to look at it from the perspective of language learning and user friendliness.</upd_detl>
</audit>
<audit time="2021-11-17 14:34:31" stat="A">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>We add such cross references when they make sense, but I'm not really seeing how this would be a solution to the problem you're seeing here. It's probably 
better to tag entries that are obscure as [obsc] (or [obs], [arch], [dated]) and let apps and sites use that info + our frequency tags to make reverse 
searches bring up the most relevant entry on top and perhaps hide some others. (jisho.org does not currently hide entries that are tagged obsc from 
reverse searches. If you think they should, it'd be best to take it up with them.)

I've suggested implementing an explicit "more commonly as" type of xref on the Github, which by the way is a better place to discuss topics that concern 
policy than the comment section of an individual entry. 
https://github.com/JMdictProject/JMdictIssues/issues

If you come across any other obscure katakana words you think should have xrefs to more common words with similar meaning or be tagged as [obsc], go ahead 
and edit them.</upd_detl>
</audit>
<audit time="2021-11-17 21:56:39" stat="A">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I don't think we need more than one gloss for obscure カタカナ語 like this.</upd_detl>
<upd_diff>@@ -15 +14,0 @@
-&lt;gloss&gt;the opposition&lt;/gloss&gt;</upd_diff>
</audit>
</info>
</entry>