W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2008

[Bug 6304] New: attribute value tokenization

From: <bugzilla@wiggum.w3.org>
Date: Fri, 12 Dec 2008 08:38:14 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-6304-523@http.www.w3.org/Bugs/Public/>


           Summary: attribute value tokenization
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
               URL: http://www.w3.org/TR/xpath-full-text-10
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Full Text 1.0
        AssignedTo: jim.melton@acm.org
        ReportedBy: peter.pleshachkov@gmail.com
         QAContact: public-qt-comments@w3.org

Dear authors,

It looks like the example from 3.6.2 Window Selection is not correct.

"The following expression returns true, because the title element contains "Web
Site Usability". A similar query on the p element would not return true,
because its occurrences of "web site" and "usability" are not within a window
of 3:

/books/book//title ftcontains "web site" ftand
"usability" window 3 words

But, actually the "Web Site Usavility" is the value of an attribute :
shortTitle="Improving Web Site Usability"

But in the spec you say that
"but it occurs in an attribute value, and so is not subject to tokenization."

And in section 4.1.1 Examples you have an example:

<p kind='secret'>Sensitive material <!-- secret --></p> ftcontains 'secret'

"the following example must return false, because the 'secret' only occurs
within an attribute and a comment, neither of which contributes characters to
the string value of the 'p' element node:"

Kind regards,
Peter Pleshachkov

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 12 December 2008 08:43:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:38 UTC