[Bug 29344] New: Failure to close empty elements makes use of XML-based tools for proofing overly difficult - XPath

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29344

            Bug ID: 29344
           Summary: Failure to close empty elements makes use of XML-based
                    tools for proofing overly difficult - XPath
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath 3.1
          Assignee: jonathan.robie@gmail.com
          Reporter: patrick@durusau.net
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 17 December 2015 20:03:12 UTC