howto map/rename element names in xslt

[pintihar]

I am trying to map external xml documents to a class in dotnet.
The problem is that the elements of the input xml will have different
names than the properties of the class.
How do I create the xslt that will allow me to transform the inbound
xml into another xml resource with the elements renamed so that I can
serialize it to an instance of the class.

I assume that this is best done with xslt.transform, but I am not sure
how to write the xslt.

<?xml version="1.0" standalone="yes"?>
<NewDataSet>
<Customer>
<nameFirst>Joe</nameFirst>
<nameLast>Schmoe</nameLast>
<addrCity>Bigtime</addrCity>
<addrState>NY</addrState>
<addrStreet>100 E Main Street</addrStreet>
<addrZIP>100014</addrZIP>
<otherfield>25</otherfield>
</Customer>
</NewDataSet>

public class Cust
{
public Cust()
{ }
public string FirstName;
public string LastName;
public string City;
public string State;
public string Zip;
}
Thanks,
Pint

[Derek Harmon]

Start with the root node, and progressively apply XSLT template rules
for each successive level of depth. The select and match attribute
values you will use will refer to element names from the original
source document. Conversely, the literal content that your tem-
plates emit into the target document will refer to the renamed
elements.

- - - Rename.xsl (excerpt)
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" />
<xsl:template match="/" >
<xsl:apply-templates select="./NewDataSet" />
</xsl:template>
<xsl:template match="NewDataSet" >
<xsl:apply-templates select="./Customer" />
</xsl:template>
<xsl:template match="Customer">
<!-- Observe, the template @match value is the source element name,
the literal element content below is the renamed element name. -->
<Cust>
<!-- Observe, the apply-templates (as in the corresponding template
@match below) refers to the source element name. -->
<xsl:apply-templates select="nameFirst" />
<!-- An xsl:apply-templates for each of the other child elements of
Customer in the source document would appear here, left as an
exercise for the reader. -->
</Cust>
</xsl:template>
<xsl:template match="nameFirst">
<FirstName>
<xsl:value-of select="text()" />
</FirstName>
</xsl:template>
<!-- The remaining template rules are left as an exercise for the reader. -->
- - -

Precise matching of the XmlSerializer output would also depend upon
any System.Xml.Serialization namespace attributes (metadata) that
have been associated with the C# class. These weren't shown, so
the above transform presumes elements with simple text content.
Derek Harmon

[pintihar]

>Start with the root node, and progressively apply XSLT template rules

for each successive level of depth. The select and match attribute
values you will use will refer to element names from the original
source document. Conversely, the literal content that your tem-
plates emit into the target document will refer to the renamed
elements.

- - - Rename.xsl (excerpt)
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" />
<xsl:template match="/" >
<xsl:apply-templates select="./NewDataSet" />
</xsl:template>
<xsl:template match="NewDataSet" >
<xsl:apply-templates select="./Customer" />
</xsl:template>
<xsl:template match="Customer">
<!-- Observe, the template @match value is the source element name,
the literal element content below is the renamed element name. -->
<Cust>
<!-- Observe, the apply-templates (as in the corresponding template
@match below) refers to the source element name. -->
<xsl:apply-templates select="nameFirst" />
<!-- An xsl:apply-templates for each of the other child elements of
Customer in the source document would appear here, left as an
exercise for the reader. -->
</Cust>
</xsl:template>
<xsl:template match="nameFirst">
<FirstName>
<xsl:value-of select="text()" />
</FirstName>
</xsl:template>
<!-- The remaining template rules are left as an exercise for the reader. -->
- - -

Precise matching of the XmlSerializer output would also depend upon
any System.Xml.Serialization namespace attributes (metadata) that
have been associated with the C# class. These weren't shown, so
the above transform presumes elements with simple text content.
Derek Harmon

thanks. That was a great help.