[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: xmlns in the root element prevents transformation

Subject: Re: xmlns in the root element prevents transformation
From: "Leo Studer leo.studer@xxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 24 Jul 2020 05:42:10 -0000
Re:  xmlns in the root element prevents transformation
> On 24 Jul 2020, at 00:17, Michael Kay mike@xxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Failing to appreciate the implications of a namespace declaratoin in the
source document is probably the most common source of XSLT questions on
StackOverflow - if you search there for "XSLT default namespace" you will find
at least 600 questions from people who have fallen into this trap. It's
particularly invidious beccause (a) the symptoms of the failure are usually
wrong results rather than any kind of error, and there's nothing in the wrong
results that hints at a namespace problem, and (b) many people try to pick up
XSLT from very elementary tutorials that only handle the simplest of
constructs, and leave out any discussion of namespaces as if they are somehow
an advanced feature that you don't need to worry about until later.
>
> It's also invidious because although the problem was recognised very early
on, it's proved impossible to fix without creating backwards compability
problems. The xpath-default-namespace attribute in XSLT 2.0 helps, but only if
you know what the problem is and know that you need to use it. In Saxon I've
been experimenting with another solution, which is for bare unqualified names
in the stylesheet to match elements in any namespace or none - but for
conformance reasons, that option can't be the default, so beginners still fall
straight into the trap. I've also tried heuristics that attempt to detect when
users are falling into the trap (specifically, when a namespace is used in the
source document and isn't declared in the stylesheet) but I fear that users
who don't even know that these peculiar xmlns things are called namespaces
find the message incomprehensible and ignore it.
>
> If the source document has a namespace declaration then it changes the names
of the elements, and if your stylesheet is trying to match elements by name
then they won't match unless you get the namespace right. So understanding
this is absolutely fundamental.
>
> Michael Kay
> Saxonica
>


Thanks Michael, a suitable error message would be highly appreciated ;-

Cheers
Leo

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.