Very nicely explained. But the position of Semantic layer is different or conflicts with one of the article"Semantics and Data Product Enablement". In the other post, semantic layer is between Physical and Data Product. Can you clear my doubt?
Chicken & Egg situation? I expect Data Products to inform the Semantic Layer but also that new Data Products could be informed by the Semantic Layer; so rather than above or below but to the side?
Thanks for sharing - echos quite a few thought's I've had on this topic recently. As someone who build a lot of Business Objects universes' early in my career, I always felt the BI semantic layer was wasted on only being able to integrate with the single BI tool. Having a Semantic layer than can be consumer by any tooling will increase data adoption and drive consistency.
What are people using to building 'The Semantic layer you talk about' today?
Very nicely explained. But the position of Semantic layer is different or conflicts with one of the article"Semantics and Data Product Enablement". In the other post, semantic layer is between Physical and Data Product. Can you clear my doubt?
Chicken & Egg situation? I expect Data Products to inform the Semantic Layer but also that new Data Products could be informed by the Semantic Layer; so rather than above or below but to the side?
Thanks for sharing - echos quite a few thought's I've had on this topic recently. As someone who build a lot of Business Objects universes' early in my career, I always felt the BI semantic layer was wasted on only being able to integrate with the single BI tool. Having a Semantic layer than can be consumer by any tooling will increase data adoption and drive consistency.
What are people using to building 'The Semantic layer you talk about' today?
I was messing around with this to look at solving
https://github.com/mpearmain/meshposure