- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Feb 2016 14:23:18 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29479 --- Comment #1 from Michael Kay <mike@saxonica.com> --- >I would challenge that in this case the error can be ignored, because the xsl:copy is shallow-copying the <root> element. To complete that copy it needs to read through to the end. Why? To shallow-copy an element you only need to know the name of the element. Shallow-copy doesn't (intrinsically) depend on the content of the element or on anything found in its end-tag. >I am wondering if we can make this more interoperable. For instance by requiring an option to at least [read] through to the end. I'm reluctant. It's an intrinsic property of functional languages that you don't read more input than is needed to compute the output. If the user wants a complete well-formedness or validity check then they can always add one to the processing pipeline. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 18 February 2016 14:23:21 UTC