8409 2009-12-01 13:25:26 +0000 WS Q2 - Scripting Expression in LET 2010-01-18 22:26:10 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Scripting Extensions 3.0 Requirements and Use Cases Working drafts All All CLOSED FIXED P2 normal --- 1 peter.fischer john.snelson public-qt-comments oldest_to_newest 29859 0 peter.fischer 2009-12-01 13:25:26 +0000 In the main document, 2.4.2 "FLWOR Expressions" states that let (for, where, ...) must contain either simple or updating expressions. In the Use Case "WS" - XQuery for Web Services, Q2 defines a sequential function local:check-user-and-log($username as xs:string). This function is used in a FLWOR expression in the main query: let $user := replace($request/url, "^http://.*/([^/]+)/add$", "$1") let $blog := local:check-user-and-log($user) return ( .... If my understanding is right and the semantics have not changed from what is currently stated in the documents, I'd suggest moving these two variables into a block, where variable initializers might be sequential expressions. 30677 1 john.snelson 2010-01-06 16:06:28 +0000 Hi Peter, Thanks for your comments - that's definitely a bug in the published use cases. However the expression category rules will change again in the next working draft, and I believe this use case will become legal. John 30988 2 john.snelson 2010-01-12 17:36:49 +0000 The XQuery WG discussed this on January 12th, and agreed that this bug has already been rendered moot by changes yet to be published in the XQuery SX specification. If you agree with this resolution, please go ahead and close this bug.