- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 16 Apr 2009 19:06:19 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6802 Pat Case <pcase@crs.loc.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #3 from Pat Case <pcase@crs.loc.gov> 2009-04-16 19:06:19 --- Christian, [9] full-text-composability-queries-results-q5.xq My parser still seems to complain about the new version; the following return statement might do its job: return <book number="{$book/@number}">{ ($title, if (count($book/metadata/author) > 0) then ($book/metadata/author, $in, $pin) else ($book/metadata/publicationInfo/publisher, $in, $pin)) }</book> --I added the comma after $title and the parens you suggested. Done in test suite and use cases. [10] xquery-xpath-composability-queries-results-q9.xq Sorry, I didn't write too much on this. "./part/chapter" is grammatically correct, but no context item is defined at this point, leading to an XPDY0002 error. This is why I suggested to replace "." with "$cont". --Mary assisted me with these and she recommended I change the period to $cont and I have so done. Part of her explanation is: "The use of the term "context item" suggests that we do bind the context item to the search context item, in which case the "." would be OK. On the other hand, we don't come out and say so explicitly..." Pat -- 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 Thursday, 16 April 2009 19:06:29 UTC