The affiliationType is global. The <organization> element, e.g., defined
within the content model of affiliationType is local. The type of
<organization> could very well be globally defined in MSTL (and should
be, IMO, and unified with the types of every other corporate entity in


>>> [log in to unmask] 01/26/05 10:30 AM >>>
Isn't the whole point of a type library that the definitions are
global?  Not a rhetorical question exactly; I just can't see the logic
of this restriction.

Clearly you don't want people to be able to *use* the same definitions
in the same context, but to not even allow them to be defined just
seems silly.