• ⌂
  • News
    • Events
    • Blog
    • Subscribe
    • Product Updates
  • Products
    • Modeler
    • Manager
    • Portal
    • Freestyle
    • Canvases
    • 2022-05-04-16-00-58
    • License
    • Features
    • Pricing
    • Shop ...
  • Downloads
    • Download
    • Model Files
    • How-to Install ...
  • Articles
    • About FCO-IM
    • Gentle Introductions
    • Architecture
    • Solutions
    • Examples
    • 2016-01-27-14-22-32 (3)
    • Presentations
    • Videos
    • Cartoons
  • Support
    • Documentation ...
    • Tickets ...
    • Training
    • Books
  • About
    • The Team
    • The Community
    • The Customers
    • The Company
    • 2016-01-27-14-22-32 (2)
    • LinkedIn...
    • 2016-01-27-14-22-32
    • Privacy
    • Disclaimer
  • Sign Up
  • Login

blog

What We Lost When We Fed the Machine

We ask AI to find meaning in our data — but the authentic story was gone before it ever looked


In What We Lost When Datum Became Data, I traced how a word that once meant "something given" shed its own etymology and became a synonym for "values in a system." Along the way, the who, the why, and the context quietly disappeared. I used the Groningen definition, the Employee-Person example, and the metadata stack to show where those losses happen.

That argument had its own reasons. It has sharper ones now.

Read more …

What we lost when Datum became Data

On etymology, semantic drift, and why the words we choose for data shape the systems we build

A Word That Carried Its Own Philosophy

In Dutch, the everyday word for data is gegevens. It is not a technical term. Any citizen uses it naturally, without a second thought. And yet it encodes something profound: gegevens are things given — handed over, recorded, established by someone, for someone, with intent.

The English word 'data' has the same Latin root. Datum means 'something given'. But that etymology is effectively dead in English practice. Nobody says "one datum" anymore. Nobody asks "given by whom, for what?" The word has shed its own origin.

What remained is a term that implies objectivity, neutrality, and independence from any observer. Data just exists. It is out there. You collect it, store it, analyse it. The act of creation — the who, the why, the context — has quietly disappeared.

That disappearance has consequences.

Read more …

The Void That Thinks

What Ancient Wisdom Teaches Us About Working With AI

The Oldest Observation

Ancient Hebrew texts describe the moment before creation as tohu va-vohu — formless and void. Not empty in a trivial sense, but charged with potential. What is striking is not the nothingness itself, but that it was considered real enough to name, to describe, and to stand in relation to.

The Kabbalistic tradition deepens this with Ayin — the nothingness that precedes all being. The void is not the absence of reality. It is a different kind of reality.

Now consider your own experience of not knowing something. It is not a blank. It has texture. It draws you toward it. You can dwell inside it, sit with it, let it work on you. Unknowing is not the opposite of knowing — it is a generative state, a threshold, a beginning.

This is a profoundly human capacity. And it is precisely what AI cannot do.

Understanding the difference — and learning to use it deliberately — will make you a better user of AI, and a better information modeler.

..you can inhabit it. And when you do, you change what AI can do for you..

Read more …

  1. Against the stream
  2. FCO-IM Is Not Telling You What to Build
  3. The Data That Doesn't Know What It Means
  4. Bridging the Gap
  5. FCO-IM Changes the Conversation
  6. Understanding Modeling Terminology
  7. AI Needs More Than a Glossary
  8. Understanding before Data
  9. Beyond the Technical
  10. Data Explorer
  11. The Illusion of 'Data-Driven'
  12. Population on a Map
  13. SIG 2024
  14. Pilot FOM in Rotterdam
  15. Modeling Entities
  16. CaseTalk Bookmarks
  17. Python DataClass
  18. Legal Articles and Information
  19. Story telling
  20. DotRunner (Free)
  21. Event Modeling
  22. Puppy Tricks
  23. Abstract Model
  24. The why and how
  25. CaseTalk partners HvA, HR and HU
  26. Congratulations!
  27. Entities from thin air
  28. Data Vault Coloring
  29. Concepts and Containers
  30. Temporal, Transitional and Localization Annotations
  31. Bi-Weekly Ticket Newsletter
  32. Congratulations!
  33. Security by design
  34. Data Centricity
  35. Use Case - ProRail
  36. Computable Award 2007 [NL]
  37. Type level modeling is (too) easy
  38. Generic "Customer"
  39. Temporal & Transitional Modeling
  40. GDPR by design
  41. Wikipedia
  42. Add language, add knowledge
  43. Presenting the new FCO-IM Book
  44. Arriving for DMZ 2015
  45. Ready for DMZ
  46. Killing three birds with one stone
  47. Fresh supply of FCO-IM Books
  48. Guido Bakema to be ambassador for CaseTalk
  49. Share your work
  50. Cooperation HAN and ICT-companies
  51. Cooperation HAN and BCP Software
  52. Cooperation Four Points and BCP Software

CaseTalk

We make IT better. Together!
 
CaseTalk Modeler
casetalk devices Download 14.4.0windows 10
CaseTalk FreeStyle
casetalk freestyle
Try Online
Canvas Helpers
casetalk freestyleUse Online

Scheduled

  • 3 days - Fact Based Modeling with CaseTalk
    July 1, 2026 9:00 am

Releases

  • CaseTalk 14.4.0
  • CaseTalk 14.3.2
  • CaseTalk 14.3.1
  • CaseTalk 14.2.2
  • CaseTalk 14.1
  • CaseTalk 14.0

Share

For You

For Managers

For Architects

For Analysts

For Developers

Solutions

Fact Oriented Modeling

Ontology & Knowledge Graphs

Taxonomy & Glossary

Natural Language

Products

CaseTalk Modeler

CaseTalk Manager

CaseTalk Portal

Editions & Licensing

Resources

Downloads

Documentation

Training

Contact Us