A Good Example of Semantic Inconsistency by David Loshin.
You can guide users through the intellectual minefield of Frege, Peirce, Russell, Carnap, Sowa and others to illustrate the need for topic maps, with stunning (as in daunting) graphics.
Or, you can use David’s story:
I was at an event a few weeks back talking about data governance, and a number of the attendees were from technology or software companies. I used the term “semantic inconsistency” and one of the attendees asked me to provide an example of what I meant.
Since we had been discussing customers, I thought about it for a second and then asked him what his definition was of a customer. He said that a customer was someone who had paid the company money for one of their products. I then asked if anyone in the audience was on the support team, and one person raised his hand. I asked him for a definition, and he said that a customer is someone to whom they provide support.
I then posed this scenario: the company issued a 30-day evaluation license to a prospect with full support privileges. Since the prospect had not paid any money for the product, according to the first definition that individual was not a customer. However, since that individual was provided full support privileges, according to the second definition that individual was a customer.
Within each silo, the associated definition is sound, but the underlying data sets are not compatible. An attempt to extract the two customer lists and merge them together into a single list will lead to inconsistent results. This may be even worse if separate agreements dictate how long a purchaser is granted full support privileges – this may lead to many inconsistencies across those two data sets.
Illustrating “semantic inconsistency,” one story at a time.
What’s your 250 – 300 word semantic inconsistency story?
PS: David also points to webinar that will be of interest. Visit his post.
[…] “…single version of the customer…” I think of David Loshin’s “A Good Example of Semantic Inconsistency” (my pointer with […]
Pingback by Matching MDM with Hadoop: Think of the Possibilities [Danger! Danger! Will Robinson!] « Another Word For It — November 9, 2012 @ 4:08 pm