Talk:ROKS Cheonan (PCC-772)

258: 240: 882:, because you have to read both articles before you know all the facts, because even though they are both very short, they are not properly formatted in a parent-child manner as you would expect - information has been randomly placed into one article or the other, with glaring issues like, why is the Reaction section, and the detailed timing info, in the ship article and not the incident article? This is unnacceptable, and makes Knowledge look as if it has no clue as to how to properly present information. If people want separate articles, then per WP:SUMMARY, do it properly and make the incident article the detailed one, and the ship section a brief summary. But as there is very little information right now, it would be quicker, and better for readers, to just merge it. It would take ten minutes to do so. This is a wiki, it is not going to be a disaster if 2222:(BTW, is that site South or North Korean?), most notably that of a grounding on a reef near Baengnyeong Island. Those in favor of this theory say that a torpedo triggered explosion is unlikely, as the hull of the ship was scratched and the propeller shaft was bent, which they say would have been as a result of the ship impacting with the reef." One other thing: it would help your case immensely if you could find another source, doesn't even have to be English, that says the same thing; I'm a little wary of possibly controversial topics supported by a single source. Cheers, 2237:

the torn part on the ship is not consistent with the torpedo theory, the fact that no explosive material (RDX) was found on the bodies while they were found on the ship, the fact that it would've been nigh impossible for a submarine to sneak past dozens of American and South Korean ships, let alone the fact that the ROKS Cheonan is the kind of ship designed for this kind of thing and has lots of anti-submarine procedures. In any case, here's some more sources, not from Media Today.

526: 2018:

also i read that after aome 38 hours or 3 days at most)i didnt bother memorising exactly but it wasn't very much) the air in survival cabins would be exhausted. my question are such cabins standard in 20 year old ships of this size? the cabins appeared the reason for the immediatly very high level of rescue activity's. however at 40 m deep the water of 4 degrees, strong currents and poor visibility apparently frustrated all attemps to enter parts of the ship.

4013:) runs to 4KB; this one is 19KB with a large chunk of that in the "sinking" section. It's already overweight, there; why do you want to add more? There is a 70KB article already on the sinking, and the fall-out from that. What, of the 15-odd KB about the sinking here isn't overlap? And why wouldn't it be more economical, as well as clearer, to have a brief statement here about the sinking, and a main article link to the other page for anyone who wants more? 2347:, but the article on the ship itself doesn't just say "The ship was attacked" and leave it at that; it says the basic stuff about the attackers and aftermath. What I'm concerned about here is this article ending up saying, in effect, "The ship sank," and not going any further. While I do think this article shouldn't go particularly in-depth into the cause of sinking, not mentioning it at all is, IMHO, a little lacking. Cheers, 3331:

Combining them would result in a sort of mish-mash of completely seperate content--the ship and its sinking, covered more in this article, and the political background and effects of the sinking, covered in the other. Putting the two together would completely outweigh the content that's more appropriate in this article, as well as throw the content of the other under a title and in a context where it fits rather awkwardly.

304: 43: 510: 591: 570: 395: 59: 21: 2396:, which has just one article. USS Cole was a major ship that already had a substantial article, justifying a secondary article. I think the Cheonan situation is more like the Pueblo. But I don't feel strongly enough about this to make a major change! It will be easier when the official report is out, as that could be the basis in this article and the secondary one can be the whole saga! 542: 90: 467: 456: 445: 423: 142: 2754:, which deals more with the sinking of the ship, and covers it in more detail than this article. Secondly, that article does already discuss alternate theories, such as what you appear to be propounding. Lastly, it's pretty unlikely that it's going to get changed; the current consensus is to focus more on the official theory behind the sinking, since that's what most 121: 353: 321: 212: 3680:); as 6 contributors were against, and only 2 (the nominator and another) in favour, there was hardly a consensus for the merger. And as the last comment was the day before you closed it, the discussion was hardly “stale”. And am I being criticized for not closing the last proposal in time, or for wanting to close this one too soon? 434: 2287:; he then failed to add said information into that article. Crap! I'm inclined to revert his edit, although I'd agree that merge tag is unneeded. Definitely want to keep the cause of sinking in this article, at least a bit. And I'm perfectly happy to add something in on the alternate theories. Thoughts? 3330:

I think a merger is a bad idea because I'm thinking more along the lines of N2e; whether or not the ship would be notable without the sinking is irrelevent; what we have to think about is how we get the better articles. In this case, I think higher quality content come from having seperate articles.

3094:

The reason that the articles should be merged is simple. There is little of interest about this ship apart from the sinking. If it had a notable service record such that it would be a bad idea to have so much information detracting from that I could quite understand. Yet it was just a patrol ship and

2236:

Maybe, but there's equally as a lot of things that don't add up if you take the case about bubble-jet torpedoes, like the fact that there's no water spout from the explosive that was sighted, the injured didn't hurt their ears (remember, people who just shoot guns wear earplugs to shield their ears),

2032:

Response: It is possible it was an old mine, though more probable it was a torpedo. If you do a search for HMAS Torrens you'll see how a ship of similar vintage can be split in half with a detonation occurring some distance from the actual hull. I was in the Australian Navy at the time this occurred,

1435:

I'm in two minds about if we need a secondary article yet. So far I'd have been content with a single article. If/when this story develops significantly beyond the sinking and recovery politically, then I'd have gone for a secondary article. But since we already have a seconondary article, perhaps it

3653:

Xyl, you are misrepresenting my position. I have not just repeated previous proposals. The last one didn't have a rationale and the one before that was not properly concluded (nor carried out in my view). This is the first merger proposal as far as I can see that's trying to get outside comment, for

3632:

One of the problems with this page is that it is dominated by the section about the sinking. This is a ship article page, which should deal with the stuff we normally have in ship articles (construction, dimensions, armament (if it's a warship), career; the ships fate shouldn’t have more than about

3424:

instead of a long list within the sinking article), but perhaps a better solution would be to merge everything upwards of the "cause of sinking" section of the sinking article into this, and rename the other something like "effects of the sinking of ROKS Cheonan." That would of course be exactly the

3402:

Re C628: If the other article is covering the political background and effects rather than the actual sinking, why is it titled "sinking"? All sinking-related information should be in the article with "sinking" in the title; if there's too much political stuff in there, maybe it should be split to a

3305:

apart from her sinking. Apart from the subjectivity of that (people like me who are interested in ships for their own sake would like to know more about the ship itself) it was pointed out on 27 March that ships are inherently notable, and that has been alluded to a couple of times since. Regards...

3282:

John -- I absolutely see your point about the Cheonan article; and I agree with you that there is, to date, very little additional info about the multi-year life of the Cheonan that is documented in this article. However, that is a separate topic of discussion from a merger. If you were to start a

2971:

article about a major international incident which occurred in 2010. It stands just fine on its own, and meets Knowledge criteria for notability. If it were to be buried inside the article on the ship itself, it would lose its very appropriate prominence as article-worthy in its own right, as well

2365:

should not have any mention of the 9/11 attacks. Instead, it should simply say "airplanes hijacked by terrorists crashed into the buildings and caused them to collapse." It should not have a whole section about the destruction of the towers, or specific casualties(and these have stuff like "oh, this

2221:

Hmm...I'm not sure...I honestly don't think any of those are right (I mean, c'mon, how does the grounding of a ship cause it to break in half? That's gotta be a first), but I don't see any harm in writing something in there to the effect of "Other theories have also been proposed by the Korean media

3909:

Per discussion in the section above, on the potential merger of the Cheonan article (this one) with the Cheonan sinking article, several editors have offered that THIS article contains entirely too much detail about the sinking, given the existence of the other article on the sinking alone, and the

3419:

Because when it was originally created, it was a lot more about the actual sinking; it was created very shortly after the original incident, and the political effects were largely nonexistant, and it's just developed into having a great deal of the political effects of the event. There's been some

3170:

stands just fine on its own, and meets Knowledge criteria for notability. That article is only partially about the demise of the ship; it is significantly about the major international political actions which followed the sinking. If it were to be buried inside this article on the ship itself, it

2735:

It should also be mentioned that the idea of a 29 meter long DPRK "mini submarine" conducting combat in an area of shallow sea less than 25 meters deep is implausible. Shallow water combat is intolerably dangerous for subs due to collision, look at what happened to the 160 meter long russian Kursk,

2709:

The torpedo remains as mentioned in the article, are worth nothing, because the imperialist south could have obtained those fragments by combing the sea-floor after previous DPRK naval excercises to spy on communist battle tech, then conveniently warehoused the remains for handy use in some kind of

2017:

i read on the aljazeera website a possible cause could be a northkorean mine from the korea war. since most had been recovered but some had been left. however the last one to explode was 20 years ago. i wonder is this the same theory mentioned in the article? why not say an "old" mine in that case?

1353:

makes more sense, particularly if there might be a skirmish or another "Baengnyeong incident" in the future. A few redirects would also suffice to point people in the right direction. We ARE talking about two countries that are, believe it or not, at war. Whatever it is that we name it, the year

789:

Seems to me the info about the ship and it's sinking warrant different articles if there was an international incident, otherwise it seems ok to redirect both links to the ship page. I agree with the intent (if not the tone) of MickMacNee; but agree with Mjroots and Julianhall that the incident may

4095:

Nonsense. As things stand there are only two short paragraphs about the sinking. No one can be confused by that at all. It is key that on an article like this people be given a full summary. A summary it shall be, but it should all the relevant information that is key to understanding the subject.

2410:

I'd also prefer a single article, but it's not worth the amount of effort it would take to do so, IMO, since there's already been so much work put into the two. That said, I still advocate at least a brief section on the cause of the sinking in this article; is there anyone who would specifically

2338:

Well, obviously they can't overlap entirely, but I think it's insane not to make any mention of the cause of sinking in this article; there has to be at least a sentence or two on it. The bulk should go to the sinking article, which I haven't been a part of editing, but to me it makes no sense to

1907:

I think it is likely that there is quite a bit of coverage in Korean-language sources that is unrelated to the sinking; over a period of 20 years, there surely must have been coverage of the ship's commissioning, construction, and operations. While this expectation of other coverage by itself does

1391:

I asked before, but I've not been here for a while, so I'll ask again; are there any objections to my trimmimg the "Sinking" section to a summary, and moving the "Reactions" (and now "Speculation") sections to the Baengnyeong Incident article? This is the Ship article, after all; they belong over

1243:

This incident might have happened to any ship of the Republic of Korea Navy so it make little sense to include the details of the sinking on this page. It should be have its own distinct article. The material on this page should be reduced to a short précis of what happened with a redirect. TBH I

979:

There has been no support yet for a merge, therefore I've reverted the conversion of the Baengnyeong Incident article into a redirect to this article. By all means let's continue to discuss this, but that action was premature. I think it is still too early to call this one, and am keeping an open

4232:

I have no idea how to edit this thing. Never had to, and I'm probably doing it wrong. Oh well. Someone can help me out on that part surely. I just wanted to add, USS LASSEN was there. We were one of the first responders(US side) and were stationed between N and S korea ships. We never got

2503:

I came here to learn and was surprised to find no photos of this (now) very notable ship. I would think that a standard file photo of the Cheonan when sailing would be the minimum to go with a well-done encyclopedic article. But beyond that, my view is that one or two photos of the end of the

1373:

The incident happened almost 2 weeks ago, and the mess go only worse. In the current state, the Baengnyeong article is much worse than the Cheonan article, but I don't care if it's merged or not. But if it's not, all the information from the Cheonan article should be pushed into the Baengnyeong

1108:

still the worst of both worlds as Mick said above. not only are all three articles not up-to-date because the parent is longer than the child, information on the sinking in the ship class article is not included in either article and several recent developments appear in no article. i certainly

2914:

I shall add that SIZE should be addressed by skillful editing -- this is an encyclopedia after all and concise articles are the norm. (Are all the pictures needed?) The UNDUE argument is skewed by Mjroots. It is the devotion of so many digits to this recent event that is UNDUE. This point is

2717:

Luckily the DPRK has just achieved fission-ignition-less fusion a few weeks ago, a world first and now xenon-smelling South Korea does not dare to attack, knowing they could be pelted by literally pocket-sized pure fusion nuclear hand grenades, employed by the dreaded DPRK spec-op troops.

1454:

I'm a bit confused by this "secondary article" bit (also "parent-child" articles, mentioned above); which is which? The Baengnyeong Incident article pre-dates this one, and, I presumed, this was created so as to provide the ship details in a more usual format (and then, "just growed").

3657:

There is also, despite your assertions, a fair bit of support this time. You should not be so dismissive of other people's views, especially given that the proposal had been up for just two days. I am trying to engage in a proper discussion about this. After all, this isn't "votes for

2736:

which tried to fool around in 120 meters of water. Submarines need 1.5x the depth of water compared to their lenght to be able to fight without destroying themselves. The Cheonan was killed by a stray naval mine or a South Korean "Maine 1898" style conspiracy, not a DPRK mini-sub!

2848:. In this case, it is part of its own article and a separate sinking article. But "ROKS Cheonan" itself is mentioned in 43 other articles and the sinking ("ROKS Cheonan sinking") is referred to in 26 articles. My gosh! Compare and consider other significant ship sinkings. The 3828:, This is a very important article and there is no need to merge it with the article about the ship itself. Because this is a major political/military/media event, it obviously needs it's own article, like many other similar events. Therefore I am going to remove the merge tag. 2705:

The so-called "international investigation" mentioned in the article is worth nothing, because they were comprised entirely of people hailing from imperialist and capitalist economy countries, who are inherently hostile to the socialist-communist DPRK and thus never impartial.

3994:

It wouldn't be duplication, it would be setting out a decent summary of the matter. There's so little information here, if you strip out virtually everything on the sinking you're left with "this was a ship of the South Korean Navy. It had guns. It was sunk." That's pathetic.

1406:

PS As far as renaming the Baengnyeong Incident article goes, I'd incline towards "if it ain't broke..."; but shouldn't that discussion be on the talk page over there? And isn't that a symptom of the problem with this, that stuff that belongs over there keeps winding up here?

2868:. Creating and keeping it as a separate article is nothing more than editors saying "I think something notable happened here because I see it in the news and I'm concerned about the tensions between the Koreas." Moving it into the main article will lessen this problem.-- 2323:

I think that if there is to be any sense in having the secondary article, we have to keep the cause speculation/discussion out of this ship article so they have different scope. So I agree with the anon edit. I've given up on these articles mostly due to this duplication.

3283:

separate Talk-page discussion section on deleting a large amount of the redundant material from THIS article, since the detail is covered in the sinking article, I would be a big supporter of that sort of cleanup for this article, along with you I imagine. I continue to

1052:, not what might happen. All we have now, bizarrely, after the half reverted merge, is a 'child' article that is shorter than the 'parent' one. This is the worst of both worlds. Readers must be laughing their heads off at this mess, as they have done since the beginning. 3701:

is not notable because of the circumstances of her sinking, but because she is a ship. As has been said several times, here and in previous discussions, ships are inherently notable, so there shouldn't be any question of moving this content to the "sinking"

1436:

would be best to switch to that to avoid duplication. NB Besides "Baengnyeong Incident" not being a very informative title, until we know if this is an "accident" or "incident" I'd point out that using either word in a title is somewhat POV - I'd prefer

949:

I agree, there is no need to merge at the moment, but to make sure we have all the information handy because, while this may not be an INTERNATIONAL incident, there will indubitably more information that comes out and THEN make an appropriate article.

1010:

Sorry, but you hadn't expressed support for the merge here. How are other editors to know that you support a merge when you hadn't expressed that support. I made it 1 in favour of a merge (nominator) against 5 editors and 2 IPs saying "wait and see".

2680:

I've added an image of the ship's bow on the infobox and removed the tag from this section. No free image of the ship intact exists, which makes this IMO the best we can get. Credit to Lt. Jared Apollo Burgamy of the US Navy for taking the photo.

3661:

I am also disturbed that you want to shut down the discussion so prematurely. You showed no interest in closing the last proposal despite the fact it was stale for the best part of a month and had been running for two months before I closed it.

762:

As it is a current event it is imperative that we don't duplicate information, it is entirely wasteful and doubles the effort required to check and maintain the articles. The content would have to expand hugely before a split was warranted tbh.

3098:

It makes sense to have the bulk of the information here. Yet there is no need to merge every piece of information on the sinking page. There is a large amount of information there that could be summarised briefly and linked through citations.

1181:

involves the ship but is a a completely distinct issue. The same logic is applied on the RMS Titanic sinking. There is a page about its collision with the iceberg (that involves the ship) but there is a separate page discussing its class, i..e

4168:

article, and made some tweaks to the last bit. Now I'd like someone to tell me if that was a reasonable response, an overreaction, or if it didn't help at all. I will also shortly leave a not on the user's talk page directing them to this.

2041:

The Armament section in the Infobox varies from the Armament section in the article. When the correct armament is determined I suggest the Infobox be made correct and the section in the article be deleted. Data should not be duplicated.

1032:

example that Hourick gave is a reasonable comparison. I've added a main article tag to the "Sinking" section, to address Mick's point about separate development. I would also agree that the "Reaction" section, at least, belongs over there.

1318:

would suit me. I think this and the moving of the info should be done as a matter of priority as it looks silly to have so much duplicated content. Sadly I can't move the page myself as an IP, but it would be good if someone could do it.

2605:

Thanks Mjroots, the picture of the sister ship is acceptable if no free image of the intact Cheonan can be found. Hard to believe some Korean sailor from a sister ship, or from a dock, never took a photo they would be willing to share.

3950:

This is ridiculous. There is no way at all that the article had too much information on the sinking. If anything it needs more, assuming there isn't a merger. You're reducing the article to a shell that only exists for the sake of it.

3262:. With all due respect, there is nothing of any interest there and it is a few sentences. As I say above, the ship is really only notable because of the sinking. Otherwise it would be just another Knowledge article on a ship in class. 257: 239: 886:

comes flooding in, I have yet to ever see a situation where that has occured so quickly that nobody was able to perform a decent enough split before the main article became huge, which the current ship article is far from being.

4115:

It might be a good idea to add more of the ships previous service history to its article, the ship was in commision for decades before this incident and was even involved in at least one other naval battle to my knowledge, the

4233:

reported in stars and stripes, and just got the mention of "other US ships" in most US papers, but i can gurantee you, we were. I hate that the whole story doesnt get reported. - anon PO2 aboard USS LASSEN during this event.

3450:. Originally I came here to oppose, thinking that the original ship is notable in its own right (as pretty well every USA ship seems to be), but seriously, what makes this ship any more notable than any other ship listed at 3965:

The sinking has its own article! Thus, all sinking information should be there. Because we currently have separate articles (merge discussion is above, not here), we don't need duplication-- this article should only have a

533: 335: 3257:

Guys, with all due respect as far as I can see you're just supporting each other. No one has addressed my points, though if someone can point to where they were made previously, I would stand corrected. N2e, you say that

1851:

report about the sinking says that the Cheonan (PCC-772) was a ASW Patrol Combat Corvette, without SSM (Harpoons or Exocet). However, according with this source, the ship was equipped with depth charges. Is this correct?

4273:

assisted, unless it was reported by the media, then it can't be put in the article. However, Knowledge is a work in progress, and this fact may emerge at some point in the future, and can then be added to the article.

1126:

Let's just wait until the discovery of what sunk the ship. From what I've read, it will be fairly easy to identify what happened to it, esp. since they said that it should take 20 days to finish salvaging the vessel.

904:

The incident had a much larger scope than the involvement of this vessel. There were other south korean vessels involved, and this vessel was apparently not the one that fired upon the unidentified ship that cross the

4294:

This should definitely be merged into the sinking article. Most of this article deals with the sinking. I note that this has already been discussed, but perhaps editors can come to a different view with a few years'

2441:

The evidence is mounting against the 'so-called' international investigation (mainly 3 NK haters: US, Japan and SK) which determined NK to have torpedoed the Cheonan. The Chinese are not buiying it, neither are the

1142:

The ship deserves its own article IMO. The incident is an entirely different event and the article should merely contain a summary. Barring a summary, which would require work, simply copy/paste the whole incident.

1756:. Interesting it sunk off the opposite side of Baengnyeong Island from the sea border with North Korea, so in fact a considerable distance from the NLL. I haven't seen any western media with a similar map yet. 517: 331: 3618:

time this discussion has taken place, and there is as little support for the idea as there was before. Also there is nothing new in this proposal, which shows a misunderstanding of what the article is about.

1890:

generally hold that all ships are inherently notable. Obviously the sinking was the event that spurred the creation of the article, but it would have been worthy of an article if the event had not happened.

995:

There has been support for a merge, both from myself and MickMacNee, at least, not counting conditionals. I still support one properly updated article, rather than two badly out-of-date and incomplete ones.

3846:

This is not "votes for merger", so please do not arbitrarily decide to close a proposal until someone neutral like an uninvolved admin has made a decision. The proposal has been up only just over a week.

2713:

All in all the Cheonan incident smells much like a repeat of the 1898 american battleship Maine trick to start the Cuba war: sacrifice a warship to create pro-war sentiment, but this time in South Korea.

2064:

You're half right, the infobox shoud match the main section, but the data is correct to both. The infobox is there to give a quick resumé of the ship, but the details lie in the main body of the article.

3371:

are notable, then yes, I think that this ship deserves an article. (Going on a tangent, if they are notable, all the articles could likely be created in a semi-automatic fashion, using refs 1 and 2 from

1421:

I have no objection with what Xy has recommended, and I think it is the right time to do so. But let's try to word the "speculation" so it can later be included when the actual cause is determined. --

2864:. Over eight thousand (8,645) sailors died in this battle! Is there a separate article for the sinking of each ship? No. Keeping this article separate from the main ship article contributes to 2123:

I see the cause, and it's like, "what?" There are plenty of people who say that the cause was not due to a bubble-jet torpedo. I'll put some sources here shortly (they're in Korean, of course.).

1871:

This ship is twenty years old and the only noteworthy thing about the ship is that it blew up and sank? Is this the only reason this article along with the corvette-class article was created?

4313:- per my reasons given in the original discussion. I can see no good reason to merge, as the sinking would dominate the article, which was the reason that it was split off in the first place. 3038:

per Mjroots. All we need is a picture of the Cheonan. As all US military photos are considered public domain, surely an American serviceman might have seen the ship and taken a picture of it.

2185: 3353:

would not be any less able to support an article today if the incident had not happened. The fact that an article hadn't been written before the incident happened in neither here nor there.

2191: 2188: 2182: 1583:, A casual reader (like me) spent a lot of time reading two articles where is much dup info. BTW, I added current status on opening paragraph which was not clear (after reading both) -- 3166:; this article covers the existence and multi-year life and missions of the ship itself, while the other article explicates a major international incident which occurred in 2010. The 1646:

this. The discussion of this proposal was largely finished by the end of April, and the last contribution was June. Some 20 editors took part; 8 were for, and 12 against, so there was

4037:

The section here is not overweight in the slightest, it is two short paragraphs. This can be expanded upon, though possibly by replacing some of the existing content at the same time.

4365:

request. I'm not saying that any move was in and of itself disruptive, and none was in bad faith, but the time has come to settle on a title. The current title is in accordance with

4184:

Its quite amazing to see people questioning the capabilities of minature submarines, especially when one looks at how they were used in the past, such as crippling the battleship

3081:. There is, however, a fair amount of interest in reconfiguring the articles to address some of the concerns behind this proposal, so I suggest that this be discussed further. — 2915:

brought out by Lynbarn -- now that several months have passed, what is going on between N & S Korea? Not much. The attention has turned to succession issues in the north.--

1961:

boundary; it was not part of the Armistice agreement, and is not accepted by North Korea, which claims Baengnyeong Island and others. The most that can be said is that it is the

4490: 4435: 2852:

has an article, but its sinking is described in its basic article and in the larger attack on Pearl Harbor. (Indeed, the US lost 3 battleships and 6 aircraft carriers in WWII

2640:

tag on the article to see if we can find a free image of the post-explosion ship (either at recovery, or in dry dock), as this would still be helpful to improving the article.

641: 631: 3376:.) However, I still think that this article gives too much weight to the sinking; all information contained herein should also be covered at the sinking article (because it's 2658:

I agree with keeping the tag too. It's a similar situation to many aircraft accident articles, where we have to have a photo of a similar aircraft where no free image exists.

4475: 3636:

There is a sugestion (below) that the "sinking" section be pruned; I suggest we go with that, to deal with the overlap issue, and that we close this, as having no consensus.

2996:

to a merger. The sinking was an incident with wider implications, best explored in an article specifically on that subject; it'd be to much for a section in a ship article.

2484:

I've just converted some bare url refs to the standard format. Ref #15 needs the title checking, as I suspect I've picked the wrong one. The language also needs checking.

4480: 2853: 1093:..."), but I’ve no idea how to do that. Any thoughts? (with hindsight, if that had been done in the first place, this discussion would probably have been un-necessary). 408: 365: 4470: 4034:, except that its part of the SK Navy. If Knowledge didn't have a "include any old rubbish, even if it's not necessary" position, Sokcho wouldn't have its own article. 3206:

I was the original proposer back in September. Alas, the proposal did not go anywhere then, and its not going anywhere now. So I've deleted it. History will tell.--

864:

I would have thought it would be best to keep them seperate for now, because both of these articles could potentially expand quite a bit as new information comes in.

4430: 2805:- the latter meaning that merging the sinking article into this article would give undue weight to the sinking compared with the rest of the history of the ship. 607: 192: 4485: 4465: 2545:

That's good to know. I'm not an image-meister either, but I understand that some image-oriented Wikipedians monitor the {reqphoto} list so the addition of the

394: 4077:

I agree with N2e, C628 and M.Nelson; the sinking section needs drastically reducing, to avoid the overlap with the main article (or giving the impression this

1994:. (Un-referenced too I might add!) Consistency of data across related articles is a common issue on Knowledge IMHO. I have added a ref and made it more NPOV. 4420: 549: 339: 221: 2186:

http://news.naver.com/main/hotissue/read.nhn?mid=hot&sid1=100&gid=467439&cid=468997&iid=1024094&oid=006&aid=0000044770&ptype=011

2822:- agree with Mjroots, and also the sinking is a politically and historically significanrt event in its own right, and worthy of it's own article. Regards, 2192:

http://news.naver.com/main/hotissue/read.nhn?mid=hot&sid1=100&gid=467439&cid=468997&iid=650926&oid=006&aid=0000044794&ptype=011

2189:

http://news.naver.com/main/hotissue/read.nhn?mid=hot&sid1=100&gid=467439&cid=468997&iid=215032&oid=006&aid=0000044818&ptype=011

2183:

http://news.naver.com/main/hotissue/read.nhn?mid=hot&sid1=100&gid=467439&cid=468997&iid=209646&oid=006&aid=0000044750&ptype=011

4460: 4455: 3421: 3515:'s article gives a relatively in-depth view of the ship's entire history, not being overweighted by the bombing. If you remove the bombing section from 2392:

This is why I've come round to the view it would be better to have a single article. I think a better one-major-event minor-ship comparison article is

3967: 2366:

company lost a lot of employees, how many of them were firefighters, etc."). Again, another example of what C628 is saying, just a more famous one. --

1209:

article has a substantial general account of the sinking, far in excess of what the Cheonan article has. And the auxiliary article is the specialised

598: 575: 1806:

No, sorry. Google translate of the surrounding text does not help. (Guessing, the two red X are where the two sections of the ship are now resting.)

1177:

I agree with the two points being kept separate. This article is about the ship, its class, its armaments, its construction and its naval role. The

274: 160: 3271: 3231: 4425: 4415: 2381: 2265: 2209: 2168: 2141: 4004: 3765:. So a merger seems to be going in the wrong direction (unless by “merge” what is meant is actually “delete and redirect”; which really isn’t 3091:

I have started a new discussion as the previous motion to merge had no rationale and should not have been discussed. It had also gotten stale.

360: 326: 202: 4105: 4049: 3884: 3856: 3671: 2085:

the size of this ship is variously reported as 1,200 tons, 1,350 tons, 1,400 tons, and even 1,500 tons. only one can be right but which one?

1753: 369: 3705:

As for support, the discussion is curently running two-to-one against, which is better than the last proposal, but not as good as the first.

1265:

Agreed. the summary of the incident on this page should be VERY short with the meat of the content transferred to the page on the incident.

4450: 4153: 1320: 1266: 740:

turn into a major international event. Let's hold fire until a bit more information becomes available before we decide one way or another.

4361:

I've move-protected the article. It has been moved a number of times now, so any further moves should only be as a result of a successful

3960: 3790:, this event was certainly notable enough to be deserving of it's own page it shpuld be renamed to say "Sinking of ROKS Cheonan" though.-- 811:

I think waiting until the south and north korean governments commented on the incident would be best, right now virtually nothing is known

4440: 2049: 1997: 1251: 797: 4249: 1923:, if someone could find information about the vessels part in that battle it might expand the history second a bit beyond the sinking. 1720: 835: 2468: 2019: 1924: 1469:

PS Anyway, I've moved it over; I trust that everyone's OK with that. I've no strong opinion on how good an article it is, though...

1159: 2527:

from the article...I suppose the best shot at an image now would be getting a South Korean Wikipedian to snap a picture of another

2504:

ship's life, or possibly of the salvage operation pulling the ship out of the water, would be appropriate. What to others think?

1633:

many ships with far less data stand alone with its own article, and there's clearly enough unique data to support its own here. --

2837:

The following is the commentary I posted in the sinking article prior to tagging for merger. Also, one endorsement is included:

2737: 2719: 878:

The only thing achieved by hanging around waiting to see if something happens, is that both of these articles remain substandard

278: 164: 70: 4445: 3875:

You have misread me. My passions are hardly "inflamed", I was just pointing out some facts that you might have missed. Thanks,

2933:

Your edit summary did say see discussion, but on clicking the link, there was no discussion - which is why I started it here.

2377: 2261: 2205: 2137: 4161: 1550:

article so they now largely duplicate each other again. 2) If you put both articles into the article traffic statistics tool,

3451: 3111: 282: 168: 2976:

article content with this content on the demise of the ship, and the major international political actions which followed.

4081:

the main article) on the sinking. It could also do with an edit note (<--) to discourage people adding more stuff there.

3072: