This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29344 - Failure to close empty elements makes use of XML-based tools for proofing overly difficult - XPath
Summary: Failure to close empty elements makes use of XML-based tools for proofing ove...
Status: RESOLVED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-17 20:03 UTC by Patrick Durusau
Modified: 2015-12-18 09:46 UTC (History)
2 users (show)

See Also:

Attachments

Description Patrick Durusau 2015-12-17 20:03:09 UTC 
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.
Comment 1 Josh Spiegel 2015-12-17 20:36:36 UTC 
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?
Comment 2 Jonathan Robie 2015-12-17 20:47:21 UTC 
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
Comment 3 Jonathan Robie 2015-12-17 20:48:52 UTC 
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
Comment 4 Patrick Durusau 2015-12-18 03:36:24 UTC 
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