> I think 
> you're looking for something more, which is for the component 
> such as a complexType resulting from a given source level 
> declaration in a schema document to have the same validation 
> semantics regardless of the larger schema in which it's employed.

Well, the main thing I'm looking for is conformance with the rule in
XSLT/XQuery which says that a schema component used at query/stylesheet
compilation time must have the same semantics as the same component when
used at run-time. And yes, I'm trying to do this without "freezing" the
whole schema, because XSLT/XQuery also allow new components to appear at
run-time (for example, from xsi:schemaLocation in an instance document
supplied as input to the transformation) that were not known at compile
time. So in this sense you're right: I'm trying to find rules that allow the
schema as a whole to be extended while retaining confidence that the
assumptions I made at query compile time relating to type-safety are still
true when the query is executed. I'm trying to do this by freezing the parts
of the schema on which compiled queries depend.

If one took the "late binding" principle to extremes, then it would be
impossible to do anything useful at query compilation time, which would
obviously be unacceptable. So it's a question of finding the right level of
late binding.

Michael Kay
http://www.saxonica.com/


From mike@s... Tue Apr 10 09:51:17 2007
Received: from li