Lists Home |
Date Index |
"David G. Durand" wrote:
> James seems to be asking for a some kind of a static type guarantee,
> where it would be impossible to write an XSLT stylesheet that
> produced a namespace error. Or where, at least, XSLT could be asked
> to automatically ensure that its output would have all needed
> namespace declarations, and the transform writer could be completely
> unaware of the machinery of prefixes, etc.
especially since one would think a guarantee can be provided where the
transformation is defined in terms of operations which close over
semantic domains, while it cannot be done where the transformation is
defined in terms of syntactic domains. (cf. the unescaped markup "holes"
below and the notion that prefixes are markup.)
> This would be useful, but unless optional, it would make it harder
> for people to create stylesheets that produce non-namespaced,
i don't see why this is harder. please give an example. i would have
thought that the abstract syntax of such documents could be defined such
that all names not in any namespace were actually in a distinguished
> or non-xml results.
i am unaware of this issue and would appreciate examples.
> There are even bigger holes in the XSLT type system, such as the
> ability to emit unescaped markup -- of course those are intended to
> solve tough problems (or enable quick hacks, depending on your
> perspective), and so their use is quite clearly marked.