[
Lists Home |
Date Index |
Thread Index
]
Richard Tobin wrote:
>
> >> <xsl:template match="x:child">
> >>
> >> The parser doesn't know that x:child is going to be interpreted as a
> >> QName; it can't distinguish it from something like:
> >>
> >> <db:read file="c:mydatabase">
> >>
> >> Only the XSLT processor knows what the attribute means.
>
> >Since it knows that as soon as the element tag has been parsed, it could
> >well act on that knowledge and discard it.
>
> I can't follow that - too many "it"s. What knows what as soon as the
> element tag has been parsed?
In the cited passage, "the XSLT processor".
> The parser knows nothing about what the
> attribute means. [The parser] has to pass the downstream processor both the
> attribute value and the namespace map, so that the downstream
> processor can interpret the attribute (or part of [the attribute]) as a QName if
> [the downstream processor] wants to. The downstream processor can discard the map
> if [the downstream processor] doesn't need [the map], or once [the downstream
> processor has] interpreted the element. But as long as the document is passed on,
> the namespace bindings have to be preserved.
The last assertion confuses me. Where all qualified names have been
interpreted, that is, where "[the downstream processor has] interpreted
the element", what does a relation between prefixes and namespace names mean?
>
> -- Richard
>
|
