xml - XSLT 2.0 - filter nodes by lang/locale hierarchy and content -



xml - XSLT 2.0 - filter nodes by lang/locale hierarchy and content -

using xslt 2.0, how can dynamically process xml document remove nodes have xml:lang attribute, based on rules/requirements below?

requirements:

find node (and it's same-type immediate siblings) attribute xml:lang know xml:lang values have 3-tier hierarchy based on language/locale, non-exhaustive examples below: x-default (tier 1, highest) en (tier 2, language prefix, other value examples: fr, es, ru) en-us (tier 3, language prefix followed suffix, other value examples: en-gb, en-ca) based on known hierarchy, duplicate values should removed. when removing duplicates, take consideration existence of additional attributes sibling may have. leave rest of xml document unmolested

example dataset:

<?xml version="1.0" encoding="utf-8"?> <arbitrarydepth> <scenario1 xml:lang="x-default">a default node value</scenario1> <scenario1 xml:lang="en">a default node value</scenario1> <scenario1 xml:lang="en-us">a default node value</scenario1> <scenario2 xml:lang="x-default">the orig value</scenario2> <scenario2 xml:lang="en">the orig value</scenario2> <scenario2 xml:lang="en-us">a new value</scenario2> <scenario3 xml:lang="x-default">the orig value</scenario3> <scenario3 xml:lang="en">a new value</scenario3> <scenario3 xml:lang="en-us">the orig value</scenario3> <scenario4 xml:lang="x-default">the orig value</scenario4> <scenario4 xml:lang="en">an english language value</scenario4> <scenario4 xml:lang="en-us">an english language value</scenario4> <scenario4 xml:lang="fr">a french value</scenario4> <scenario4 xml:lang="fr-fr">a french value</scenario4> <scenario4 xml:lang="fr-ca">a french canada value</scenario4> <scenario5 xml:lang="x-default" attr0="something here">the orig value</scenario5> <scenario5 xml:lang="en" attr1="some attribute">the orig value</scenario5> <scenario5 xml:lang="en-us" attr2="some other attribute">the orig value</scenario5> <scenario5 xml:lang="fr" attr0="something here">the orig value</scenario5> <scenario5 xml:lang="fr-fr">the orig value</scenario5> </arbitrarydepth>

example resultset:

<?xml version="1.0" encoding="utf-8"?> <arbitrarydepth> <scenario1 xml:lang="x-default">a default node value</scenario1> <scenario2 xml:lang="x-default">the orig value</scenario2> <scenario2 xml:lang="en-us">a new value</scenario2> <scenario3 xml:lang="x-default">the orig value</scenario3> <scenario3 xml:lang="en">a new value</scenario3> <scenario3 xml:lang="en-us">the orig value</scenario3> <scenario4 xml:lang="x-default">the orig value</scenario4> <scenario4 xml:lang="en">an english language value</scenario4> <scenario4 xml:lang="en-us">an english language value</scenario4> <scenario4 xml:lang="fr">a french value</scenario4> <scenario4 xml:lang="fr-ca">a french canada value</scenario4> <scenario5 xml:lang="x-default" attr0="something here">the orig value</scenario5> <scenario5 xml:lang="en" attr1="some attribute">the orig value</scenario5> <scenario5 xml:lang="en-us" attr2="some other attribute">the orig value</scenario5> </arbitrarydepth>

this should fulfill requirements, except lastly 1 matching dynamic attributes:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/xsl/transform" version="1.0"> <xsl:template match="*"> <xsl:variable name="elementname" select="name()"/> <xsl:variable name="contenttext" select="normalize-space(.)"/> <xsl:choose> <xsl:when test="not(@xml:lang)"> <!-- non-lang element --> <xsl:copy> <xsl:copy-of select="@*"/> <xsl:apply-templates select="*"/> </xsl:copy> </xsl:when> <xsl:when test="@xml:lang='x-default'"> <!-- tier 1: xml:lang="x-default" --> <xsl:copy-of select="."/> </xsl:when> <xsl:when test="contains(@xml:lang,'-')"> <!-- tier 3: xml:lang="en-us" --> <xsl:variable name="baselang" select="substring-before(@xml:lang, '-')"/> <xsl:choose> <xsl:when test="../*[name()=$elementname][@xml:lang=$baselang][normalize-space(.)=$contenttext]"> <!-- same text tier 2 parent --> </xsl:when> <xsl:when test="../*[name()=$elementname][@xml:lang=$baselang]"> <xsl:copy-of select="."/> </xsl:when> <xsl:when test="../*[name()=$elementname][@xml:lang='x-default'][normalize-space(.)=$contenttext]"> <!-- same text tier 1 parent --> </xsl:when> <xsl:when test="../*[name()=$elementname][@xml:lang='x-default']"> <xsl:copy-of select="."/> </xsl:when> <xsl:otherwise> <xsl:copy-of select="."/> </xsl:otherwise> </xsl:choose> </xsl:when> <xsl:otherwise> <!-- tier 2: xml:lang="en" --> <xsl:choose> <xsl:when test="../*[name()=$elementname][@xml:lang='x-default'][normalize-space(.)=$contenttext]"> <!-- same text tier 1 parent --> </xsl:when> <xsl:when test="../*[name()=$elementname][@xml:lang='x-default']"> <xsl:copy-of select="."/> </xsl:when> <xsl:otherwise> <!-- no matching parent --> <xsl:copy-of select="."/> </xsl:otherwise> </xsl:choose> </xsl:otherwise> </xsl:choose> </xsl:template> </xsl:stylesheet>

demo: http://www.xsltcake.com/slices/uopn40

matching dynamic attributes between parent , kid complex. have loop trough attributes , compare against current parent. if attribute missing on parent, or if it's value different, have maintain new element.

to fulfill lastly requirement, think have move imperative language (c#, javascript, java).

xml xslt xpath xslt-2.0

Comments

Post a Comment

Popular posts from this blog

assembly - What is the addressing mode for ld, add, and rjmp instructions? -

assembly - What is the addressing mode for ld, add, and rjmp instructions? - hey guys know ldi (load immediate) addressing mode set immediate , st instruction addressing mode set index. however, have no thought others curious are! thanks :) the addressing modes explained in instruction set, in first few pages. in table of instructions see operands instruction determine addressing mode. mode indicated arguments assembly instruction. for example, ld had several different ways of operating, depending on arguments. 1 of them ld rd,x d number of register, such ld r3,x . ld r3,-z else (although both indirect addressing). rjmp k relative addressing, jumping pc + k + 1. add rr,rd direct register addressing. result contained in rd. assembly avr instructions
Read more

vowpalwabbit - Interpreting Vowpal Wabbit results: Why are some lines appended by "h"? -

vowpalwabbit - Interpreting Vowpal Wabbit results: Why are some lines appended by "h"? - below part of log training vw model. why of these lines followed h? you'll notice that's true of "average loss" line in summary @ end. i'm not sure means, or if should care. ... average since illustration illustration current current current loss lastly counter weight label predict features 1.000000 1.000000 1 1.0 -1.0000 0.0000 15 0.500000 0.000000 2 2.0 1.0000 1.0000 15 1.250000 2.000000 4 4.0 -1.0000 1.0000 9 1.167489 1.084979 8 8.0 -1.0000 1.0000 29 1.291439 1.415389 16 16.0 1.0000 1.0000 45 1.096302 0.901166 32 32.0 -1.0000 -1.0000 21 1.299807 1.503312 64 64.0 -1.0000 1.0000 ...
Read more

Is there a way to convert an HTML page styled with Bootstrap CSS into email-compatible html? -

Is there a way to convert an HTML page styled with Bootstrap CSS into email-compatible html? - is there way convert html page styled bootstrap css html email compatible form? see there exclusively different css frameworks, ink, creating email compatible html, there flow creating email doesn't require utilize of different css framework? there html -> pdf -> email html flow? or other flow? no, couple of reasons... first, there no reliable css or html email. clients on place in terms of css back upwards & how render html, structural/semantic problem. isn't converting classes much altering html structure. as explained in this css tricks post, typical solution ol-skool techniques table-based layouts, requiring exclusively restructure existing html. have add together client-specific hacks. second, , more importantly, shouldn't send everything on existing page email. if it's newsletter subscribers, people won't read it. instead, create ...
Read more