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

[Bug 6304] [FT] attribute value tokenization

From: <bugzilla@wiggum.w3.org>
Date: Mon, 22 Dec 2008 02:24:22 +0000
To: public-qt-comments@w3.org
Message-Id: <E1LEaT0-000371-7s@farnsworth.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6304


Jim Melton <jim.melton@acm.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




--- Comment #1 from Jim Melton <jim.melton@acm.org>  2008-12-22 02:24:21 ---
[personal response]

Peter, thanks for your comment.  It's gratifying to know that you're reviewing
the spec so thoroughly. 

We have discovered (because of other comments, for example) that our
explanation of tokenization is somewhat confusing.  We have adopted changes to
that explanation that will be visible when we publish the next revision of the
CR document. 

In the first example, you observe that:

   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."

The way that tokenization is intended to work is basically this: If a query
explicitly requests to search within an attribute value, then the value of the
attribute is tokenized and its tokens are the subject of the search.  However,
if a query requests to search within element content only, the values of any
attributes are not included in the search context and are therefore not
subjects of the search. 

This is now clearly stated in Section 4.1, Tokenization, in list item 2, which
reads:

   2. Tokenization of an item MUST include only tokens derived from the string
value of that item. The string value is defined in [XQuery 1.0 and XPath 2.0
Data Model] in Section 2.6.5 String Values; for element nodes it does not
include the contents of attributes, but for attribute nodes it does.


Therefore, I believe that the example in 3.6.2 Window Selection is correct as
written and as explained.  Because this response has not been reviewed by the
groups, I am not marking the comment INVALID, but I expect that will be the
decision of the groups. 


-- 
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 Monday, 22 December 2008 02:24:32 UTC

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