We currently refer to our conceptual data modelling as "data product design". When I run those conceptual modelling sessions, I very deliberately avoid the terms fact and dimension (even though our conceptual models are ultimately high level star schemas). I often use the work entity as a substitute for dimension, but I think I prefer your term of concept and detail. Event as fact makes sense to me.
Imagine us in Europe where we also have to switch to the local languages. It's a mess! :D
I struggle enough translating data speak to business speak.
I don't know how you do it when you are also translating between more than one human dialect.
I always wondered if it made it easier for you because you are natively bilingual or harder?
We currently refer to our conceptual data modelling as "data product design". When I run those conceptual modelling sessions, I very deliberately avoid the terms fact and dimension (even though our conceptual models are ultimately high level star schemas). I often use the work entity as a substitute for dimension, but I think I prefer your term of concept and detail. Event as fact makes sense to me.
I have tested Concept and Detail enough to be confident to say they work.
But open to a better term for Events.