=?utf-8?B?UkU6IFt4bWwtZGV2XSBXaGVyZSBoYXZlIHRoZSBlbGVtZW50IHR5?==?utf-8?B?cGVzIGdvbmU/?=

[=?utf-8?B?SmVmZiBMb3dlcnk=?= <jlowery@scenicsoft.com>]

The point I would make is that schema types give one the freedom to name
their element according to semantic context, while allowing said elements to
be processed as the same definitional type. Fer instance:


<rectangle>
	<vertices>
		<upperRight>23 34</upperRight>
		<lowerLeft>11 44</lowerLeft>
	</vertices>
</rectangles>

<peanuts>
	<count>2</count>
</peanuts>

Here, all numbers can be processed as positiveInteger types instance (or
lists thereof), regardless of context. On the other hand, the application
can attach different semantic meaning to the data represented by those typed
values. I can separate the validation of the type from it's meaning in a
particular context.