https://www.w3.org/Bugs/Public/show_bug.cgi?id=28024 --- Comment #2 from Patrick Durusau <patrick@durusau.net> --- Thanks! You make my case better than I could. If "string" is being defined and then used differently in the case I cited, it is even more of a problem. Or are you saying that sometimes XPath 3.1 relies on XDM definitions and at other times it doesn't? (a different problem than the one I posed) "string" cannot (should not) be defined to mean one thing and then used to mean a variety of other things. In general that is why standards have definitions, to fix the meaning of terms. Perhaps a definition that conflicts with usage would have been more accurate. -- You are receiving this mail because: You are the QA Contact for the bug.Received on Saturday, 14 February 2015 16:26:32 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:52 UTC