Subject: Re: [xsl] priority of key patterns From: Ihe Onwuka <ihe.onwuka@xxxxxxxxx> Date: Wed, 14 Nov 2012 10:59:27 +0000 |
On Wed, Nov 14, 2012 at 10:44 AM, Andrew Welch <andrew.j.welch@xxxxxxxxx> wrote: >>> <xsl:template match="EmployeeCategory | PersonName | FormerlyKnown"> >>> <Name> >>> >> >> I cut the examples off with .... too early. Here are a few more >> illustrating the more general case for which that solution will not >> work. >> >> <ren:element from="Directors" to="Names"/> >> <ren:element from="ParentCompany" to="Names"/> >> <ren:element from="LegalStatusAdditional" to="AdditionalInfo"/> >> <ren:element from="EmployeeChanges" to="Changes"/> > > ...just add more templates!?! > I think it is better to achieve it by adding data (which is what that variable is).
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] priority of key patterns, Andrew Welch | Thread | Re: [xsl] priority of key patterns, Ihe Onwuka |
Re: [xsl] priority of key patterns, Andrew Welch | Date | Re: [xsl] priority of key patterns, Ihe Onwuka |
Month |