- From: Abel Braaksma <abel.braaksma@xs4all.nl>
- Date: Tue, 28 Jun 2016 13:18:25 +0200
- To: "'C. M. Sperberg-McQueen'" <cmsmcq@blackmesatech.com>, "'Public Joint XSLT XQuery XPath'" <public-xsl-query@w3.org>
> -----Original Message----- > From: C. M. Sperberg-McQueen [mailto:cmsmcq@blackmesatech.com] > Sent: Saturday, June 25, 2016 10:10 PM > > > So, I would assume that normalization does *not* take place (I will raise an > > XPath bug for this, as the specs seems to disagree on this amongst each > > other). > > No, I don't think so. The XPath spec is consistent with XSD here, I think. I agree now, I was mistaken. I found it hard to find the definitive verdict, browsing through the specs, while a line in the XPath spec clearly suggests the whitespace normalization taking place. > > > > > In short: I agree with your assessment that whitespaces SHOULD be > > allowed > > I don't think I said that, at least not in the sense that I think it's a good idea > to allow whitespace in URIs or to allow whitespace within the brackets in > an EQName. I think I said that the XPath grammar currently seems > to allow them, and that I believe the schema for serialization parameters > should align with the XPath grammar. Yes, I misunderstood. So we should allow them in the serialization-XSD.
Received on Tuesday, 28 June 2016 11:18:59 UTC