[
Lists Home |
Date Index |
Thread Index
]
> Since this is compile-time assessment of the expressions in the
> stylesheet, I think that the answer is to not import a schema to the
> stylesheet in the first place,
Well yes, but that answer's the same as Jonathan's. If someone argues
that supporting schema complex types, bloats the spec, complicates the
use of the language, and provides lots of undesirable side effects.
Being told that you can use Xpath/XSLT without using that feature is
I suppose better than nothing, but hardly a justification for the schema
complex type support being there in the first place.
> I can't see anything in the XSLT 2.0 WD that says that, during
> compilation, it will access a particular instance document's schema
> and use that to optimise queries.
Neither could I actually, but this so far has been the only
justification offered for the provision of strong typing based on schema
complex types, so if it is Xquery only, what's it doing in Xpath?
> If a processor substituted aaa/bbb for the empty sequence on
> the assumption that the source document was completely valid, there
> would be a rather strange situation where the data model contained an
> element that was inaccessible from the stylesheet.
You say it's strange, and I agree, but neither of us are on the WG,
It's hard to understand how the argument that the type system allows
compile time optimisation (if it is true) can fail to lead to this
strange situation.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
|
