Thanks for sharing your thoughts! You are absolutely right—Foundry has so many powerful strengths beyond just the Ontology.
However, as Denis touched upon earlier, I am still looking for answers to a more fundamental question. Ultimately, it boils down to: “What truly is the Ontology, and how should we architect it?”
Most companies adopting Foundry likely already have established, in-house data platforms. In my view, what they expect from Foundry is the ability to integrate disparate data sources and transform them into a unified Ontology to drive better, data-driven decision-making.
From this perspective, advice like “just start building and you’ll eventually get a feel for the Ontology” doesn’t quite resonate with me. Simply configuring an Ontology to fit a single use case or to build a workshop demo feels insufficient.
That is why I want to dive deeper into the experience of senior developers who have been in the trenches. I would love to discuss:
-
How you actually integrate legacy data systems into a unified Ontology.
-
Why it must be the Ontology (the core value proposition).
-
The tangible benefits and advantages you have experienced firsthand through this architectural shift.