The XML Schema set that’s made up of all files that can be traced from the OSEO schema link you have provided, is valid. The tools, unfortunately, don’t seem able to just deal with that one file; which makes the whole process cumbersome, since there are 104 files in total… with very complex include/imports. I’ll … Read more
In XPath, // and .// are both syntactic abbreviations: // is short for /descendant-or-self::node()/ .// is short for self::node()/descendant-or-self::node()/ The descendant-or-self axis contains the context node and all descendents of the context node. So the difference between // and .// reduces to a difference in context nodes. For //, the context node is the root … Read more
What you need to do is transform your XML data into a format that works better with Access. Specifically, you need to insert the parent key value (assuming that it is C_NOT in this case) into each child node. The following XSLT file will do that for you <xsl:stylesheet version=”1.0″ xmlns:xsl=”http://www.w3.org/1999/XSL/Transform”> <xsl:output indent=”yes”/> <xsl:strip-space elements=”*”/> … Read more
I am getting the error: … xsl:version: only 1.0 features are supported Here’s a purely XSLT 1.0 solution: <xsl:stylesheet version=”1.0″ xmlns:xsl=”http://www.w3.org/1999/XSL/Transform”> <xsl:output method=”xml” version=”1.0″ encoding=”UTF-8″ indent=”yes”/> <xsl:strip-space elements=”*”/> <xsl:template match=”event”> <xsl:variable name=”start”> <xsl:call-template name=”dateTime-to-seconds”> <xsl:with-param name=”dateTime” select=”start/@time” /> </xsl:call-template> </xsl:variable> <xsl:variable name=”end”> <xsl:call-template name=”dateTime-to-seconds”> <xsl:with-param name=”dateTime” select=”end/@time” /> </xsl:call-template> </xsl:variable> <xsl:variable name=”duration” select=”$end – $start” … Read more
Similar questions have been asked several times .. in stackoverflow or any tech blogs .. but the answer is always not possible, cases like : (a) validating Element depending on the value or presence of any other element/attribute (b) validating value of an element depending on the value or presence of any other element/attribute (c) … Read more
In XPath 2.0, use the max function. To find the book with the highest id, do /library/book[@id = max(/library/book/@id)]
The following mimics the XSLT 2.0 construct: Create templates in a mode that will re-construct your nodes without namespaces: <!– generate a new element in the same namespace as the matched element, copying its attributes, but without copying its unused namespace nodes, then continue processing content in the “copy-no-namepaces” mode –> <xsl:template match=”*” mode=”copy-no-namespaces”> <xsl:element … Read more
To change tag‘s value to 2 and tag1‘s value to 3, using XMLStarlet: xmlstarlet ed \ -u ‘/root/tag’ -v 2 \ -u ‘/root/tag1’ -v 3 \ <old.xml >new.xml Using your sample input: xmlstarlet ed \ -u ‘/root/tag’ -v 2 \ -u ‘/root/tag1’ -v 3 \ <<<‘<root><tag>1</tag><tag1>2</tag1></root>’ …emits as output: <?xml version=”1.0″?> <root> <tag>2</tag> <tag1>3</tag1> </root>
An attribute must be specified with the following syntax: Name Eq AttValue where Name is a legal XML name, Eq is = optionally preceded or followed by whitespace, and AttValue is a legal attribute value. This definition is true for both XML 1.0 and XML 1.1. If you are trying to specify an attribute as … Read more
‘Variables’ in XSL are actually constants – you cannot change their value. This: <xsl:value-of select=”$counter + 1″/> will just output the value of $counter+1 To do loops you have to use recursion – e.g.: <xsl:stylesheet version=”1.0″ xmlns:xsl=”http://www.w3.org/1999/XSL/Transform”> <xsl:template name=”loop”> <xsl:param name=”i”/> <xsl:param name=”limit”/> <xsl:if test=”$i <= $limit”> <div> <xsl:value-of select=”$i”/> </div> <xsl:call-template name=”loop”> <xsl:with-param name=”i” … Read more