Since there is no default namespace defined, the source document's elements
(clients, Title, Surname) have no namespace associated with them.  It
appears that the author of the XSLT is attempting to simply map all
<clients> tag's elements into elements that belong to the http://123.co.uk/
namespace. Perhaps the process using the output of the transformation
expects those particular tags to belong to that namespace (or perhaps they
are defined in a schema with that target namespace).

Mike


"resolutionsnet" <resolutionsnet@d...> wrote in message
news:2E2CD144-CCCA-4E19-92B1-8D751D5E2312@m......
> Can someone help explain what is happening in the below XSLT, in
particular I
> am interested is the namespace usage for xmlns:e and it's use on Title and
> Surname. What is happening here?
>
> Thank you
>
> <?xml version="1.0" encoding="UTF-8" ?>
> <xsl:stylesheet xmlns:xsl='http://www.w3.org/1999/XSL/Transform'
> xmlns:msxsl='urn:schemas-microsoft-com:xslt'
exclude-result-prefixes='msxsl'
> version='1.0' xmlns:e="http://123.co.uk/" >
>
> <xsl:output method='xml' omit-xml-declaration='no' />
> <xsl:template match='/'>
>    <xsl:apply-templates select='clients'/>
> </xsl:template>
>
> <xsl:template match='clients'>
> <client>
>
>    <e:Title><xsl:value-of select='Title/text()'/></e:Title>
>    <e:Surname><xsl:value-of select='Surname/text()'/></e:Surname>
>
> </client>
> </xsl:template>