<xsl:template match="Name"> <FullName> <xsl:value-of select="."/> </FullName> </xsl:template> It worked. A tiny, perfect transformation. He felt a jolt of dopamine. He bought the "Advanced XSLT" course as a pre-order, just out of sheer optimism.
His job was to transform this beastly <ShipmentOrder> XML into a flat, friendly <OrderRecord> CSV for an ancient warehouse database. His tool? XSLT. He had a weekend to learn it. udemy xslt
<xsl:template match="hcl:ShipmentOrder"> <xsl:for-each select="hcl:Packages/hcl:Package"> <xsl:value-of select="../../hcl:OrderID"/>, <xsl:value-of select="hcl:TrackingNumber"/>, <xsl:for-each select="hcl:Items/hcl:Item"> <xsl:value-of select="hcl:SKU"/>, <xsl:value-of select="hcl:Qty"/> <xsl:if test="not(position()=last())">|</xsl:if> </xsl:for-each> <xsl:text> </xsl:text> </xsl:for-each> </xsl:template> He was mixing a little imperative (the for-each ) with the declarative, and he didn't care. It was his solution. He bought the "Advanced XSLT" course as a
He wrote a rule:
But by hour three, Alistair introduced <xsl:apply-templates> and the dreaded attribute. Leo’s brain began to short-circuit. The coffee wasn't working. He was staring at a recursive descent through a 5,000-line XML file, trying to flatten a <ShipmentDetails> node that contained nested <Package> elements, which themselves contained <Item> elements, which had attributes like @hazmat="true" . " he said
He fast-forwarded to the lecture. Alistair was holding a whiteboard marker. "Namespaces," he said, "are like the last name of an element. You wouldn't walk into a high school reunion and shout 'Michael!' You'd get twenty Michaels. You need the last name. In XSLT, you must bind the namespace to a prefix, then use the prefix." Leo added xmlns:hcl="urn:healthcare-logistics-45b" to his <xsl:stylesheet> tag. Then he changed his selects to hcl:ShipmentOrder . The data returned like a dam breaking. He had never felt such relief over angle brackets.