The document discusses semantic gaps that occur in multi-domain engineering. It defines a semantic gap as a difference in meaning between constructs formed in different representation systems. Three main semantic gaps are identified: between stakeholders and engineers, within a single engineering domain, and between different engineering domains. The document proposes some methods for bridging these gaps, such as finding analogies, visual representations, and increasing shared understanding through documentation in a standardized language like SysML. It also discusses limitations to fully bridging inter-domain understanding.