So doesn't this mean that the xsl processor also needs to do some
normalising (based on declared namespaces) before it begins processing? Its
the same problem, just different code.

As I understand this, the process is to effectively state "I want namespace
xxxxxxxxxxxx to map to prefix yy:" so you can go ahead and refer to things
with this prefix in your program.

I suppose the real clash is when multiple things need the xml normalised to
use different prefixes at the same time (xsl and perl program).

Brian

-----Original Message-----
From: Eric Bohlman [mailto:ebohlman@[...].net]
Sent: Wednesday, 9 October 2002 14:26
To: perl-xml
Subject: Re: RE: What's So Great about SAX? (ie. Future Indecisions)


10/8/02 3:39:09 PM, "Grant McLean" <gmclean@[...].biz>  wrote:

> Can you give an example of the 'QNames in content' phenomenon?
> (I'm not trying to propose a fix, I'd just like to understand the
> problem better).

<xsl:value-of select="article/dc:date"/> 

That's the most common sort of case: a QName appears in an XPath expression
in the content of an 
attribute or text node.  The namespace prefix ("dc" in this case) is
"hard-wired" into the 
expression, and it won't match date nodes that don't have a "dc" prefix even
if they're definitely 
in the Dublin Core namespace by defaulting or another prefix.



_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs