Conditional Streaming Accumulator in XSLT 3 - xslt-3.0

With input XML like this:
<?xml version="1.0" encoding="UTF-8"?>
<Root>
<Entry>
<Amount>2088</Amount>
<DebitCredit>C</DebitCredit>
</Entry>
<Entry>
<Amount>9074</Amount>
<DebitCredit>D</DebitCredit>
</Entry>
...
</Root>
I'd like to create a streamable transformation with separate accumulators for debits & credits, but when I attempted to create an accumulator for one type or the other similar to this
<xsl:accumulator name="debitcount" initial-value="0" streamable="yes">
<xsl:accumulator-rule phase="end"
match="Entry[DebitCredit eq 'D']"
select="$value + 1"/>
</xsl:accumulator>
I'm finding that apparently the sweep of any patterns in the match, select, or sequence constructor must be motionless. I'm able to access attribute values for the current element but not child elements or anything ahead of the current element.
I'm wondering if what I'm trying to do is even possible with accumulators in streaming mode - I'm pretty sure I can accomplish what I'm aiming for here with iterator params, but it seems like a pretty big limitation if I'm understanding the docs correctly.

In my understanding, the only way with a streaming accumulator to store the content of an element is to match on the text child node so e.g.
<xsl:accumulator name="current-amount" as="xs:decimal?" initial-value="()" streamable="yes">
<xsl:accumulator-rule match="Entry/Amount/text()" select="xs:decimal(.)"/>
</xsl:accumulator>
Then you should be able to add up those values in similar rules like
<xsl:accumulator name="credit" as="xs:decimal" initial-value="0" streamable="yes">
<xsl:accumulator-rule match="Entry/DebitCredit/text()" select="if (. = 'C') then $value + accumulator-before('current-amount') else $value"/>
</xsl:accumulator>
<xsl:accumulator name="debit" as="xs:decimal" initial-value="0" streamable="yes">
<xsl:accumulator-rule match="Entry/DebitCredit/text()" select="if (. = 'D') then $value - accumulator-before('current-amount') else $value"/>
</xsl:accumulator>
The same approach (i.e. matching on the text child node) should do if you only want to count the number of DebitCredit/text()[. = 'C'] nodes.
It is a bit of pain if you are used to normal XSLT/XPath where I certainly advice people to never explicitly select text nodes unless they have to deal with mixed contents but I have found that uses streaming forces you to change your XSLT/XPath coding approach quite a lot.
Here is an example, with the input being
<Root>
<Entry>
<Amount>100</Amount>
<DebitCredit>C</DebitCredit>
</Entry>
<Entry>
<Amount>50</Amount>
<DebitCredit>D</DebitCredit>
</Entry>
<Entry>
<Amount>10</Amount>
<DebitCredit>C</DebitCredit>
</Entry>
<Entry>
<Amount>20</Amount>
<DebitCredit>D</DebitCredit>
</Entry>
</Root>
Saxon 9.8.0.8 EE with the stylesheet
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:math="http://www.w3.org/2005/xpath-functions/math"
exclude-result-prefixes="xs math"
version="3.0">
<xsl:output method="text"/>
<xsl:mode on-no-match="shallow-skip" streamable="yes" use-accumulators="#all"/>
<xsl:accumulator name="current-amount" as="xs:decimal?" initial-value="()" streamable="yes">
<xsl:accumulator-rule match="Entry/Amount/text()" select="xs:decimal(.)"/>
</xsl:accumulator>
<xsl:accumulator name="credit" as="xs:decimal" initial-value="0" streamable="yes">
<xsl:accumulator-rule match="Entry/DebitCredit/text()" select="if (. = 'C') then $value + accumulator-before('current-amount') else $value"/>
</xsl:accumulator>
<xsl:accumulator name="debit" as="xs:decimal" initial-value="0" streamable="yes">
<xsl:accumulator-rule match="Entry/DebitCredit/text()" select="if (. = 'D') then $value - accumulator-before('current-amount') else $value"/>
</xsl:accumulator>
<xsl:accumulator name="debitcount" initial-value="0" streamable="yes">
<xsl:accumulator-rule
match="Entry/DebitCredit/text()[. = 'D']"
select="$value + 1"/>
</xsl:accumulator>
<xsl:template match="/*" expand-text="yes">
<xsl:apply-templates/>
Debit count {accumulator-after('debitcount')}
Sum of credits {accumulator-after('credit')},
Sum of debits {accumulator-after('debit')}
</xsl:template>
</xsl:stylesheet>
outputs
Debit count 2
Sum of credits 110,
Sum of debits -70

Related

Find and ReplaceAll : To get Find Value in Attribute and Replace with Content using XSLT3.0

I would like to do Find and Replace using XSLT 3.0. When I have found the value from TextStyle element with attribute of FONTSTYLE value it should store in variables and replace with the text.
Found Pattern is : <String ID="p1_w5" CONTENT="Human" HPOS="261.948" VPOS="75.8759" STYLEREFS="font1"/>
Replace Pattern Expect this : <String ID="p1_w5" CONTENT="<bold>Human</bold>" HPOS="261.948" VPOS="75.8759" STYLEREFS="font1"/>
How do achieve my requirements using XSLT Find and Replace?
My Current Input XML File is :
<?xml version="1.0" encoding="UTF-8"?>
<ALTO>
<STYLES>
<TextStyle ID="font1" FONTFAMILY="cambria" FONTSIZE="12.000" FONTSTYLE="bold"/>
<TextStyle ID="font2" FONTFAMILY="cambria" FONTSIZE="7.920" FONTSTYLE="sup"/>
<TextStyle ID="font3" FONTFAMILY="cambria" FONTSIZE="12.000" FONTSTYLE="it"/>
</STYLES>
<LAYOUT>
<TextBlock ID="p1_b1" HPOS="83.6703" VPOS="75.8759" HEIGHT="10.6680" WIDTH="445.700">
<TextLine WIDTH="445.700" HEIGHT="10.6680" ID="p1_t1" HPOS="83.6703" VPOS="75.8759">
<String ID="p1_w1" CONTENT="Hie" HPOS="83.6703" VPOS="75.8759" STYLEREFS="font0"/>
<String ID="p1_w2" CONTENT="org" HPOS="154.915" VPOS="75.8759" STYLEREFS="font0"/>
<String ID="p1_w3" CONTENT="of" HPOS="228.005" VPOS="75.8759" STYLEREFS="font0"/>
<String ID="p1_w4" CONTENT="the" HPOS="241.393" VPOS="75.8759" STYLEREFS="font0"/>
<String ID="p1_w5" CONTENT="Human" HPOS="261.948" VPOS="75.8759" STYLEREFS="font1"/>
<String ID="p1_w6" CONTENT="cell" HPOS="303.263" VPOS="75.8759" STYLEREFS="font0"/>
<String ID="p1_w8" CONTENT="a" HPOS="354.900" VPOS="75.8759" STYLEREFS="font0"/>
<String ID="p1_w9" CONTENT="CANCER" HPOS="363.965" VPOS="75.8759" STYLEREFS="font3"/>
</TextLine>
</TextBlock>
</LAYOUT>
</ALTO>
Tried XSLT file :
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:fnc="http://www.xsweet.org/2022/ext"
xmlns:math="http://www.w3.org/2005/xpath-functions/math"
xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl"
exclude-result-prefixes="#all"
version="3.0">
<xsl:output method="xml" indent="yes"/>
<xsl:preserve-space elements="*"/>
<xsl:template match="/|node()|*|#*">
<xsl:copy>
<xsl:apply-templates select="node() | * | #*"/>
</xsl:copy>
</xsl:template>
<xsl:param name="styletag1" select="TextStyle[#FONTSTYLE = 'sup']"/>
<xsl:param name="styletag2" select="TextStyle[#FONTSTYLE = 'it']"/>
<xsl:param name="styletag3" select="TextStyle[#FONTSTYLE = 'bold']"/>
<xsl:template match="/|node()|*|#*">
<xsl:copy>
<xsl:apply-templates select="node() | * | #*"/>
</xsl:copy>
</xsl:template>
<xsl:template match="LAYOUT/TextBlock/TextLine/String[$styletag1]">
<xsl:message>Superscript Need to Replace All</xsl:message>
</xsl:template>
</xsl:stylesheet>
You can do
<xsl:key name="text-style" match="TextStyle/#FONTSTYLE" use="../#ID"/>
<xsl:mode on-no-match="shallow-copy"/>
<xsl:template match="String[key('text-style', #STYLEREFS)]/#CONTENT">
<xsl:attribute name="{name()}" select="'<' || key('text-style', ../#STYLEREFS) || '>' || . || '</' || key('text-style', ../#STYLEREFS) || '>'"/>
</xsl:template>
but of course the output is XML with entity references in the attribute value e.g.
<String ID="p1_w5" CONTENT="<bold>Human</bold>" HPOS="261.948" VPOS="75.8759" STYLEREFS="font1"/>
If you really want e.g. CONTENT="<bold>Human</bold>" then use a character map
<xsl:output use-character-maps="m1"/>
<xsl:character-map name="m1">
<xsl:output-character character="<" string="<"/>
<xsl:output-character character=">" string=">"/>
</xsl:character-map>

XSLT Can't Read an Excel XML File?

I'm using XSLT / XPath to browse some of the XML files you get when you unzip an Excel file. I found a "relationships" file workbook.xml.rels that I don't seem to be able to read, using code similar to that which successfully read the workbook.xml file.
Here's some of the workbook.xml file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<workbook xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"
...
<sheets>
<sheet name="Sheet1"
sheetId="2"
r:id="rId1"/>
<sheet name="Test Sheet"
sheetId="1"
r:id="rId2"/>
</sheets>
...
</workbook>
Here's the workbook.xml.rels file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Relationships xmlns="http://schemas.openxmlformats.org/package/2006/relationships">
<Relationship Id="rId3"
Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/theme"
Target="theme/theme1.xml"/>
<Relationship Id="rId2"
Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/worksheet"
Target="worksheets/sheet2.xml"/>
<Relationship Id="rId1"
Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/worksheet"
Target="worksheets/sheet1.xml"/>
<Relationship Id="rId5"
Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/sharedStrings"
Target="sharedStrings.xml"/>
<Relationship Id="rId4"
Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/styles"
Target="styles.xml"/>
</Relationships>
Here's some of the XSLT:
<?xml version="1.0"?>
<!-- greeting.xsl -->
<xsl:stylesheet
...
<xsl:output method="text"/>
<xsl:variable name="baseDir" select="replace(document-uri(.), '(.*[\\/]xl).*', '$1/')"/>
<xsl:variable name="workbook" select="concat($baseDir, 'workbook.xml')"/>
<xsl:variable name="theSheetId" select="doc($workbook)/workbook/sheets/sheet[matches(#name, 'Test Sheet')]/#r:id"/>
<xsl:variable name="workbook_rels" select="concat($baseDir, '_rels/workbook.xml.rels')"/>
<!-- code to read workbook.xml.rels -->
<xsl:variable name="theSheet" select="doc($workbook_rels)/Relationships/Relationship[matches(#Id, $theSheetId)]/#Target"/>
<xsl:template match="/">
<xsl:text>
baseDir = </xsl:text><xsl:value-of select="$baseDir"/>
<xsl:text>
workbook = </xsl:text><xsl:value-of select="$workbook"/>
<xsl:text>
workbook_rels = </xsl:text><xsl:value-of select="$workbook_rels"/>
<xsl:text>
theSheetId = </xsl:text><xsl:value-of select="$theSheetId"/>
<xsl:text>
theSheet = </xsl:text><xsl:value-of select="$theSheet"/>
<xsl:text>
end</xsl:text>
</xsl:template>
</xsl:stylesheet>
And the output:
baseDir = file:/C:/Training/sandbox/conv_/xl/
workbook = file:/C:/Training/sandbox/conv_/xl/workbook.xml
workbook_rels = file:/C:/Training/sandbox/conv_/xl/_rels/workbook.xml.rels
theSheetId = rId2
theSheet = **<I get nothing here>**
end
You can see that 'theSheetID' variable is correctly set when reading workbook.xml. But when I use that variable to get the corresponding Target value into 'theSheet' variable from workbook.xml.rels, I get nothing. I tried replacing the matches expression with just a number but I still get nothing. Is there a problem from reading this type of file?
Suggestions? Thanks!
The use of matches and replace suggests you are using an XSLT 2 or 3 processor and that way XSLT 2 or 3 where you can certainly declare xpath-default-namespace, you just have to understand you have to change that in the sections that deal with elements from a different namespace e.g. <xsl:variable name="theSheet" select="doc($workbook_rels)/Relationships/Relationship[matches(#Id, $theSheetId)]/#Target" xpath-default-namespace="http://schemas.openxmlformats.org/package/2006/relationships"/>.
Given the samples I would rather use a key <xsl:key name="rel" match="Relationships/Relationship" use="#Id" xpath-default-namespace="http://schemas.openxmlformats.org/package/2006/relationships"/> and then use <xsl:variable name="theSheet" select="key('rel,$theSheetId, doc($workbook_rels))/#Target"/> but the use of xpath-default-namespace to declare the relevant namespace when selecting elements from a particular document is probably what is missing in your XSLT.

How to process two parts of a single xml by streaming?

I have a really large XML that has two different sets of data. I need to stream through one and do a lookup on the other. My Data looks like below
<?xml version="1.0" encoding="utf-8"?>
<Root>
<EmployeePersonal>
<Employee>
<ID>21234</ID>
<Name>Jim Carrey</Name>
<Age>43</Age>
<City>Chicago</City>
<State>IL</State>
</Employee>
<Employee>
<ID>41876</ID>
<Name>Edward Norton</Name>
<Age>33</Age>
<City>New York</City>
<State>NY</State>
</Employee>
<Employee>
<ID>51239</ID>
<Name>Eli Roth</Name>
<Age>46</Age>
<City>Los Angeles</City>
<State>CA</State>
</Employee>
</EmployeePersonal>
<EmployeeEmployment>
<Empl>
<Emplid>21234</Emplid>
<Title>HR Partner</Title>
<HireDate>2008-12-29</HireDate>
</Empl>
<Empl>
<Emplid>41876</Emplid>
<Title>Comp Partner</Title>
<HireDate>1999-07-09</HireDate>
</Empl>
<Empl>
<Emplid>51239</Emplid>
<Title>Programmer</Title>
<HireDate>2004-12-06</HireDate>
</Empl>
</EmployeeEmployment>
</Root>
I would like to loop through the /Root/EmployeePersonal data and lookup the /Root/EmployeeEmployment by matching on the employee id.
I tried to loop through one and then load into a map and then loop through the other, but kept getting an error. Finally I tried loading one set into a variable and then tried to stream the other, but in vain. This is what I've tried so far.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="xs"
version="3.0">
<xsl:mode streamable="yes" on-no-match="shallow-skip"/>
<xsl:output indent="no"/>
<xsl:variable name="vEmploymentData" select="Root/copy-of(EmployeeEmployment)"/>
<xsl:template match="/Root/EmployeePersonal">
<AllEmployeeData>
<xsl:for-each select="Employee/copy-of()">
<Employee>
<xsl:copy-of select="./*"/>
<xsl:copy-of select="$vEmploymentData/Empl[Emplid=current()/ID]/*[local-name() ne 'Emplid']"/>
</Employee>
</xsl:for-each>
</AllEmployeeData>
</xsl:template>
</xsl:stylesheet>
I need to merge these two sets of data together. Since the data is huge, is there a way to stream both sets of data in?
Thanks
Given that you need to different sets of the data at the same time to compare and merge them I am not sure there is an easy single pass, streamable and therefore forwards-only approach, so some easy way around that would be to set up the same document twice as an xsl:merge-source for an xsl:merge:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="#all">
<xsl:param name="input-uri" as="xs:string" select="'input1.xml'"/>
<xsl:output indent="yes"/>
<xsl:template name="xsl:initial-template">
<AllEmployeeData>
<xsl:merge>
<xsl:merge-source name="emp-details1" for-each-source="$input-uri" streamable="yes" select="Root/EmployeePersonal/Employee">
<xsl:merge-key select="ID"/>
</xsl:merge-source>
<xsl:merge-source name="emp-details2" for-each-source="$input-uri" streamable="yes" select="Root/EmployeeEmployment/Empl">
<xsl:merge-key select="Emplid"/>
</xsl:merge-source>
<xsl:merge-action>
<xsl:copy>
<xsl:copy-of select="current-merge-group('emp-details1')/*, current-merge-group('emp-details2')/(* except Emplid)"/>
</xsl:copy>
</xsl:merge-action>
</xsl:merge>
</AllEmployeeData>
</xsl:template>
</xsl:stylesheet>
As xsl:merge works with a snapshot, that has the advantage that the access to ID and Emplid child is not a problem. You also don't have to take any particular action to buffer data in maps or accumulators. The main disadvantage is that xsl:merge expects the sources to be ordered by the merge keys, that seems to be the case for your sample data but I am not sure that will be true for your complete data.
You would run such a stylesheet with Saxon 9 EE using the command line option -it to start without a primary input but with the initial template named xsl:initial-template instead.
As an alternative approach that only reads through the main input once but buffers the EmployeePersonal/Employee in an accumulator using a Saxon 9.9 EE specific saxon:capture attribute you could use:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:saxon="http://saxon.sf.net/"
exclude-result-prefixes="#all">
<xsl:output indent="yes"/>
<xsl:mode streamable="yes" on-no-match="shallow-skip" use-accumulators="emp-details1"/>
<xsl:accumulator name="emp-details1" streamable="yes" as="element(Employee)*" initial-value="()">
<xsl:accumulator-rule match="EmployeePersonal/Employee" phase="end" saxon:capture="yes" select="$value, ."/>
</xsl:accumulator>
<xsl:template match="/*">
<AllEmployeeData>
<xsl:apply-templates/>
</AllEmployeeData>
</xsl:template>
<xsl:template match="EmployeeEmployment/Empl">
<Employee>
<xsl:variable name="this" select="copy-of()"/>
<xsl:copy-of select="accumulator-before('emp-details1')[ID = $this/Emplid]/*, $this/(* except Emplid)"/>
</Employee>
</xsl:template>
</xsl:stylesheet>
This reads through the input only once but buffers all EmployeePersonal/Employee in memory and then uses the buffered/accumulated elements later one when EmployeeEmployment/Empl is matched to output the necessary corresponding data. This also of course, as the output is created when matching EmployeeEmployment/Empl, requires the presence of all ids in that data, I am not sure that is the case or whether the EmployeePersonal/Employee is the main input and you only look for matching EmployeeEmployment/Empl if it exists.
Finally, you could as well try to store the details of EmployeePersonal/Employee in an accumulator using a map and then access this from the template for EmployeeEmployment/Empl:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:map="http://www.w3.org/2005/xpath-functions/map"
xmlns:saxon="http://saxon.sf.net/"
expand-text="yes"
exclude-result-prefixes="#all">
<xsl:output indent="yes"/>
<xsl:mode streamable="yes" on-no-match="shallow-skip" use-accumulators="#all"/>
<xsl:accumulator name="current-emp-id" streamable="yes" as="xs:integer?" initial-value="()">
<xsl:accumulator-rule match="EmployeePersonal/Employee/ID/text()" select="xs:integer(.)"/>
</xsl:accumulator>
<xsl:accumulator name="emp-details" streamable="yes" as="map(xs:integer, map(xs:string, xs:string))" initial-value="map{}">
<xsl:accumulator-rule match="EmployeePersonal/Employee/ID/text()" select="map:put($value, xs:integer(.), map{})"/>
<xsl:accumulator-rule match="EmployeePersonal/Employee/*[not(self::ID)]/text()"
select="map:put($value, accumulator-before('current-emp-id'), map:put(map:get($value, accumulator-before('current-emp-id')), local-name(..), string()))"/>
</xsl:accumulator>
<xsl:template match="/*">
<AllEmployeeData>
<xsl:apply-templates/>
</AllEmployeeData>
</xsl:template>
<xsl:template match="EmployeeEmployment/Empl">
<Employee>
<xsl:variable name="this" select="copy-of()"/>
<ID>{$this/Emplid}</ID>
<xsl:apply-templates select="map:get(accumulator-before('emp-details'), xs:integer($this/Emplid))" mode="entry-to-element"/>
<xsl:copy-of select="$this/(* except Emplid)"/>
</Employee>
</xsl:template>
<xsl:template match=".[. instance of map(*)]" mode="entry-to-element">
<xsl:variable name="map" select="."/>
<xsl:for-each select="map:keys(.)">
<xsl:element name="{.}">{map:get($map, .)}</xsl:element>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
Of course it will still buffer all the EmployeePersonal/Employee data, only this time using a light-weight map instead of a sequence of XML snapshot elements. The main disadvantage is that XSLT 3/XPath 3.1 maps have no order so unless you later spell out each entry you are looking for in the wanted order you get the results in a random order. In the example above I have simply used a for-each to convert map entries back to XML elements so the order is a random order and not the one of the input XML (that the xsl:merge approach or the saxon:capture approach would preserve).
As you asked in a comment about using xsl:merge but provide the input as a primary input source, the only way I can think of is to use it as a dummy streamable input and then to provide its document-uri() for the xsl:merge/xsl:merge-source, that is, to adapt the code from above to
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="#all">
<xsl:mode streamable="yes"/>
<xsl:output indent="yes"/>
<xsl:template match="/">
<AllEmployeeData>
<xsl:variable name="input-uri" as="xs:anyURI" select="document-uri()"/>
<xsl:message select="$input-uri"/>
<xsl:merge>
<xsl:merge-source name="emp-details1" for-each-source="$input-uri" streamable="yes" select="Root/EmployeePersonal/Employee">
<xsl:merge-key select="ID"/>
</xsl:merge-source>
<xsl:merge-source name="emp-details2" for-each-source="$input-uri" streamable="yes" select="Root/EmployeeEmployment/Empl">
<xsl:merge-key select="Emplid"/>
</xsl:merge-source>
<xsl:merge-action>
<xsl:copy>
<xsl:copy-of select="current-merge-group('emp-details1')/*, current-merge-group('emp-details2')/(* except Emplid)"/>
</xsl:copy>
</xsl:merge-action>
</xsl:merge>
</AllEmployeeData>
</xsl:template>
</xsl:stylesheet>
Interestingly enough, that works with Saxon 9.7 EE (of course that opening the same input three times for streaming) but fails with an error " XTSE3430: Template rule is not streamable * The merge-source/#select expression is not striding" in Saxon 9.8 and 9.9 EE.
Not sure whether that helps, in earlier questions you seemed to indicate that the tool you use embeds Saxon 9.7 EE so it might be an option.

Populating nodes based on condition in Receiver file

I need to populate one segment based on input values.the requirement like below
in the input payload we are getting below segment like
<charac>
<charactername>
<charactervalue>
</charac>
so the above segment may come multiple times but based on the few values only need to populate the segment for example,
<charac>
<charactername>print</charactername>
<charactervalue>123</charactervalue>
</charac>
<charac>
<charactername>comp</charactername>
<charactervalue>1234</charactervalue>
</charac>
<charac>
<charactername>pal</charactername>
<charactervalue>1235</charactervalue>
</charac>
so here only I need populate segment when charactername is equal to only print or comp
the receiver structure the segment is
<e1edl1>
<at>
<rt>
</e1edl1>
so the output should be like
<e1edl1>
<at>print</at>
<rt>123</rt>
</e1edl1>
<e1edl1>
<at>comp</at>
<rt>1234</rt>
</e1edl1>
I tried with below code
<ns0:if test="count(./charac)!=0">
<ns0:for-each select="./charac">
<e1edl1 SEGMENT="1">
<at>
<ns0:value-of select="charactername" />
</at>
<rt>
<ns0:value-of select="charactervalue" />
</rt>
</e1edl1>
</ns0:for-each>
</ns0:if>
could you please help on this.
Regards,
Janardhan
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:strip-space elements="*"/>
<xsl:output omit-xml-declaration="yes" indent="yes"/>
<xsl:template match="/">
<xsl:apply-templates select="//charac[charactername='print' or charactername='comp']" />
</xsl:template>
<xsl:template match="charac">
<e1edl1>
<at><xsl:value-of select="charactername" /></at>
<rt><xsl:value-of select="charactervalue" /></rt>
</e1edl1>
</xsl:template>
</xsl:stylesheet>

from string to number xslt

I want to make a comparison of two different date’s. To realize that, I want to transform to number.
Input example:
<file>
<date>2015-11-06 09:00/>
</file>
<history>
<date>2016-01-12 10:00/>
</history>
First I extract the time, from date. And put the result in a var.
<xsl:for-each select="//item/metadata/document/file/date">
<xsl:variable name="d_log"
select="substring-before(., ' ')" as="xs:string"/>
So the value of the variable would be, for example 2015-11-06.
The next step is, that I want to transform 2015-11-06 in to 20151106.
Questions is how I can transform from a string to a number?
Or is there a easier way?
You can do:
translate(substring-before(., ' '), '-', '')
to get the expected number.
However, your syntax suggests you are using XSLT 2.0. If so, why don't you convert the given strings to xs:date or xs:dateTime and compare them as such?
Here is my result.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="xs"
version="2.0">
<xsl:output method="xml" indent="yes"></xsl:output>
<xsl:template match="/">
<aaa>
<xsl:for-each select="//item/metadata/document/file/date">
<xsl:variable name="d_log"
select="translate(substring-before(., ' '), '-', '')"
as="xs:string"/>
<xsl:for-each select="../../history/log/date">
<xsl:variable name="d_doc" select="translate(substring-before(., ' '), '-', '')" as="xs:string"/>
<xsl:if test="$d_doc > $d_log">
<bb>
<xsl:value-of select="node()"/>
</bb>
</xsl:if>
</xsl:for-each>
</xsl:for-each>
</aaa>
</xsl:template>
</xsl:stylesheet>

Resources