It's a pain, isn't it... (and you have to wonder what sort of an idiot thinks that it would be cool to make up a namespace like that) . But if you want to produce the Guidelines in PDF using LaTeX, either you have to ditch that example, or misrepresent the RDF namespace, or somehow find a way of tweaking the LaTeX code before it gets processed (in LaTeX, I believe, you would simply escape the character with a backslash) On 02/10/15 23:13, Syd Bauman wrote:
you need to lose the sharp sign in your xenodata as I said earlier Sorry, hadn't caught up with the PDF thread, yet.
because there is an unescaped # character (which is Magic in Latex) floating around in one of the xenodata examples ... which doesn't affect the sense of the example in any way that I can see Thanks for the catch, Lou. (Nicely done.) But how do I escape it?[1] (I don't think it makes sense to just remove it, because according to http://www.w3.org/TR/REC-rdf-syntax/#section-Namespace the RDF namespace is "http://www.w3.org/1999/02/22-rdf-syntax-ns#", not "http://www.w3.org/1999/02/22-rdf-syntax-ns". And since, according to http://www.w3.org/TR/REC-xml-names/#NSNameComparison, comparison of namespaces is simply a case-sensitive string comparison, not a resolve-URI-escapes-first comparison, we can't use "...-ns%23".)
Notes ----- [1] There is only 1 problematic '#', I think. There are only 4 <egXML> elements that contain <xenoData>, all in xenoData.xml. There are only 3 '#' signs in that entire file (and I checked for NCRs, too). One of them is part of an NCR ("…"), so it's not the problem. Another is part of a namespace declaration, so it's not the problem. The third is the last character of the RDF namespace, which is being given to the reader because the example uses that namespace.