• From: David Carlisle <davidc@n...>
• To: xml-dev@i...
• Date: Tue, 21 Dec 1999 10:52:31 GMT

Rick,

Perhaps I missed something but I fail to see why your xslt example
shows that prefixes are required.

> In this document, the axsl: element will not be interpreted
> as an XSLT function by an XSL processor: it will be output
> unchanged as
>     <axsl:value-of select="xxx"/>

That is true, but not because it is a different prefix, but because it
is a different namespace.

The expanded form is not

   <(http://www.w3.org/1999/XSL/Transform)value-of select="xxx"/>

that you suggest but rather

   <(http://www.w3.org/1999/XSL/TransformAlias)value-of select="xxx"/>

which is (to the namespace processor parsing the stylesheet) just some
unknown namespace unrelated to XSLT which is why it is a literal result
element not an xsl instruction.

The `magic' aliasing comes later, as result elements in that namespace
are switched to the XSLT namespace as the result tree is written out.


David


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: Re: Request for Discussion: SAX 1.0 in C++
• Next by Date: Re: Representing IP addresses in XML Schema
• Previous by thread: Re: SAX2: summary of Namespace-support arguments
• Next by thread: SAX2: Namespace proposal
• Index(es):
  • Date
  • Thread