Subject: Re: [xsl] Finding another element with the same name as the current node From: Jeni Tennison <mail@xxxxxxxxxxxxxxxx> Date: Sat, 3 Feb 2001 10:13:42 +0000 |
Mike Kay wrote: > Ooh, a rare mistake from Jeni, I can't resist leaping in with a correction! Oh... piffle. Thanks Mike :) > name() returns a QName for the node, not an expanded name. An > expanded name consists of a (namespace URI, local name) pair, and > there is no defined way of expressing an expanded name as a string. I'm sure there used to be a proposal to represent it as: {http://www.foo.com/}:doc Or something similar? Probably in one of the XML Namespaces Working Drafts. > A QName has the form [prefix:]local-name; the prefix will be one > that corresponds to the namespace URI, which usually means it will > be the same prefix as you used in your source document. That 'usually' got me wondering. When might it not? Well, when you've got multiple namespace declarations for the namespace, the processor could use any one of the prefixes that are defined. In tests, 3 out of 3 processors (MSXML, Saxon and Xalan) use the same prefix as used in the source document, even if there are multiple namespace declarations for the URI, and even if one of those declarations is the default namespace. Does anyone know of any processors that don't? Cheers, Jeni --- Jeni Tennison http://www.jenitennison.com/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Can I use XSL to output m, Michael Beddow | Thread | RE: [xsl] Finding another element w, Michael Kay |
Re: [xsl] different first page usin, Nikolai Grigoriev | Date | Re: [xsl] Javascript Function with , Jeni Tennison |
Month |