[sv-bc] typedefs in separate compilation units

It seems that the definition of type compatibility does not 
consider the practical case of separate compilation units.
 
Consider a global typedef declared at the compilation unit scope.
 
Consider the same exact global typedef declared in another compilation unit.
 
The design brings these two compilation units together.
 
I think it is the user intent that these types be compatible such that
ports connecting objects of these types are legal and assignment of values
of objects of these types are also legal.
Is that not the case?
 
Francoise
       '