This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1630 - Issue: booleannaming
Summary: Issue: booleannaming
Status: CLOSED WONTFIX
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Working drafts
Hardware: PC Windows 2000
: P2 normal
Target Milestone: ---
Assignee: Sihem Amer-Yahia
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-15 15:36 UTC by David Carlisle
Modified: 2005-09-29 10:27 UTC (History)
0 users

See Also:

Attachments

Description David Carlisle 2005-07-15 15:36:33 UTC 
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 |.
Comment 1 Pat Case 2005-09-27 11:36:17 UTC 
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.
Comment 2 David Carlisle 2005-09-27 11:44:43 UTC 
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.