2. As I point out in the post,
https://stackoverflow.com/questions/67575484/what-attribute-node-cannot-follow-non-attribute-node-in-element-content-tells
it is not only very difficult to search value if anelement (<currency>)
contains both element (<id>) and text value(USD) but alsoreturns false result.
<amount>
<currency>
<id>settlementCurrency</id>USD</currency>
<referenceAmount>StandardISDA</referenceAmount>
<cashSettlement>true</cashSettlement>
</amount>
That USD really is the value of <currency>. In this case, it is legitimate
andsensible to transform id as sibling element of its originalelement
<currency> (its parent is still <amount>) to:
<amount>
<currency>USD</currency>
<id>settlementCurrency</id>
<referenceAmount>StandardISDA</referenceAmount>
<cashSettlement>true</cashSettlement>
</amount>
The flattened XML is very searchable (an index on 'currency' is good enough)
and can be transformed to JSON.
On Friday, May 21, 2021, 10:35:53 a.m. MST, Martin Honnen
martin(_dot_)honnen(_at_)gmx(_dot_)de
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
On 21.05.2021 16:30, Sam Spade anonymousjuly1(_at_)yahoo(_dot_)ca wrote:
|The transformation logic:
|||
|
1) transform namespace
2) transform root element
3) transform the selected attribute(s) to element (the attribute name is
parameterised not hard-coded)
4) the transformed element shouldn't contain both other element
(transformed from the attribute) and its original data
|
|
The desired result:
|<requestProduct xmlns="http://fc.fasset/product";> <trade> <cal>
<c>PRECEDING</c> <bcs> <id>businessCenters</id> <bc>USNY</bc>
<bc>GBLO</bc> </bcs> </cal> <amount> *<currency>USD</currency>
<id>settlementCurrency</id>*
<referenceAmount>StandardISDA</referenceAmount>
<cashSettlement>true</cashSettlement> </amount> </trade> </requestProduct>|
What is wrong with my module? How can I transform the input to the
desired result? |
What is the criteria to transform an attribute to a child element of its
parent as is done for the "id" of the "bcs" element and what is the
criteria for the other choice, to not include the new element as a child
but to make it a sibling of the (previous) parent element?
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--