I have previously written about the lack of a common upper ontology in the semantic web and commercial software markets (e.g., business rules). For example, the lack of understanding of time limits the intelligence and ease of use of software in business process management (BPM) and complex event processing (CEP). The lack of understanding of money limits the intelligence and utility of business rules management systems (BRMS) in financial services and the capital markets. and in enterprise decision management (EDM). And, more fundamentally, understanding time and money (among other things, such as location, which includes distance) requires a core understanding of amounts.
- Understanding events and processes takes time
- Oracle should teach Siebel CRM about location and money
- Ontology of time in progress – amounts needed
The core principle here is that software needs to have a common core of understanding that makes sense to most people and across almost every application. These are the concepts of Pareto’s 80/20 Principle. A concept like building could easily be out, but concepts like money and time (and whatever it takes to really understand money and time) are in. Location, including distance, is in. Luminousity could be out, but probably not if color is in. Charge and current could be out, but not if electricity or magnetism is in. The cutoff is less scientific than practical, but what is in has to be deeply consistent and completely rational (i.e., logically rigorous). (more…)