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 4668 - [Full text LC draft sec. 3.2] Examples with "because" need a change
Summary: [Full text LC draft sec. 3.2] Examples with "because" need a change
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-20 07:07 UTC by Felix Sasaki
Modified: 2008-02-12 00:51 UTC (History)
0 users

See Also:

Attachments

Description Felix Sasaki 2007-06-20 07:07:03 UTC 
The examples in this section contain statements like

"The following expression returns the book element whose number is 1, because ..."

I think that, given the XPath expressions in the examples, the statements should be like:

"The following expression returns the book element whose number is 1 and ..."
Comment 1 Jochen Doerre 2007-08-06 11:17:53 UTC 
Hi Felix,

thanks for pointing this out. We have discussed your suggestion in the task force and agreed to change the text.
I have fixed the explanations of the 3 examples to which this relates slightly different than you suggested, since I wanted to directly refer to effect of these examples if evaluated against the sample document we provide. 

The text now reads:
The following expression returns the sample book element, because its number attribute is 1 and its title element contains the token "Expert":

/book[@number="1" and ./title ftcontains "Expert"]

... and likewise for the other examples.
Does this address your concern? If yes, please close the bug.

Kind Regards,
/Jochen Doerre (on behalf of the FTTF)
Comment 2 Felix Sasaki 2008-02-12 00:51:49 UTC 
Apologies for late reply, I did not see the comment at
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4668#c1
I'm fine with this bug being closed.

Felix