4717 2007-06-23 10:07:46 +0000 [FT] editorial: 3.5.5 Anchoring Selection 2008-03-03 00:04:52 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Last Call drafts All All CLOSED FIXED P2 minor --- 1 jmdyck pcase public-qt-comments oldest_to_newest 15545 0 jmdyck 2007-06-23 10:07:46 +0000 3.5.5 Anchoring Selection [1] para 1 "An anchoring selection consist of" s/consist/consists/ [2] paras 3-5 'Using the "..." operator tokens or phrases are matched which are' [2a] After "operator", insert comma. [2b] s/which are/that are/ (or "if they are") [2c] Maybe put these paras into a bulleted list. [3] example 2 'The following expression returns each p element ending with the phrase "propagating few errors"' You could point out that it would also match a p element ending with, say, "few errors are propagated". [4] examples It would be instructive to have an example in which the LHS of ftcontains has length>1. 17696 1 doerre 2007-11-13 13:42:31 +0000 Fixed [1]-[3] as proposed. [4] needs some discussion. 18507 2 pcase 2008-01-24 16:08:29 +0000 [4] Resolved by adding the example: <eg role="xpath">/books//* ftcontains "Association" at end</eg> It will return the "content" and the "note" element. Michael, if you agree with this change, please close the bug. 19098 3 jmdyck 2008-02-16 09:55:28 +0000 Re [4]: The spec's style seems to be to preface each example with prose, so the sentence "This example returns true..." should maybe be put before the example and changed to "The following example return true...". Also, "content" and "note" should be in <code> and not quoted. And a follow-up on [3]: The text now says the last example would also yield a match, if the p element would end with say, "few errors are propagated". but should perhaps be the last example would also yield a match if the p element ended with, say, "few errors are propagated". (Comma delete, comma insert, s/would end/ended/.) 19247 4 jmdyck 2008-03-03 00:04:28 +0000 The task force approved the changes in comment #3, and I have applied them to the document, so I'm marking this bug resolved-fixed, and will close it.