Jason Greene wrote:
IMO something other than the MDR should be created/used to achieve this. The MDR's design is in many ways incompatible with what we actually want for a domain model. As an example, the notion of scoping is the exact opposite of how an administrator expects the domain.xml to work. An entry in the domain should *override* something expressed in a deployment, not the other way around.
Yes, i was not really referring to the MDR - rather to a general concept of a meta data repository, since MDR does not really fit the needs of the domain metadata. Where we create a more generic way of handling domain metadata entries within ProfileService.