W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2006

[Bug 3419] AllMatches model fails to represent correct semantics of FTUnaryNot

From: <bugzilla@wiggum.w3.org>
Date: Fri, 07 Jul 2006 00:12:11 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Fydx5-0007ia-Sq@wiggum.w3.org>


joaquin.delgado@oracle.com changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

------- Comment #1 from joaquin.delgado@oracle.com  2006-07-07 00:12 -------
This standalone UnaryNot does not have a bug.

The negation of an empty <allMatches> is not an empty <allMatches> but an
<allMatches> with one empty <match>. That is clear in the definition of
fts:UnaryNotHelper. It populates <match/> when there is no <match> in
<allMatches>. This empty <match> element satisfies fts:FTContainsExpr because
it has no <stringExclude>. So, ftcontains returns TRUE as expected.


Received on Friday, 7 July 2006 00:12:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:13 UTC