I don’t use xmllint, but I think the reason your XPath isn’t working is because your doc.xml file is using a default namespace (http://purl.org/net/ulf/ns/0.4-02). From what I can see, you have 2 options. A. Use xmllint in shell mode and declare the namespace with a prefix. You can then use that prefix in your XPath. … Read more
This transformation: <xsl:stylesheet version=”1.0″ xmlns:xsl=”http://www.w3.org/1999/XSL/Transform”> <xsl:output omit-xml-declaration=”yes” indent=”yes”/> <xsl:template match=”t”> <p> <xsl:apply-templates/> </p> </xsl:template> <xsl:template match=”text()” name=”insertBreaks”> <xsl:param name=”pText” select=”.”/> <xsl:choose> <xsl:when test=”not(contains($pText, ‘
’))”> <xsl:copy-of select=”$pText”/> </xsl:when> <xsl:otherwise> <xsl:value-of select=”substring-before($pText, ‘
’)”/> <br /> <xsl:call-template name=”insertBreaks”> <xsl:with-param name=”pText” select= “substring-after($pText, ‘
’)”/> </xsl:call-template> </xsl:otherwise> </xsl:choose> </xsl:template> </xsl:stylesheet> when applied on this XML document: <t>Line1 Line2 Line3 </t> … Read more
The currently accepted answer will return incorrect paths. For example, the element Ele2 in the OP sample XML would return the path /Doc[1]/Ele2[2]. It should be /Doc[1]/Ele2[1]. Here’s a similar XSLT 1.0 template that returns the correct paths: <xsl:template name=”genPath”> <xsl:param name=”prevPath”/> <xsl:variable name=”currPath” select=”concat(“https://stackoverflow.com/”,name(),'[‘, count(preceding-sibling::*[name() = name(current())])+1,’]’,$prevPath)”/> <xsl:for-each select=”parent::*”> <xsl:call-template name=”genPath”> <xsl:with-param name=”prevPath” select=”$currPath”/> … Read more
The two options are almost exactly the same. Here are your two choices: <html>This is <b>bold</b></html> <html><![CDATA[This is <b>bold</b>]]></html> In both cases, you have to check your string for special characters to be escaped. Lots of people pretend that CDATA strings don’t need any escaping, but as you point out, you have to make sure … Read more
This is FAQ (but I’m lazy to search duplicates today) In XPath 1.0 //*[local-name()=’name’] Selects any element with “name” as local-name. In XPath 2.0 you can use: //*:name
If you happen to have Visual Studio, open the DTD file an you should have a button to “Create Schema” out of it. I haven’t checked if it was available on Express edition, though.
There is an article titled “Principles of XML design: When to use elements versus attributes” on IBM’s website. Though there doesn’t appear to be many hard and fast rules, there are some good guidelines mentioned in the posting. For instance, one of the recommendations is to use elements when your data must not be normalized … Read more
Generally I would consider the use of an unprefixed // as a bad smell in an XPath. Try this:- /DocText/WithQuads/Page/Word[text()=’July’ and Quad/P1/@X > 90] Your problem is that you use the //P1[@X < 90] which starts back at the beginning of the document and starts hunting any P1 hence it will always be true. Similarly … Read more
Because in the constructor, I had super(context) instead of super(context, attrs). Makes sense, if you don’t pass in the attributes, such as the id, then the view will have no id and therefore not be findable using that id. 🙂
You’ll need to associate the XML document in Visual Studio with the XSD file you have. You should see something like this in your Properties window of the XML document: In the XML schema set editor (opens when you click on the (…) ellipsis in the “Schemas” textbox in your Properties window) you need to … Read more