Assume you define the Data Domains in such a way that you allow the organization to manage data autonomously with the least coupling with other Data Domains. The definition of these Data Domains are driven by Bounded Context (inspired from Domain-driven Design and Data Mesh).
Finance talks about Customer, from his own perspective. Marketing talks about Customer from another perspective.
Nevertheless, they both want to define the Business Term "Customer" that is very own to each Data Domain. Note that it means that there are two Business Terms with identical key: the name Customer
My question: Can both Data Domains define Customer and make it unique by the relationship to Data Domain?Precisely's answer is: Have a naming convention in the name of your Business Term.
I don't believe that a naming convention helps.
Why? Bad Data User Experience (DUX)
It is confusing.
It makes things difficult, instead of simple.
It increases the hurdles of adopting Data Governance even higher.
@Sam Darmo logged an enhancement request via an Idea here:Assets with the same name but belonging to different | Precisely Ideas