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 2298 - Precise semantics of double negation (formerly Cluster G, Issue 62)
Summary: Precise semantics of double negation (formerly Cluster G, Issue 62)
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Working drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Jochen Doerre
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-25 19:10 UTC by Jim Melton
Modified: 2005-11-07 15:37 UTC (History)
0 users

See Also:

Attachments

Description Jim Melton 2005-09-25 19:10:34 UTC 
Currently, (! ! Q) does not produce the same AllMatches as (Q). There seem to be
two reasons for that. First, there are duplicate StringIncludes, StringExcludes,
and Matches. Second, there are Matches that are subsumed by other Matches (i.e.
the former are a logical consequence of the latter). How do we handle these
situations? It seems reasonable to expect that !!Q produces the same result as Q.
Comment 1 Jochen Doerre 2005-11-07 15:31:17 UTC 
AllMatches returned for FTSelections are subject to a Normal Form now, by which
it is insured that (! ! Q) behaves equivalent in all contexts to (Q) (see
Section 4.3.1.4 Match and AllMatches Normal Form)