<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Great East Sea Tug-of-War</title>
	<atom:link href="http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/</link>
	<description>Korea... in Blog Format</description>
	<pubDate>Thu,  8 Jan 2009 20:59:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Infidel Confessions  Primadonnas Vs. Princesses</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17710</link>
		<dc:creator>Infidel Confessions  Primadonnas Vs. Princesses</dc:creator>
		<pubDate>Sat, 04 Jun 2005 00:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17710</guid>
		<description>[...]   	Its an unsatisfactory conclusion to an unproductive situation:  	The standoff over the Shinpung-ho, a 77-t [...]
</description>
		<content:encoded><![CDATA[<p>[...]   	Its an unsatisfactory conclusion to an unproductive situation:  	The standoff over the Shinpung-ho, a 77-t [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: usinkorea</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17709</link>
		<dc:creator>usinkorea</dc:creator>
		<pubDate>Fri, 03 Jun 2005 23:56:36 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17709</guid>
		<description>I was saying that if Korea wanted to do something about the issue against Japan, they should not have taken the direct physical confrontation route.  A diplomatic, media, or limited, punitive trade smack would have been much, much more preferrable.

By this, I am taking it for granted Korea wanted to "make a statement" with its actions - that it wanted to react to Japan and the EEZ zone and fishing vessel issues.

I did not consider the "do nothing" approach at all, because it doesn't seem like something Korea was considering.  The reaction within Korea to the physical confrontation doesn't seem, from what little I know, to have generated a "why did we feel the need to do anything" consideration of the event....</description>
		<content:encoded><![CDATA[<p>I was saying that if Korea wanted to do something about the issue against Japan, they should not have taken the direct physical confrontation route.  A diplomatic, media, or limited, punitive trade smack would have been much, much more preferrable.</p>
<p>By this, I am taking it for granted Korea wanted to &#8220;make a statement&#8221; with its actions - that it wanted to react to Japan and the EEZ zone and fishing vessel issues.</p>
<p>I did not consider the &#8220;do nothing&#8221; approach at all, because it doesn&#8217;t seem like something Korea was considering.  The reaction within Korea to the physical confrontation doesn&#8217;t seem, from what little I know, to have generated a &#8220;why did we feel the need to do anything&#8221; consideration of the event&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: baduk</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17708</link>
		<dc:creator>baduk</dc:creator>
		<pubDate>Fri, 03 Jun 2005 21:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17708</guid>
		<description>Who said SK and Japan can never have an armed conflict over Dokto?  War can happen easily.  Countries have fought over things cheaper than fish.</description>
		<content:encoded><![CDATA[<p>Who said SK and Japan can never have an armed conflict over Dokto?  War can happen easily.  Countries have fought over things cheaper than fish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gorea</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17707</link>
		<dc:creator>gorea</dc:creator>
		<pubDate>Fri, 03 Jun 2005 20:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17707</guid>
		<description>Mainichi Simbun &lt;a href="http://www.mainichi-msn.co.jp/kokusai/america/news/20050603k0000m030090000c.html" rel="nofollow"&gt;http://www.mainichi-msn.co.jp/kokusai/america/news/20050603k0000m030090000c.html&lt;/a&gt;
reported that Korean side demanded compensation and apology for the injured fisherman.

The fisherman
&lt;a href="http://www.uploda.org/file/uporg117302.jpg" rel="nofollow"&gt;http://www.uploda.org/file/uporg117302.jpg&lt;/a&gt;
He looked his condition got worse while he was in hospital.</description>
		<content:encoded><![CDATA[<p>Mainichi Simbun <a href="http://www.mainichi-msn.co.jp/kokusai/america/news/20050603k0000m030090000c.html" rel="nofollow">http://www.mainichi-msn.co.jp/.....0000c.html</a><br />
reported that Korean side demanded compensation and apology for the injured fisherman.</p>
<p>The fisherman<br />
<a href="http://www.uploda.org/file/uporg117302.jpg" rel="nofollow">http://www.uploda.org/file/uporg117302.jpg</a><br />
He looked his condition got worse while he was in hospital.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kushibo</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17706</link>
		<dc:creator>Kushibo</dc:creator>
		<pubDate>Fri, 03 Jun 2005 14:20:40 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17706</guid>
		<description>USinKorea, you are saying that Korea should have gone the emotional route on this one?

I was glad that it ended with the Korean skipper admitting fault. I was glad that people could see that not every Korea-versus-Japan issue has the Korean side in the right. I haven't seen yet this morning how it is playing in the press, but I was glad to see that the Korean side seemed to give in because they knew the Korean skipper was in the wrong.</description>
		<content:encoded><![CDATA[<p>USinKorea, you are saying that Korea should have gone the emotional route on this one?</p>
<p>I was glad that it ended with the Korean skipper admitting fault. I was glad that people could see that not every Korea-versus-Japan issue has the Korean side in the right. I haven&#8217;t seen yet this morning how it is playing in the press, but I was glad to see that the Korean side seemed to give in because they knew the Korean skipper was in the wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: usinkorea</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17705</link>
		<dc:creator>usinkorea</dc:creator>
		<pubDate>Fri, 03 Jun 2005 07:54:01 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17705</guid>
		<description>I'd have to wait for a lawyer to give a definitive answer or someone quote more from the rules that apply...

but, I would think it screwy if a ship that has been documented as having broken the rules or laws of the area returns, it can't be boarded unless it allows the ship to start breaking the law again -- that it has to be caught red handed or not at all.

But, international treaties and conventions have a logic all their own frequently enough.

To me, regardless of the legal issues, I believe Korea picked a very bad way to handle the situation.  Raise hell in the media.  Hurt Japan by cancelling some inter-government meetings or something like that - a diplomatic tiff type move.  Or, temporarily block some imports from Japan for some months, preferrably any trade in sea food.

Using brute force and a brute force confrontation isn't the way I would have gone.  It makes both nations look very petty and more so for the Koreans since their coast guard got involved second.</description>
		<content:encoded><![CDATA[<p>I&#8217;d have to wait for a lawyer to give a definitive answer or someone quote more from the rules that apply&#8230;</p>
<p>but, I would think it screwy if a ship that has been documented as having broken the rules or laws of the area returns, it can&#8217;t be boarded unless it allows the ship to start breaking the law again &#8212; that it has to be caught red handed or not at all.</p>
<p>But, international treaties and conventions have a logic all their own frequently enough.</p>
<p>To me, regardless of the legal issues, I believe Korea picked a very bad way to handle the situation.  Raise hell in the media.  Hurt Japan by cancelling some inter-government meetings or something like that - a diplomatic tiff type move.  Or, temporarily block some imports from Japan for some months, preferrably any trade in sea food.</p>
<p>Using brute force and a brute force confrontation isn&#8217;t the way I would have gone.  It makes both nations look very petty and more so for the Koreans since their coast guard got involved second.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MichaelMichael</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17704</link>
		<dc:creator>MichaelMichael</dc:creator>
		<pubDate>Thu, 02 Jun 2005 23:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17704</guid>
		<description>Japan has every right to sieze that boat if made a de facto violation of Japan's EEZ, and the violation by definition would be illegal if it had been cited for illegal fishing in past. It's in the UN convention on EEZs: "fixing quotas of catch, whether in relation to particular stocks or groups of stocks or catch per vessel over a period of time or to the catch by nationals of any State during a specified period." The Korean gov't shouldn't make a big deal of this, because its been doing the same thing to Japanese fishermen for years.</description>
		<content:encoded><![CDATA[<p>Japan has every right to sieze that boat if made a de facto violation of Japan&#8217;s EEZ, and the violation by definition would be illegal if it had been cited for illegal fishing in past. It&#8217;s in the UN convention on EEZs: &#8220;fixing quotas of catch, whether in relation to particular stocks or groups of stocks or catch per vessel over a period of time or to the catch by nationals of any State during a specified period.&#8221; The Korean gov&#8217;t shouldn&#8217;t make a big deal of this, because its been doing the same thing to Japanese fishermen for years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oranckay</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17703</link>
		<dc:creator>oranckay</dc:creator>
		<pubDate>Thu, 02 Jun 2005 22:55:04 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17703</guid>
		<description>"OhMyNews ran a rather interesting report last night that might help us understand some of the issues that were involved in this case. It would seem that last year, Tokyo informed Seoul that it had made a ?€œblacklist?€? of 22 Korean fishing vessels that Japan claimed had violated Japan?€™s EEZ a combined total of 81 times last year. Most, like the Sinpung-ho, were eel trawlers. The vessels on the list would be subject to seizure if caught in Japan?€™s EEZ, regardless of whether they were illegally fishing or not"

Leave it to OhmyNews to add some helpful and objective information to the issue and help understanding.... if true, this part: 

"The vessels on the list would be subject to seizure if caught in Japan?€™s EEZ, regardless of whether they were illegally fishing or not"

Means that Japan was saying it would be acting illegally. Japan just doesn't have the right to sieze ships that are in its EEZ but not in its territorial waters unless they are doing something illegal, so if it said it would sieze them regardless....</description>
		<content:encoded><![CDATA[<p>&#8220;OhMyNews ran a rather interesting report last night that might help us understand some of the issues that were involved in this case. It would seem that last year, Tokyo informed Seoul that it had made a ?€œblacklist?€? of 22 Korean fishing vessels that Japan claimed had violated Japan?€™s EEZ a combined total of 81 times last year. Most, like the Sinpung-ho, were eel trawlers. The vessels on the list would be subject to seizure if caught in Japan?€™s EEZ, regardless of whether they were illegally fishing or not&#8221;</p>
<p>Leave it to OhmyNews to add some helpful and objective information to the issue and help understanding&#8230;. if true, this part: </p>
<p>&#8220;The vessels on the list would be subject to seizure if caught in Japan?€™s EEZ, regardless of whether they were illegally fishing or not&#8221;</p>
<p>Means that Japan was saying it would be acting illegally. Japan just doesn&#8217;t have the right to sieze ships that are in its EEZ but not in its territorial waters unless they are doing something illegal, so if it said it would sieze them regardless&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MichaelMichael</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17702</link>
		<dc:creator>MichaelMichael</dc:creator>
		<pubDate>Thu, 02 Jun 2005 22:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17702</guid>
		<description>Back to our grilled eel.</description>
		<content:encoded><![CDATA[<p>Back to our grilled eel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kushibo</title>
		<link>http://www.rjkoehler.com/2005/06/02/great-east-sea-tug-of-war/comment-page-1/#comment-17701</link>
		<dc:creator>Kushibo</dc:creator>
		<pubDate>Thu, 02 Jun 2005 22:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://rjkoehler.com/?p=1658#comment-17701</guid>
		<description>The issue has been resolved, with the Korean skipper admitting fault.</description>
		<content:encoded><![CDATA[<p>The issue has been resolved, with the Korean skipper admitting fault.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
