Autocannons are not machine guns

Fragment of a discussion from User talk:Rua

I'll go ahead and put it back then since it seems to have been a misunderstanding.

2602:4B:AC4E:6800:388B:977B:6489:E4CA01:26, 31 October 2014

Again you removed the definition "A large-bore machine gun". So yes, you did remove it.

CodeCat01:36, 31 October 2014

We're talking about two different things. I removed the "large-bore machine gun" definition and simultaneously added the autocannons on aircraft line. I figure whoever added the large-bore machine gun line was most likely thinking of autocannons.

My understanding was that you said that my usage comment about autocannons on aircraft makes the machine gun definition correct, which led to my first comment above saying that autocannons are not machine guns. There is no version of a cannon that is a machine gun, or vice versa, so the definition of "a large-bore machine gun" is completely incorrect. If you want to say that some cannons are autocannons, that would be correct, but I think the autocannons on aircraft line under usage covers it.

2602:4B:AC4E:6800:388B:977B:6489:E4CA04:40, 31 October 2014

Ok, but then why didn't you replace the machine gun definition with one about autocannons? Usage notes aren't meant to add more definitions to a word, only to give information about how the listed definitions are used in more detail.

CodeCat16:43, 31 October 2014

Because a cannon isn't a type of autocannon. An autocannon is a type of cannon. So how would I add autocannon as a definition of "cannon"? Or, do you want me to list shorthand as a definition? I mean, I could say that "cannon" is sometimes used as short for "autocannon" under definitions, but that doesn't seem right.

2602:4B:AC4E:6800:E828:9073:382B:13AE00:14, 1 November 2014

I'm not sure. I'm fairly certain that there are other examples where a more generic term is widely used to refer to a more specific term, to the point where using the specific term is thought of as overspecifying. "computer" is another example; most people use it specifically for a desktop personal computer. An egg is assumed to be from a chicken, and milk is assumed to come from a cow. Maybe this should be brought up at the Tea Room as there may be an existing practice concerning cases like this already.

CodeCat00:20, 1 November 2014

Yes, but all of your examples are usage, not definitions.

2602:4B:AC4E:6800:E828:9073:382B:13AE01:22, 1 November 2014

What's the difference?

CodeCat01:23, 1 November 2014

Usage is just an example of how the word is sometimes used. A definition is what the word actually means.

2602:4B:AC4E:6800:E828:9073:382B:13AE06:17, 1 November 2014

But how do you determine what a word means, if not by how it's used?

CodeCat13:57, 1 November 2014

Are you pulling my leg?

One definition of "car" could be "a vehicle used for transportation" while usage could be "Jane drove the car to the store."

2602:4B:AC4E:6800:9951:C4B4:92FE:271D01:35, 2 November 2014

Of course, but when you say that sentence, you're using the word "car" and intend it to mean something specific. That's its definition; it's what people mean when they say it.

In this case, when people say "cannon", they sometimes mean something that could also be described by the word "autocannon". So in that sense they are synonyms. Therefore, one of the definitions of "cannon" is "autocannon".

CodeCat01:52, 2 November 2014

If you want to say that one of the definitions of "autocannon" is a "cannon" with certain particular characteristics, then I'm ok with that. I'm not ok with saying that a "cannon" is an "autocannon" because that would be a lie.

2602:4B:AC07:1A00:9951:C4B4:92FE:271D09:27, 2 November 2014
 

I've decided I can live with adding "sometimes used as shorthand for "autocannon", when mounted on aircraft" if it's genuinely important to you. Emphasis placed on shorthand.

2602:4B:AC07:1A00:9951:C4B4:92FE:271D10:22, 2 November 2014
 

But CodeCat's examples are unlike either of yours- I think you're reanalyzing things without realizing it. A definition is just a tool for presenting a meaning- it doesn't determine meaning, unless it's adopted by users of the language. As for the meanings themselves, they can't exist independently of usage. Any language is a negotiation between those who use it: everyone may have a different idea of what a term means, but only those meanings that are understood by the one producing and the one receiving will work: I may be convinced that German means extraterrestrials with three ears, but if I use it that way, no one will understand me, and if I try to assign that meaning to what others say, I won't understand them. The way this negotiation works is through usage. At one time, an earlier form of hound was a general term for any dog, but at some point, it became restricted to a particular type of dog, and the earlier form of dog became the general term. The kind of things CodeCat is talking about are hidden parts of the meaning that may, at some point, become explicit and thus part of what you would call the definition. Even now, people tend to use qualifiers for any type of milk that's not from a cow: goat's milk, mother's milk, etc. That's a sign that things are already heading in that direction.

Chuck Entz (talk)02:24, 2 November 2014

Chuck, you wouldn't list "short for goat's milk" as a definition for the word "milk". You could, on the other hand, list "milk that comes from a goat" as a definition for "goat's milk". So, you could go to "desktop personal computer" (if it was one word) and add a definition that it's a certain type of computer, but you wouldn't list desktop personal computer as a definition of computer.

2602:4B:AC07:1A00:9951:C4B4:92FE:271D09:23, 2 November 2014