concept knowledge in category data

This is an excerpt from Manning's book The Art of Data Usability.
The thing is, even if we’re working with data we’re not aiming only for data quality, we’re aiming for more. In addition to ensuring the quality of the data itself, we also need to ensure the quality of transformed data and the interpretations of data. Ultimately, we’re trying to generate good knowledge. If the knowledge we have is of good quality, we’ll be able to make better decisions or you could say we become wiser. That’s what we’re trying to achieve, so how do we get from data to wisdom?

This is an excerpt from Manning's book Think Like a Data Scientist: Tackle the data science process step-by-step.
Knowledge, technology, and opinions are typically what you have at the beginning of any project; they are the three things that turn data into answers. Knowledge is what you know for a fact. Technology is the set of tools you have at your disposal. Opinions are those little almost facts you want to consider true but shouldn’t quite yet. It’s important to establish a hierarchy for your thought processes so that less-important things don’t steamroll more-important ones because they’re easier or more popular or because someone has a hunch.
Expectations can come from almost anywhere. Some are hopes and dreams, and others are drawn from experience or knowledge of similar projects. But a typical discussion of expectations boils down to two sides: what the customer wants versus what the data scientist thinks is possible. This could be described as wishes versus pragmatism, with the customer describing their desires and the data scientist approving, rejecting, or qualifying each one based on apparent feasibility. On the other hand, if you’d like to think of yourself, the data scientist, as a genie, a granter of wishes, you wouldn’t be the only one to do so!