I have no problem with changing the words AS LONG AS the replacements are as accurate and unambiguous as the originals.
As to Bob's definition, where does one stop. Since one of the old time mantras for CM was that it helped you "deliver a correct product, on time and within budget."
So, how about we add Accounting (money) within the cadre of Bob's subfunctions. We have to plan and allocate CM resources. Maybe we should add Recruiting.
The point is, "Where do we stop."
The real problem however is less a matter of adding functions to the definition/description of the CM discipline than one of watering down the definition/description!
First and foremost, project managers and clients (especially U.S. Government clients) typically want a quick and dirty. So, the contractor gives them what they ask for, as in, "Yes, we'll provide CM services. We will track versions of all documents and files." Even worse?--"Our CM specialist will log all deliverables to make sure you have everything."
Something else I have encountered over the years. Various work groups/roles have very differing ideas on what CM is.
Example: Most programmers...Oops! I'm sorry. Most Software Engineers only see an incoming "Change Request," then check out a file, and check it back in. That is, the "CR," or what is now tantamount to a "work order," has been vetted before the SE's ever see it.
So, to them it is a generic process, rather like the cleaning room of a laundry receiving a ticket to clean, starch, iron, wrap or hang. Then verify that the work has been done.
What they don't see is either the customer, before arriving at the cleaners, or the receptionist at the laundery going through the clothing to determine which pieces to wash, dry and iron, which to dry clean, which to repair first.
It would be very easy for the washing team to get the idea that providing a clothes cleaning service consists only of receiving the work ticket, doing the work, and turning the finished product over to the customer, and tracking the items throughout the process.
As I stated previously, the definition of CM is not a job description. It is the basis of the specialized management subdiscipline that concentrates on the product.
As to the four functions of CM, part of the problem may be that "most" people think of it in linear terms. The CM definition says that these four are the functions that comprise CM. There is nothing that states or implies a sequence. It says simply that these things are/will be done.
As to Bob's definition, four of his six I would put under the function of Configuration Change Control (EIA-649B). One I would not include under CM at all - build is part of production. And I have not a clue as to what the ambiguous term "Environment Configuration" refers -- configuration of the workroom environment, configuration of the natural environment, configuration of the technology environment??
Now, here's the biggest question of all. Which words are "arcane?" I think it is less a matter of being arcane than it is a matter of the words implying something much larger and more complex than most people want to believe. Most are interested only in that portion that directly affects them. Therefore, it is much easier for example, to accept that "CM is version control" than to accept that CM is a discipline comprising all sorts of "stuff" outside their purview that they are not interested in. The result is that the listener doesn't want to hear it and accuses the describer of using "arcane" terminology.
It takes work. If it was easy, we'd be on the dole.