1630 2005-07-15 15:36:33 +0000 Issue: booleannaming 2005-09-29 10:27:02 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Working drafts PC Windows 2000 CLOSED WONTFIX P2 normal --- 1 davidc sihem public-qt-comments oldest_to_newest 4708 0 davidc 2005-07-15 15:36:33 +0000 Issue: booleannaming, priority: , status: open I agree with the suggestion listed in this issue that ftand and ftor would be preferable to && and || && has problems in XPath as that's often used in XML so would have to be &amp;&amp; XPath already makes use of < but there's no need to make the sitation worse, and a query using full text search is likely to make a lot of use of && || can easily be misread as |. 6484 1 pcase 2005-09-27 11:36:17 +0000 The Full-Text Task Force (FTTF) was advised that it could not change "&&", "||", "!" in XQuery and XPath Full-Text to "and", "or", "not" without producing conflicts with XQuery. At the last Face-to-Face, the FTTF decided not to change from "&&", "||", "!" to "ftand", "ftor", "ftnot". The majority of the FTTF prefers the symbolic notation. The FTTF realizes that the ampersands will need to be escaped if a query is placed in an URL, but considers that manageable. This is the official FTTF response. Please let us know if you agree with this resolution by adding a comment to the issue record and changing the Status of the issue to Closed. Or, if you do not agree with this resolution, please add a comment explaining why. 6485 2 davidc 2005-09-27 11:44:43 +0000 The spec asked for comments on this issue and I commented but I have no formal objection to any resolution. > the FTTF realizes that the ampersands will need to be escaped if a > query is placed in an URL, but considers that manageable. Putting a full text query in a URL might be rather rare, a more common requirement is likely to be to put an xpath+ft into an XML document, but &amp;&amp; isn't impossible, people will live with it.