See , it says about the contains function: “If the value of $arg2 is the zero-length string, then the function returns true.”. You could however check <xsl:when test=”contains(.”) and not(matches(substring-before(.”),’ ‘)) and not(./@align)”> 3 solved template condition is not matching…
**<?xml version=”1.0″ encoding=”UTF-8″?> <xsl:stylesheet version=”1.0″ xmlns:xsl=””> <xsl:template match=””> <xsl:element name=”document”> <xsl:apply-templates select=”bill”/> </xsl:element> </xsl:template> <xsl:template match=”//docTitle”> <para format=”6655″ loc=”05″> <xsl:apply-templates/> </para> </xsl:template> <xsl:template match=”//officialTitle”> <para format=”66554″ loc=”11″> <xsl:apply-templates/> </para> </xsl:template> <xsl:template match=”//enactingFormula”> <para format=”6501″ loc=”20″> <xsl:apply-templates/> </para> </xsl:template> <xsl:template match=”//section”>…
If I understand correctly your explanation, you want to do something like: XSL 1.0 <xsl:stylesheet version=”1.0″ xmlns:xsl=””> <xsl:output method=”xml” version=”1.0″ encoding=”UTF-8″ indent=”yes”/> <xsl:key name=”cust-by-charge” match=”Customer” use=”chargeto” /> <xsl:template match=”/CustomerRecord”> <Root> <Customer_PO> <xsl:copy-of select=”Customer[count(key(‘cust-by-charge’, chargeto)) > 1]”/> </Customer_PO> <Customer_Falty> <xsl:copy-of select=”Customer[count(key(‘cust-by-charge’,…
Here is one approach. You define a key to group your items you are looking to remove. I think you are grouping by the @id attribute of the element, together with the @id attribute of the two parent nodes <xsl:key…
You need an identity transformation template: <xsl:template match=”@*|node()”> <xsl:copy> <xsl:apply-templates select=”@*|node()”/> </xsl:copy> </xsl:template> plus a template for the name tag: <xsl:template match=”name[not(node())]”> <name>UNK</name> </xsl:template> Wrap this within the stylesheet tag, and add an xml header: <?xml version=”1.0″ encoding=”ISO-8859-1″?> <xsl:stylesheet version=”1.0″…
As far as I remember loadXML takes a string with the XML. If you have a file or URL to parse use the load method. 1 solved XML to XML XSLT transformation. MSXML in VBScript
I don’t think you need grouping for your Alert issues. It looks like you simply want to output Alert issues which are referenced by “Item/Issue” records. So, what you can do, is define a key like to look up “Item/Issue”…
XSLT based solution. Input XML <config> <connection port=”4404″ type=”tcp”> <selection name=”test-mode” enabled=”true”/> </connection> <connection port=”4405″ type=”tcp”> <selection name=”test-mode” enabled=”true”/> </connection> <connection port=”4406″ type=”tcp”> <selection name=”test-mode” enabled=”true”/> </connection> <option> <maxNumberOfDownloads>10</maxNumberOfDownloads> </option> </config> XSLT <?xml version=”1.0″?> <xsl:stylesheet version=”1.0″ xmlns:xsl=””> <xsl:output method=”xml” encoding=”utf-8″…
Is XSLT the right choice to interpret CDATA in a certain way and write to a file? Yes, CDATA is just a (part of a) text node and is processed as any other text node. Yes, the XSLT 2.0 xsl:result-document…
This is a pretty straightforward grouping problem. If you’re limited to XSLT 1.0, you need to use Muenchian Grouping. If you’re using XSLT 2.0+, you can use xsl:for-each-group. Examples… XSLT 1.0 <xsl:stylesheet version=”1.0″ xmlns:xsl=””> <xsl:output indent=”yes”/> <xsl:strip-space elements=”*”/> <xsl:key name=”class”…
You can find the XML Schema for Schemas here. However, you probably do not need it unless you’re trying to validate an XSD (as opposed to validating an XML document instance with against an XSD). See also: xmlns, xmlns:xsi, xsi:schemaLocation,…
I couldn’t quite work out your logic but I think you may benefit from using a key here to look up the SecDef element using its MktSegGrp attribute value <xsl:key name=”MktSeg” match=”SecDef” use=”MktSegGrp/@MktSegID” /> So, for a given MktDef, you…
There are a few things incorrect with your XSLT: It is trying to replace the whole ‘use’ element with an attribute. You are using two pairs of quotes around $blue, which causes it to be treated as a string. You…
This XSLT will do the thing: <xsl:stylesheet xmlns:xsl=”” xmlns:x=”” xmlns=”” exclude-result-prefixes=”x” version=”1.0″> <xsl:output indent=”yes” method=”xml” /> <xsl:template match=”x:Standards”> <Standards namespace=”{namespace-uri()}”> <xsl:apply-templates select=”.//x:Standard” /> </Standards> </xsl:template> <xsl:template match=”x:Standard”> <Standard> <xsl:copy-of select=”x:ProductID” /> <xsl:copy-of select=”x:Prefix”/> <xsl:copy-of select=”x:SNumber”/> <RelatedProducts> <xsl:apply-templates select=”.//x:RelatedProduct”/> </RelatedProducts> <xsl:copy-of…
Just as a different approach and also handling the colours for the same bus_types.Demo <?xml version=”1.0″?> <xsl:stylesheet xmlns:xsl=”” version=”1.0″> <xsl:output method=”html”/> <xsl:template match=””> <table> <tr> <td colspan=”9″>ACME BUS SERVICE</td> </tr> <tr> <td colspan=”9″> Month: <xsl:value-of select=”//Month”/> </td> </tr> <tr> <td>Season</td>…