Sections 7.3.2 and 18.4 require that a type from another schema can only be used when the other schema has been "merged" into the current schema.
This is overly restrictive. Reusing a single model element from another schema should not force to include all model elements from that schema.
Ralf is putting together a proposal to address the following issues at the Zurich Face to Face:
-
ODATA-180: Remove Extends attribute from EntityContainer element [Open]-
ODATA-181: Referencing/reusing a model element from a different schema does not require to "include" this schema via a Using element [Open]-
ODATA-193: Allow function imports to return entities from a different service [Open]-
ODATA-195: Simplify entity set qualification rules for NavigationPropertyBinding [Open]