- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 11 May 2006 10:44:34 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3201 ------- Comment #3 from david_marston@us.ibm.com 2006-05-11 10:44 ------- I'm not satisfied with the resolution. Even in the F&O document, there is no mention in 15.5.2 (in the CR), only in a non-normative appendix. But I was hoping for a note in the XPath document, definitely in Appendix I and maybe also in 3.1.5, which is where I realized the incompatibility. For example, the note in 3.1.5 could be: NOTE: When an argument signature is disqualified from 1.0 compatibility rules for any reason (e.g., different occurrence indicator), the argument is disqualified for all compatibility conversion (e.g., type conversion). My concern is that I was looking at XPath in a frame of mind where I was thinking about casting boolean to string, but the answer came from an orthogonal concern. If the specs don't point it out, then they are more vulnerable to critics saying there are traps and gotchas in there.
Received on Thursday, 11 May 2006 10:44:38 UTC