I wrote a generic custom Xslt for mapping html form input from the HTTP Adapter. It also requires an extension Xml file for the System.Web.HttpUtility dll
[code:1:d1601e74ca]<?xml version=\"1.0\" encoding=\"UTF-16\"?>
<xsl:stylesheet xmlns:xsl=\"http://www.w3.org/1999/XSL/Transform\"
xmlns:msxsl=\"urn:schemas-microsoft-com:xslt\"
xmlns:var=\"http://schemas.microsoft.com/BizTalk/2003/var\"
xmlns:SystemWebHttpUtility=\"http://schemas.microsoft.com/BizTalk/2003/System.Web\"
xmlns:s0=\"urn:schemas-tkh-co-nz:htmlform-flatfile\"
xmlns:ns0=\"urn:schemas-tkh-co-nz:htmlform-xmldefault\"
exclude-result-prefixes=\"msxsl var s0 SystemWebHttpUtility\"
version=\"1.0\" >
<xsl:output omit-xml-declaration=\"yes\" version=\"1.0\" method=\"xml\" />
<xsl:template match=\"/\">
<xsl:element name=\"ns0:htmlform\">
<xsl:for-each select=\"//field[name != ‘Submit’]\">
<xsl:variable name=\"var:v1\" select=\"name\" />
<xsl:element name=\"{$var:v1}\">
<xsl:value-of select=\"SystemWebHttpUtility:UrlDecode(string(value))\"/>
</xsl:element>
</xsl:for-each>
</xsl:element>
</xsl:template>
</xsl:stylesheet>[/code:1:d1601e74ca]
This map shows host to create a tag name from data using {$var:v1}. However I suspect your case is not so generic. This blog shows you how to use the Source Link property within the mapper to map name/value pairs.
[url]http://geekswithblogs.net/benny/archive/2006/02/06/68382.aspx[/url]