jbw wrote:
My point exactly. It's your definition, but others (including the dictionary) define it far more broadly. This is my take on the issue from a fairly extensive thread on another site:
"I've often heard it said on these and other boards that if there's no smoke, there's no BBQ. Well, one other barbecue locus where the smoke doesn't necessarily touch the meat is in the dictionary. This is how Webster's defines "barbecue":
"1 : to roast or broil on a rack or revolving spit over or before a source of heat (as hot coals)
2 : to cook in a highly seasoned vinegar sauce"
Now, I would never consult a dictionary to determine what constitutes good barbecue, but Webster's is a pretty good authority for language usage, and I think we spend a lot of time arguing over what is and is not "BBQ" when BBQ itself has become (and maybe always was) a fairly generic term.
No, I certainly agree in that a word means what a majority of people say it means. And dictionaries, being descriptivist by nature, reflect how the word is used in the general population. I mean, hell, I say "barbecue" when I mean "grill" sometimes because that's just how we talk in Chicago. "We're gonna have a barbecue" means a cook-out around here, generally.
However, it is always a question of "know your audience." Within a group of food specialists, I would expect the term "barbecue" to be used more precisely. There are many words which have a narrower definition when used by certain groups of people. I think in a food forum, it is certainly useful to keep such distinctions to avoid confusion. I also think, personally, that in the restaurant industry in general, it would be great if barbecue kept the more narrow definition simply because it's more informative to me than the expansive definition. As it stands, I have to ask someone when they've had "great barbecue ribs" whether they mean a) grilled ribs, b) braised ribs slathered in barbecue sauce, or c) slow cooked, wood-smoked ribs.
But, hey, that's language. I'm not about to try to change it.