I dont want to put all the modeling disciplines into the information modeling (as sub-domains) just because most of these are somehow related to information modeling, or just because we can view any modeling activity itself as information processing activity.
For me information modeling is part of the larger domain of modeling the structural aspects of the domains or systems, and answers in this context to the following questions:
- What information we capture (represent) about particular domain here information model should have the connection to the domain model, which itself answers to the question what the domain is and gives the semantics (meaning) to the information model elements.
- What information we capture (represent) for a particular purpose here information model should have the connection to the behavioral models (use-case, process, state-transition, etc. models) of either the domain or the system under study, to show for what and how the information model elements are used.
- What are the formal rules for assessing the quality of information (for given purpose) here information model should have the connection to the domain model constraints for static or structural rules, and connection to the behavioral models for dynamic and context sensitive rules.
It is important to have in mind that because different modeling disciplines cover different aspects of the system under study, we get the full holistic picture only by applying several modeling disciplines, not by putting one discipline above others real world systems have both structure and behavior at the same time.
That is why I would like to see that neither information owner nor process owner are ruling over each other in information or process governance the governance should be set over full picture that describes all aspects of given domain or system (EA in case the system is the enterprise).
To achieve the consistency, stability and encapsulation, there is no need to try to establish global governance over all levels, just higher level composition owner should govern the interfaces (incl. both structure and behavior) between the next level components doing so we are able to partition the models to fight the complexity, and allow freedom of development/governance inside the components.