This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The current XQuery Candidate draft, http://www.w3.org/TR/2015/CR-xquery-31-20151217/, fails to close empty elements as follows: [FODC0002] "file:/home/patrick/working/w3c/XQuery3.1.html" (Line 68): The element type "link" must be terminated by the matching end-tag "</link>". [FODC0002] "file:/home/patrick/working/w3c/XQuery3.1.html" (Line 68): The element type "meta" must be terminated by the matching end-tag "</meta>". (lines 3 and 4 for the <meta> elements. There are 2 <meta> elements [FODC0002] "file:/home/patrick/working/w3c/XQuery3.1.html" (Line 69): The element type "img" must be terminated by the matching end-tag "</img>". There are 3 <img> elements that are not closed. [FODC0002] "file:/home/patrick/working/w3c/XQuery3.1.html" (Line 78): The element type "br" must be terminated by the matching end-tag "</br>". There are 353 <br> elements that are not closed. [FODC0002] "file:/home/patrick/working/w3c/XQuery3.1.html" (Line 17618): The element type "hr" must be terminated by the matching end-tag "</hr>". There are 2 <hr> elements that are not closed. I make that to be 361 edits that must be made to use XML based tools on the most recent XQuery 3.1 Candidate draft. I realize this is a production error but it is one that significantly impacts the review of this draft.
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