29344 2015-12-17 20:03:09 +0000 Failure to close empty elements makes use of XML-based tools for proofing overly difficult - XPath 2015-12-18 09:46:43 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XPath 3.1 Candidate Recommendation PC Linux RESOLVED INVALID P2 normal --- 1 patrick jonathan.robie cmcconkey6 josh.spiegel public-qt-comments oldest_to_newest 124456 0 patrick 2015-12-17 20:03:09 +0000 I would have posted only one issue but as configured, Bugzilla only permits one component per bug. The The current XPath Candidate draft, http://www.w3.org/TR/2015/CR-xpath-31-20151217/, fails to close empty elements as follows: [FODC0002] "file:/home/patrick/working/w3c/XPath3.1.html" (Line 68): The element type "link" must be terminated by the matching end-tag "</link>". [FODC0002] "file:/home/patrick/working/w3c/XPath3.1.html" (Line 68): The element type "meta" must be terminated by the matching end-tag "</meta>". 2 none closed <meta> elements [FODC0002] "file:/home/patrick/working/w3c/XPath3.1.html" (Line 69): The element type "img" must be terminated by the matching end-tag "</img>". 3 none closed <img> elements [FODC0002] "file:/home/patrick/working/w3c/XPath3.1.html" (Line 78): The element type "br" must be terminated by the matching end-tag "</br>". 230 none closed <br> elements [FODC0002] "file:/home/patrick/working/w3c/XPath3.1.html" (Line 9730): The element type "hr" must be terminated by the matching end-tag "</hr>". 2 none closed <hr> elements I make that to be 238 edits that must be made to use XML based tools on the most recent XPath 3.1 Candidate draft. I realize this is a production error but it is one that significantly impacts the review of this draft. 124459 1 josh.spiegel 2015-12-17 20:36:36 +0000 I don't see these problems in the published html. Is it possible that the software you are using to download these files is also modifying them? 124460 2 jonathan.robie 2015-12-17 20:47:21 +0000 I wonder if the XML version would be better for your purposes - you can find it in the headers for the spec. For this version, see http://www.w3.org/TR/2015/CR-xquery-31-20151217/xquery-31.xml 124461 3 jonathan.robie 2015-12-17 20:48:52 +0000 I wonder if the XML version would be better for your purposes - you can find it in the headers for the spec. For this version, see http://www.w3.org/TR/2015/CR-xquery-31-20151217/xquery-31.xml 124466 4 patrick 2015-12-18 03:36:24 +0000 I was using BaseX, which was correctly reporting errors with the file as I presented it. However, the file as displayed (CNTR-U) in Chrome, is not the same file as saved by Chrome. In particular, for some unknown (to me) reason, Chrome is stripping out the closing "/" from empty elements. My bad. I have marked the status of this bug (and soon the others) as Resolved, Invalid. Please re-set if some other notation is more appropriate. Hope you are having a great week! Patrick