From leo.studer at varioweb.ch Tue Oct 7 01:07:45 2014 From: leo.studer at varioweb.ch (Leo Studer) Date: Tue, 7 Oct 2014 10:07:45 +0200 Subject: [xquery-talk] xquary update 3.0 Message-ID: hello I am wondering whats happening with the update facility 3.0. Is there any support yet? With Saxon EE 9.5.1.5 in Oxygen and xquery 3.0 enabled, I get errors with updates. Thanks in advance Leo From ghislain.fourny at 28msec.com Tue Oct 7 01:23:43 2014 From: ghislain.fourny at 28msec.com (Ghislain Fourny) Date: Tue, 7 Oct 2014 10:23:43 +0200 Subject: [xquery-talk] xquary update 3.0 In-Reply-To: References: Message-ID: Hi Leo, The XQUF 3.0 specification needs to address a few issues to be adapted for new XQuery 3.0 constructs (e.g., expression categories w.r.t. the introduction of dynamic function invocations). If I am correct, a newer version addressing at least the issue mentioned above may be on its way (but I don't know about any timelines). Mike will probably tell you better than me the status of Saxon with respect to XQUF 3.0. As for the Zorba engine, it should not throw errors in 3.0 for simple update usage. Expect it to be a bit bumpy for dynamic function invocations with updating functions though :-) What queries did you try to run? I hope it helps. Kind regards, Ghislain On Tue, Oct 7, 2014 at 10:07 AM, Leo Studer wrote: > hello > > I am wondering whats happening with the update facility 3.0. > Is there any support yet? > With Saxon EE 9.5.1.5 in Oxygen and xquery 3.0 enabled, I get errors with updates. > > Thanks in advance > Leo > > > > > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk From mike at saxonica.com Tue Oct 7 01:33:00 2014 From: mike at saxonica.com (Michael Kay) Date: Tue, 7 Oct 2014 09:33:00 +0100 Subject: [xquery-talk] xquary update 3.0 In-Reply-To: References: Message-ID: <2C12C390-C2BF-42C3-A997-19AC00E5D5E5@saxonica.com> > hello > > I am wondering whats happening with the update facility 3.0. > Is there any support yet? > With Saxon EE 9.5.1.5 in Oxygen and xquery 3.0 enabled, I get errors with updates. > Saxon 9.5 didn't allow you to use XQuery 3.0 and XQuery Update in the same query. We've fixed that in Saxon 9.6. Michael Kay Saxonica From leo.studer at varioweb.ch Tue Oct 7 02:42:49 2014 From: leo.studer at varioweb.ch (Leo Studer) Date: Tue, 7 Oct 2014 11:42:49 +0200 Subject: [xquery-talk] xquary update 3.0 In-Reply-To: <2C12C390-C2BF-42C3-A997-19AC00E5D5E5@saxonica.com> References: <2C12C390-C2BF-42C3-A997-19AC00E5D5E5@saxonica.com> Message-ID: Thank you Michael I hope 9.6 will be in the next update of Oxygen soon ;-) Yours Leo On 07 Oct 2014, at 10:33, Michael Kay wrote: > >> hello >> >> I am wondering whats happening with the update facility 3.0. >> Is there any support yet? >> With Saxon EE 9.5.1.5 in Oxygen and xquery 3.0 enabled, I get errors with updates. >> > Saxon 9.5 didn't allow you to use XQuery 3.0 and XQuery Update in the same query. > > We've fixed that in Saxon 9.6. > > Michael Kay > Saxonica > From ihe.onwuka at gmail.com Sat Oct 18 10:58:34 2014 From: ihe.onwuka at gmail.com (Ihe Onwuka) Date: Sat, 18 Oct 2014 18:58:34 +0100 Subject: [xquery-talk] format-number problem Message-ID: Given a piece of data like I wanted to zero pad all imdbID attributes to length 7. So i did this / { @rtID, attribute imdb_id {format-number(@imdbID,'0000000')} } Now it's quite possible that I asked for the wrong thing but leave that aside for a sec. In this particular example the desired outcome is that the data returns unchanged since it is already the requisite length. But in eXist I get and in Zorba I get -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.gruen at gmail.com Sat Oct 18 11:18:49 2014 From: christian.gruen at gmail.com (=?UTF-8?Q?Christian_Gr=C3=BCn?=) Date: Sat, 18 Oct 2014 20:18:49 +0200 Subject: [xquery-talk] format-number problem In-Reply-To: References: Message-ID: > / > { > @rtID, > attribute imdb_id {format-number(@imdbID,'0000000')} > } I tried to other processors, and the result I got was? ?so I looks more an implementation issue. Best, Christian From benito at benibela.de Sun Oct 26 10:52:21 2014 From: benito at benibela.de (Benito van der Zander) Date: Sun, 26 Oct 2014 19:52:21 +0100 Subject: [xquery-talk] XQuery 3.1 and the version declaration in a query Message-ID: <544D42E5.3070509@benibela.de> Hi, A query can start with xquery version "..." to set a specific version. Is xquery version "3.1"; valid? What should a XQuery processor that understands 3.1 do, if the query starts with xquery version "3.0"; but contains expressions that are only valid in 3.1 and not in 3.0? Benito From christian.gruen at gmail.com Sun Oct 26 10:59:58 2014 From: christian.gruen at gmail.com (=?UTF-8?Q?Christian_Gr=C3=BCn?=) Date: Sun, 26 Oct 2014 19:59:58 +0100 Subject: [xquery-talk] XQuery 3.1 and the version declaration in a query In-Reply-To: <544D42E5.3070509@benibela.de> References: <544D42E5.3070509@benibela.de> Message-ID: > Is xquery version "3.1"; valid? I think it should be (although it seems not to be mentioned in the current version of the spec [1]). > What should a XQuery processor that understands 3.1 do, if the query starts > with xquery version "3.0"; > but contains expressions that are only valid in 3.1 and not in 3.0? The spec offers three alternatives: * Process the module using the specification of the XQuery version identified in the version declaration. * Process the module using the specification of XQuery 3.0. (? 3.1) * Raise a static error [err:XQST0031] Hope this helps, Christian [1] http://www.w3.org/TR/2014/WD-xquery-31-20141007/#id-version-declaration From benito at benibela.de Sun Oct 26 12:07:36 2014 From: benito at benibela.de (Benito van der Zander) Date: Sun, 26 Oct 2014 21:07:36 +0100 Subject: [xquery-talk] XQuery 3.1 and the version declaration in a query In-Reply-To: References: <544D42E5.3070509@benibela.de> Message-ID: <544D5488.6030608@benibela.de> Hi Christian, > The spec offers three alternatives: > > * Process the module using the specification of the XQuery version > identified in the version declaration. > * Process the module using the specification of XQuery 3.0. (? 3.1) > * Raise a static error [err:XQST0031] But these are the alternatives for > If an XQuery 3.0 processor processes a module labeled with a version of "1.0", it must do one of the following: How do we know that they also apply to an XQuery 3.1 processor ? Bye, Benito On 10/26/2014 07:59 PM, Christian Gr?n wrote: >> Is xquery version "3.1"; valid? > I think it should be (although it seems not to be mentioned in the > current version of the spec [1]). > >> What should a XQuery processor that understands 3.1 do, if the query starts >> with xquery version "3.0"; >> but contains expressions that are only valid in 3.1 and not in 3.0? > The spec offers three alternatives: > > * Process the module using the specification of the XQuery version > identified in the version declaration. > * Process the module using the specification of XQuery 3.0. (? 3.1) > * Raise a static error [err:XQST0031] > > Hope this helps, > Christian > > [1] http://www.w3.org/TR/2014/WD-xquery-31-20141007/#id-version-declaration > > From mike at saxonica.com Sun Oct 26 12:49:01 2014 From: mike at saxonica.com (Michael Kay) Date: Sun, 26 Oct 2014 20:49:01 +0000 Subject: [xquery-talk] XQuery 3.1 and the version declaration in a query In-Reply-To: <544D42E5.3070509@benibela.de> References: <544D42E5.3070509@benibela.de> Message-ID: I raised the issue recently here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27094 No doubt the next draft will say exactly what should happen. Michael Kay Saxonica mike at saxonica.com +44 (0) 118 946 5893 On 26 Oct 2014, at 18:52, Benito van der Zander wrote: > Hi, > A query can start with xquery version "..." to set a specific version. > > Is xquery version "3.1"; valid? > > What should a XQuery processor that understands 3.1 do, if the query starts with xquery version "3.0"; > but contains expressions that are only valid in 3.1 and not in 3.0? > > > Benito > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk