28216 2015-03-15 11:57:28 +0000 [XSLT30] XPath 3.0 requires host languages to specify the kind of line ending normalization 2015-10-29 09:50:44 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC Windows NT CLOSED FIXED P2 normal --- 1 abel.braaksma mike public-qt-comments oldest_to_newest 118604 0 abel.braaksma 2015-03-15 11:57:28 +0000 The XPath 3.0 bug 14917, resolved during CR period, introduced the following requirement for host languages of XPath under A.2.3 End-of-Line Handling (http://www.w3.org/TR/xpath-30/#id-eol-handling): <quote> The host language must specify whether the XPath 3.0 processor normalizes all line breaks on input, before parsing, and if it does so, whether it uses the rules of [XML 1.0] or [XML 1.1]. </quote> I tried to search using several keywords for whether we specify that normatively somewhere, but I couldn't find it. I think we ought to add somehow/somewhere specifically how line endings are (not) normalized for XPath expressions to meet this XPath 3.0 requirement (note: the bug also applies to earlier XPath versions and by extension to earlier XSLT versions). 118714 1 mike 2015-03-20 12:53:39 +0000 Subject to WG approval, I have added the following text at the end of section 5.3: <p diff="add" at="S-bug28216">The XPath specification states that the host language must specify whether the XPath processor normalizes all line breaks on input, before parsing, and if it does so, whether it uses the rules of [XML 1.0] or [XML 1.1]. In the case of XSLT, all handling of line breaks is the responsibility of the XML parser (which may support either XML 1.0 or XML 1.1); the XSLT and XPath processors make no further changes.</p> <note><p diff="add" at="S-bug28216">Most XPath expressions in a stylesheet appear within XML attributes. They are therefore subject to XML line-ending normalization (for example, a CRLF sequence is normalized to LF) and also to XML attribute-value normalization, which replaces tabs and newlines by spaces. XPath expressions appearing in text value templates, however (see TVTs) are subject to line-ending normalization but not attribute value normalization). In both cases, normalization of whitespace can be prevented by using character references such as <code>&amp;#x9;</code>.</p></note> 119574 2 mike 2015-04-16 16:56:52 +0000 The changes in comment #1 were accepted.