Subject:copy-namespaces mode Author:Hans-Juergen Rennau Date:01 Nov 2006 07:26 PM
Hello,
does the stylus XQuery processor implement the copy-namespaces mode strictly according to the W3C recommendation? It seems to me - not quite, at least as far as document constructors are concerned. The query
Or is this to be explained by a serialization process which strives to place namespace declaration attributes intelligently, though not warranted by the actual in-scope namespaces?
The example looks strained, but I want to know exactly what the processor does, rather than guess.
Subject:Re: copy-namespaces mode Author:(Deleted User) Date:02 Nov 2006 06:00 AM
Hi Hans-Juergen,
it looks you have found a bug in the XQuery processor: the
construction of document nodes ignores the copy-namespace directive.
You will get the same results of Saxon if you wrap that node in
another element, e.g.
Subject:copy-namespaces mode Author:Hans-Juergen Rennau Date:05 Nov 2006 06:27 PM
Hello Alberto,
thank you very much for the prompt information!
Unfortunately, I did not quite understand your remark about Saxon, related to the example you gave. At any rate, trying out your example with Saxon (as well as with the built-in processor), I got the correct results, or so it seemed to me. If you wanted to point out something else, it would be kind to let me know.
Subject:copy-namespaces mode Author:(Deleted User) Date:06 Nov 2006 03:14 AM
Hi Hans-Juergen,
I'm sorry my remark was not clear; I was trying to say that both processors (Stylus and Saxon) return the same result if the <a> element is a children of another element, instead of a children of a document node.
Alternatively, it means that Stylus does support the copy-namespace property, but there was a bug when document nodes were involved.