From burnside@kattare.com Thu May 1 07:16:42 2003 Received: from pyramid-01.kattare.com (pyramid-01.kattare.com [206.163.128.20]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h41EGgIG010801 for ; Thu, 1 May 2003 07:16:42 -0700 Received: from localhost (localhost [127.0.0.1]) by pyramid-01.kattare.com (8.12.8/8.12.3) with ESMTP id h41GrUYK002851 for ; Thu, 1 May 2003 09:53:30 -0700 Received: from 65.212.181.200 ( [65.212.181.200]) as user burnside@mail.kattare.com by www.kattare.com with HTTP; Thu, 1 May 2003 09:53:30 -0700 Message-ID: <1051808010.3eb1510a4c794@www.kattare.com> Date: Thu, 1 May 2003 09:53:30 -0700 From: Ethan Burnside To: talk@x-query.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-MailScanner: Found to be clean X-MailScanner-Information: Please contact your ISP for more information - Be sure to include all mail headers X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-7.1, required 5, BAYES_01, USER_AGENT_IMP) Subject: [Talk] test X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 14:16:42 -0000 -- -------------------------- Ethan Burnside - Founder Kattare Internet Services http://www.kattare.com -------------------------- From burnside@kattare.com Thu May 1 13:53:42 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h41KrYST011127 for ; Thu, 1 May 2003 13:53:42 -0700 Received: from pyramid-02.kattare.com (pyramid-02.kattare.com [206.163.128.3]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h41NX8WC014175 for ; Thu, 1 May 2003 16:33:08 -0700 Received: from localhost (localhost [127.0.0.1]) by pyramid-02.kattare.com (8.12.8/8.12.3) with ESMTP id h41NX7ZT028408 for ; Thu, 1 May 2003 16:33:07 -0700 Received: from 65.212.181.200 ( [65.212.181.200]) as user burnside@mail.kattare.com by www.kattare.com with HTTP; Thu, 1 May 2003 16:33:07 -0700 Message-ID: <1051831987.3eb1aeb32ab00@www.kattare.com> Date: Thu, 1 May 2003 16:33:07 -0700 From: Ethan Burnside To: talk@x-query.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-MailScanner: Found to be clean X-MailScanner-Information: Please contact your ISP for more information - Be sure to include all mail headers X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-7.1, required 5, BAYES_01, USER_AGENT_IMP) Subject: [Talk] test X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 20:53:42 -0000 -- -------------------------- Ethan Burnside - Founder Kattare Internet Services http://www.kattare.com -------------------------- From jhunter@servlets.com Fri May 2 17:53:07 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h430r7ST012298 for ; Fri, 2 May 2003 17:53:07 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h433jWbH000492 for ; Fri, 2 May 2003 20:45:32 -0700 (PDT) Message-ID: <3EB33A91.7A9A976B@servlets.com> Date: Fri, 02 May 2003 20:42:09 -0700 From: Jason Hunter X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: talk@x-query.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [xquery-talk] Test X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 00:53:08 -0000 Testing the new list config. -jh- From stephen.buxton@oracle.com Tue May 6 08:17:07 2003 Received: from inet-mail3.oracle.com (inet-mail3.oracle.com [148.87.2.203]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h46FH7ST016227 for ; Tue, 6 May 2003 08:17:07 -0700 Received: from inet-mail3.oracle.com (localhost [127.0.0.1]) by inet-mail3.oracle.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h46ImVo27602 for ; Tue, 6 May 2003 11:48:31 -0700 (PDT) Received: from rgmgw5.us.oracle.com (rgmgw5.us.oracle.com [138.1.191.14]) by inet-mail3.oracle.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h46ImUj27558 for ; Tue, 6 May 2003 11:48:30 -0700 (PDT) Received: from rgmgw5.us.oracle.com (localhost [127.0.0.1]) by rgmgw5.us.oracle.com (Switch-2.1.5/Switch-2.1.0) with ESMTP id h46ImSw06502 for ; Tue, 6 May 2003 12:48:28 -0600 (MDT) Received: from rgmum12.us.oracle.com (rgmum12.us.oracle.com [138.1.191.16]) by rgmgw5.us.oracle.com (Switch-2.1.5/Switch-2.1.0) with ESMTP id h46ImLg06265 for ; Tue, 6 May 2003 12:48:26 -0600 (MDT) Received: from dhcp-4op7-4op8-west-130-35-170-61.us.oracle.com by rgmum3.us.oracle.com with ESMTP id 142785351052246726; Tue, 06 May 2003 12:45:26 -0600 Message-ID: <3EB801F8.E11FDD80@oracle.com> Date: Tue, 06 May 2003 11:42:01 -0700 From: Stephen Buxton Organization: Oracle Corporation X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: xquery talk Content-Type: multipart/mixed; boundary="------------53784A65D1792C7D4B72B82B" X-Mailman-Approved-At: Tue, 06 May 2003 17:01:27 -0700 Subject: [xquery-talk] confirm be84b5b42f5f3d5d496a8569107f581ec18b0628 X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 15:17:07 -0000 This is a multi-part message in MIME format. --------------53784A65D1792C7D4B72B82B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit confirm be84b5b42f5f3d5d496a8569107f581ec18b0628 --------------53784A65D1792C7D4B72B82B Content-Type: text/x-vcard; charset=us-ascii; name="stephen.buxton.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Stephen Buxton Content-Disposition: attachment; filename="stephen.buxton.vcf" begin:vcard n:Buxton;Stephen tel;fax:650 633 2230 tel;work:650-506-2469 x-mozilla-html:FALSE url:http://sbuxton-sun.us.oracle.com org:DAST;Server Technologies adr:;;;;;; version:2.1 email;internet:stephen.buxton@oracle.com title:Director, Text and XML PM x-mozilla-cpt:;-13120 fn:Stephen Buxton end:vcard --------------53784A65D1792C7D4B72B82B-- From srinivas@ipedo.com Tue May 6 13:08:05 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h46K85ST016489 for ; Tue, 6 May 2003 13:08:05 -0700 Received: from mail.ipedo.com (ip-216-36-69-83.dsl.sjc.megapath.net [216.36.69.83]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h46NfdDe012744 for ; Tue, 6 May 2003 16:41:39 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01C31429.08E6788C" X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Date: Tue, 6 May 2003 16:41:37 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Latest drafts.... Thread-Index: AcMUKQiYZ/bpQhlmT+qozoqtD+Tezg== From: "Srinivas Pandrangi" To: "Talk@X-Query. Com (E-mail)" X-Mailman-Approved-At: Tue, 06 May 2003 17:01:27 -0700 Subject: [xquery-talk] Latest drafts.... X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 20:08:05 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C31429.08E6788C Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C31429.08E6788C" ------_=_NextPart_002_01C31429.08E6788C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In case anybody missed it, the latest drafts of most of the xquery spec documents were published on May 2nd (http://www.w3.org/XML/Query). Two of the drafts (Data Model & Functions and Operators) are now in last call. Check them out. --Srinivas <>=20 Srinivas Pandrangi Ipedo Inc. [http://www.ipedo.com] Ph: (650) 306 4002 Fax: (650) 306 4001 ------_=_NextPart_002_01C31429.08E6788C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Latest drafts....

In case anybody missed it, the latest = drafts of most of the xquery spec documents were published on May 2nd = (http://www.w3.org/XML/Query). = Two of the drafts (Data Model & Functions and Operators) are now in = last call. Check them out.

--Srinivas

3D"ole0.bmp"
Srinivas Pandrangi
Ipedo Inc. [http://www.ipedo.com]
Ph: (650) 306 4002
Fax: (650) 306 4001

------_=_NextPart_002_01C31429.08E6788C-- ------_=_NextPart_001_01C31429.08E6788C Content-Type: image/bmp; name="ole0.bmp" Content-Transfer-Encoding: base64 Content-Description: ole0.bmp Content-Location: No%20AttachName Qk0OFgAAAAAAAOoAAAAoAAAAhAAAACkAAAABAAgAAAAAAAAAAAAAAAAAAAAAAC0AAAAAAAAAAAAA AG6g/wBuoG4A0ND/ADoAAACgoP8A/9D/ABUVFQDQoP8A///QAAA6OgBubjoAOjo6AG46OgCgoKAA sLCwAAA6AADQoKAAoNDQAMDAwAA6OgAA0NDQAH9/fwCgoNAA4ODgAI+PjwAAbv8AOm7/ACgoKAAA Ov8Abm7/AG5ubgA6Ov8AOjpuAG46bgDQ//8A7+/vAP///wBdXV0AAAA6ADoAOgBubqAATExMAKBu oACg0P8AJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUGJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSMlJQklJSUjJSUGJSUJJSUlJSUlJQklJSUlBiUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUYCRUVCRUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJR8UDAoVJSUlJR8nCigjJSUlJSUlJSUlJSUlJSUlJSUlJSUDCigMACgKAAoAKBQMJxQQDAQK FBMlJSUlFQwKBCgnFAQKBAwhCx8RFSUlJSUlJSUlJSUlJSUlJRUCDQwAAAAAACcUDCkXJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJRcAAAACJSUlJQ8AAAAOJSUlJSUlJSUlJSUlJSUlJSUlJSUl DAAAAAAAAAAAAAAAAAAAAAAAACIlJSUlJRQAAAAAAAAAAAAAAAAAAAwCGCUlJSUlJSUlJSUVIQAA AAAAAAAAAAAAAAAAEB8jJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSMEAAAKJSUlJQYAAAAhIyUl JSUlJSUlJSUlJSUlJSUlJSUlGQAAAAwZKw8ZKw4ZFw4ODisOGQ4lJSUlJSsAAAAfDhkZDhkfHwwA AAAAACIVJSUlJSUlJQMAAAAAACgpDhMTEw8rIQoAAAAACxUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUhAAAAFSUlJSULAAAACSUlJSUlJSUlJSUlJSUlJSUlJSUlFQAAAA0lJSUlJSUlJSUlJSUlJSUl JSUlJRIAAAAZJSUlJSUlJSUjDwwAAAAnEiUlJSUlCSgAAAAAGSUlJSUlJSUlJQYZBAAAABQVJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSURAAAAGSUlJSUSAAAADiUlJSUlJSUlJSUlJSUlJSUlJSUlJQwA AAAYJSUlJSUlJSUlJSUlJSUlJSUlJSUMAAAoJSUlJSUlJSUlJSUTDAAAABYlJSUlDwAAAAALJSUl JSUlJSUlJSUlIw0AAAAAFyUlJSUlJSUlJSUlJSUlJSUlJSUlJSUGAAAACiUlJSUYCgAADBgjGCMY GCMYIwYlJSUlJSUlJSUlJQ4AAAArJSUlJSUlJSUlJSUlJSUlJSUlJSUWAAAAGCUlJSUlJSUlJSUl IxQAAAAOJSUlGQAAAAAVJSUlJSUlJSUlJSUlJSUNAAAABBUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl CwAAABMlJSUlHwAAAAAAAAAAAAAAAAAAKA0OFSUlJSUlJRgQAAAKJSUlJSUlJSUlJSUlJSUlJSUl JSUVAAAAFiUlJSUlJSUlJSUlJRgAAAAKGCUlKwAAAAAYJSUlJSUlJSUlJSUlJSUJCgAAAAwlJSUl JSUlJSUlJSUlJSUlJSUlJSUlDgAAABklJSUlEwAAAAAAAAAAAAAAAAAAAAAAACERJSUlJSUqAAAA KgwhKgwhDAwLJSUlJSUlJSUlJSUlKAAADCUlJSUlJSUlJSUlJSUfAAAADiUlDgAAAAAOJSUlJSUl JSUlJSUlJSUlKwAAAAAYJSUlJSUlJSUlJSUlJSUlJSUlJSUlIwoAAAQlJSUlIygAACgVFSMVGAMY AxUVEw4NAAAAHwklJSUOAAAAAAAAAAAAAAAAFSUlJSUlJSUlJSUlGQAAABUlJSUlJSUlJSUlJSUV AAAADCUlJRAAAAAqJSUlJSUlJSUlJSUlJSUlFQAAAAAfJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSIA AAATJSUlJR8AAAADJSUlJSUlJSUlJSUlDgAAACElJSUjJwAAABYpHx8fHysfGCUlJSUlJSUlJSUl FQAAABklJSUlJSUlJSUlJSUGAAAACiUlJRkAAAAADyUlJSUlJSUlJSUlJSUlAxQAAAAmJSUlJSUl JSUlJSUlJSUlJSUlJSUlJQ8AAAAfJSUlJRMAAAAOJSUlJSUlJSUlJSUlJRkAAAATJSUlDAAAABUl JSUlJSUlJSUlJSUlJSUlJSUlJRQAABQlJSUlJSUlJSUlJSUTAAAADAYlJSUiAAAAJxUlJSUlJSUl JSUlJSUlGAAAAAAMJSUlJSUlJSUlJSUlJSUlJSUlJSUlJQYUAAAKJSUlJQYMAAAMJSUlJSUlJSUl JSUlJRMAAAAfJSUlDgAAAB8lJSUlJSUlJSUlJSUlJSUlJSUlJQ4AAAATJSUlJSUlJSUlJQYKAAAA ISUlJSUjDAAAABATJSUlJSUlJSUlJSUlKQAAAAAOJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUmAAAA FSUlJSUfAAAAFSUlJSUlJSUlJSUlCSYAAAApJSUlGAoAAAwlJSUlJSUlJSUlJSUlJSUlJSUlJQMA AAAfJSUlJSUlJSUVGQAAAAAAFSUlJSUlJSIAAAAAKhIlJSUlJSUlJQkfAAAAAAAGJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUTAAAAHyUlJSUTAAAAFB8CFhYCGR8CFgIqAAAAACgJJSUlJQsAAAAoHyIm CyIfHx8LIiYfIh8DJSUlJSUMAAAADB8WHyELKgAAAAAAABQTJSUlJSUlJSUXFAAAAAAQIR8ZGSsf IQAAAAAABBUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlAAAAFAYlJSUlFAAAAAAAAAAAAAAAAAAA AAAAIRUlJSUlJQ4AAAAAAAAAAAAAAAAAAAAAAAARJSUlJSUPAAAAAAAAAAAAAAAAAAAMKSMlJSUl JSUlJSUlJRINAAAAAAAAAAAAAAAAAAAfBiUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlGQsiJhUl JSUlDioiIQ0MKiIMCyEMIioWGRMjJSUlJSUlJSMLKiIiKiIqDSoiCyEiIQwiCyEpJSUlJSUYDCEh DCIhIQsMHx8OFxglJSUlJSUlJSUlJSUlJSUlJQ8ZIgwUACcUJwwfEyMlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlBgklJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSMlAyUDIyMDAwMDAywsBSwFBQMF AR4BAR4BHh4lJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlAwMD AwMILCwFCAUBAQUeARseGxsbGxseIBogGh0sJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlIyUlIyUlAyMDIyMDBgMDAwMDAywDLCws LAUFBQUFBSwFAQUBAQEeAQEeBR4BAQEbLCUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlAwMDIwMDLAMFLCwsCCwFBQEF ASwBCAEBHgEeAR4BAR4bHgEbHgEbHhsbGxsbHhsgGx0bIBsaGx0dHR0gGyUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlAwYlAwYD AwMDAwMsLAMFJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJQMDAyMDLAUFBQUBHgEe AR4bGxsbGx0dHR0dHR0dHR0dHR0dHRodHRodGyUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUDIwYjAwMDAwMDLCUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl JSUl ------_=_NextPart_001_01C31429.08E6788C-- From jhunter@servlets.com Mon May 12 08:08:10 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4CF89ST022379 for ; Mon, 12 May 2003 08:08:09 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h4CJstbH002732 for ; Mon, 12 May 2003 12:54:56 -0700 (PDT) Message-ID: <3EBFFB60.AAB18B32@servlets.com> Date: Mon, 12 May 2003 12:52:00 -0700 From: Jason Hunter X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: talk@x-query.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [xquery-talk] Welcome! X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2003 15:08:10 -0000 Hi everyone, Thanks for joining up on this list! I'm going to go public with the list today and get things started. I plan to write announcements to www-ql, xml-dev, and jdom-interest. Ron Bourret said he'd write to xml-dbms for me. If you know of other lists where interested people hang out, please send an invite or forward on my emails. -jh- From jhunter@servlets.com Mon May 12 08:10:32 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4CFAWST022392 for ; Mon, 12 May 2003 08:10:32 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h4CJvMbH002735 for ; Mon, 12 May 2003 12:57:22 -0700 (PDT) Message-ID: <3EBFFBF2.75CC1C14@servlets.com> Date: Mon, 12 May 2003 12:54:26 -0700 From: Jason Hunter X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: talk@x-query.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [xquery-talk] Best engine for learning? X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2003 15:10:32 -0000 One of the first topics I'd like to cover is this: What's the best XQuery engine to learn on? I foresee this question being asked by a lot of newbies here, and I frankly don't know the answer. It feels like there's an XQuery FAQ to be written and this is Question One, but no one knows the answer yet. :-) Here's the criteria I'd use to judge: 1) The engine must be readily downloadable and available for extended experimental use without a fee. I see having to write to sales@vendor.com for a copy as an impediment to experimentation. A 30-day eval license is perhaps OK but it'd be better to have a license which allowed extended non-deployment experimentation. 2) The engine must be rigorously faithful to the specs. People shouldn't learn bad habits. 3) The engine should be simple to setup and must be usable without a large number of non-XQuery pieces. The more unadorned the XQuery feature, the better for learning. 4) The engine should have good, accurate error reporting. I know how frustrating "Nope, try again" errors can be. 5) The engine need not scale or be high performant. In my own exploration, I've had good luck with Cerisent. However, Cerisent doesn't expose an evaluation download. Ipedo XML Database 3.2 had some problems and so I'm now waiting for the follow-on where I'm told all my problem reports have been fixed. I've heard some good things said recently about Fatdog's XQEngine. Has anyone experimented there? -jh- From per@bothner.com Mon May 12 11:22:58 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4CIMvST022604 for ; Mon, 12 May 2003 11:22:57 -0700 Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4CNZiGS012674 for ; Mon, 12 May 2003 16:35:44 -0700 Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out2.apple.com (8.12.9/8.12.9) with ESMTP id h4CNZlnB019933 for ; Mon, 12 May 2003 16:35:47 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Mon, 12 May 2003 16:35:46 -0700 Received: from bothner.com (il0102a-dhcp62.apple.com [17.201.27.190]) by scv3.apple.com (8.12.9/8.12.9) with ESMTP id h4CNZkRM001169 for ; Mon, 12 May 2003 16:35:46 -0700 (PDT) Message-ID: <3EC0300F.9040306@bothner.com> Date: Mon, 12 May 2003 16:36:47 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@x-query.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xquery-talk] Re: Best engine for learning? X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2003 18:22:58 -0000 > One of the first topics I'd like to cover is this: What's the best > XQuery engine to learn on? I haven't tried other implementations, but here are some reasons to consider my own Qexo engine. Of course I'm biased, but at least when it comes to Qexo I know of what I speak! > 1) The engine must be readily downloadable and available for extended > experimental use without a fee. Qexo is Free Software (Open-Source if you prefer), available without charge in both binary and source form (with a public CVS repository). > 2) The engine must be rigorously faithful to the specs. People > shouldn't learn bad habits. Huh? The most recent specs are about a week old. Even those have plenty of inconsistencies and unclear issues. Are there any implementations are are "regorously faithful to the specs"? Even the Novembver '02 version? What about static typing and schema import? Qexo may be less faithful/complete than some implementations, and more than others, but it is coming along well. I just implemented the new comment syntax, plus some other changes, including the new KindType syntax. One peeve: On the x-query.com homepage, only Qexo is listed as a "partial implementation", with the misleading implication that the other implementations are complete. Qexo is complete enough to do useful work with, as illustrated by the pages linked to from Qexo home page (http://www.gnu.org/software/qexo/). I admit there are big holes; no schema support, very limited static typing (though the hooks are there), no sorting, no duplicate removal in path expressions, many functions are not yet implemented, builtin functions are in the wrong namespace. But it has FLWR expressions, functions, typeswitch, some typing support, element constructors (both kinds), namespace support (except for namespace nodes), an efficient XML parser and DOM representation, decent error handling, a Java interface, lots of functions, and can be used in various modes, including command-line and servlets. > 3) The engine should be simple to setup and must be usable without a > large number of non-XQuery pieces. All you need is a Java VM and the Kawa .jar file. The kawa-1.7beta1 is usable, but kawa-1.7beta2 (should be out this weekend) will have a number of improvents, including the ones mentioned above. > 4) The engine should have good, accurate error reporting. I know how > frustrating "Nope, try again" errors can be. It's fairly decent. See the second half of this (draft) article at http://www.gnu.org/software/qexo/simple-xquery-webapp.html . (The article is servlet-centric, but the error handling is general. I made some recent improvements to syntactic error recovery; and the article is based on the CVS or forthcoming 1.7beta2 version of Qexo.) This article http://www.gnu.org/software/qexo/Running.html is useful how-to on using Qexo, and it illustrates error messages - though it has not been updated for the new comment syntax. > 5) The engine need not scale or be high performant. Since Qexo uses a compiler, it has decent performance, and hooks for further optimization. -- --Per Bothner per@bothner.com http://per.bothner.com/ From jhunter@acm.org Tue May 13 08:59:35 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4DFxZST023828 for ; Tue, 13 May 2003 08:59:35 -0700 Received: from snowball.huntershots.com ([65.122.201.44]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4DLYKFk003358 for ; Tue, 13 May 2003 14:34:21 -0700 Received: from acm.org (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h4DLZUFU000687 for ; Tue, 13 May 2003 14:35:30 -0700 (PDT) Message-ID: <3EC16446.22D01021@acm.org> Date: Tue, 13 May 2003 14:31:50 -0700 From: Jason Hunter X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: talk@x-query.com Subject: Re: [xquery-talk] Re: Best engine for learning? References: <3EC0300F.9040306@bothner.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2003 15:59:36 -0000 Per Bothner wrote: > > 2) The engine must be rigorously faithful to the specs. People > > shouldn't learn bad habits. > > Huh? The most recent specs are about a week old. True. I wouldn't expect conformance to the May drafts. November 2002 would be nice. I actually like any engine that conforms well to a particular date, rather than being a mix with some-April, some-November, and some-May for example. It gets old trying everything three different ways. :-) > Even those have > plenty of inconsistencies and unclear issues. Are there any > implementations are are "regorously faithful to the specs"? Even > the Novembver '02 version? Good question. I'd hope to point newbies at an engine that was as faithful as possible, with the ideal being one where the developers say, "It's not perfect, but we can't do anything to be more compliant til the next draft rev clears some things up." > One peeve: On the x-query.com homepage, only Qexo is listed as a > "partial implementation", with the misleading implication that the > other implementations are complete. Qexo is complete enough > to do useful work with, as illustrated by the pages linked to > from Qexo home page (http://www.gnu.org/software/qexo/). > > I admit there are big holes; no schema support, very limited > static typing (though the hooks are there), no sorting, no > duplicate removal in path expressions, many functions are not > yet implemented, builtin functions are in the wrong namespace. > But it has FLWR expressions, functions, typeswitch, some typing > support, element constructors (both kinds), namespace support > (except for namespace nodes), an efficient XML parser and DOM > representation, decent error handling, a Java interface, lots > of functions, and can be used in various modes, including > command-line and servlets. I knew I was getting myself into hot water by expressing any opinions about engines. The list of items TBD on Qexo justifies its "partial" status IMO. Whether the others can or should be inferred to be "complete" is debatable, but their "pending" lists seem significantly shorter. I don't mean to offend anyone, but I do want to provide a little editorial guidance for visitors so they know what to expect. -jh- From jhunter@servlets.com Tue May 13 09:17:28 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4DGHSST023848 for ; Tue, 13 May 2003 09:17:28 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h4DLrWFU000694 for ; Tue, 13 May 2003 14:53:33 -0700 (PDT) Message-ID: <3EC16880.50800E10@servlets.com> Date: Tue, 13 May 2003 14:49:52 -0700 From: Jason Hunter X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "talk@x-query.com" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [xquery-talk] Brainteaser X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2003 16:17:28 -0000 Here's a brainteaser XQuery problem, borrowed from a co-worker's real problem from this afternoon. I thought I'd share it as a little XQuery braincell stretch. I'm not asking for help; I know the answer and will post it later in the off chance no one else writes in. (Don't cheat and peek ahead unless you need to!) Assume an XML file "teaser.xml": One 2003-05-12T18:07:35Z Two 2003-05-12T18:09:01Z The following query contains three enclosed expressions, only one of which actually works as intended. The comments in the query describe the situation. Who can figure out the reason? define function get-root() as element { document("teaser.xml")/root }
This correctly prints the original document { get-root() }

This should print the original document, but doesn't { document("teaser.xml")/root }

This should print the names, but doesn't { get-root()/record/name }
-jh- From sander@x-hive.com Tue May 13 18:37:16 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4E1bGST024274 for ; Tue, 13 May 2003 18:37:16 -0700 Received: from JAKARTA.xhive.archipel (a194-109-160-206.adsl.xs4all.nl [194.109.160.206]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4E7IUvS027601 for ; Wed, 14 May 2003 00:18:31 -0700 content-class: urn:content-classes:message Subject: RE: [xquery-talk] Brainteaser Date: Wed, 14 May 2003 09:18:29 +0200 Message-ID: <41D11F414A26E942912B7E7696DC8E226C37AA@JAKARTA.xhive.archipel> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [xquery-talk] Brainteaser Thread-Index: AcMZ6QSfDmSAmvEVR5G22cUUNPvCfw== X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 From: "Sander Bos" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by jhunter.x-query.com id h4E1bGST024274 X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2003 01:37:16 -0000 > Here's a brainteaser XQuery problem, borrowed from a co-worker's real > problem from this afternoon. I thought I'd share it as a > little XQuery > braincell stretch. I'm not asking for help; I know the > answer and will > post it later in the off chance no one else writes in. > (Don't cheat and > peek ahead unless you need to!) > define function get-root() as element { > document("teaser.xml")/root > } > > > >
This correctly prints the original document > { > get-root() > } >
> >
This should print the original document, but doesn't > { > document("teaser.xml")/root > } >
> >
This should print the names, but doesn't > { > get-root()/record/name > } >
> > [SPOILER....] That the test-case is small obviously makes it easier to find what is the problem: The default namespace declaration means that 'root' in document("teaser.xml")/root is treated as '{http://www.w3.org/1999/xhtml}root' which cannot be found in the namespace free document. The function does not have this problem because it is outside the scope of the element constructor. Kind regards, --Sander. -- X-Hive Corporation (www.x-hive.com) email: sander@x-hive.com phone: +31 10 2818080 From jhunter@servlets.com Tue May 13 20:00:48 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4E30mST024354 for ; Tue, 13 May 2003 20:00:48 -0700 Received: from snowball.huntershots.com ([65.122.201.44]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4E8gsvS031295 for ; Wed, 14 May 2003 01:42:54 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h4E8hwFU001985; Wed, 14 May 2003 01:43:58 -0700 (PDT) Message-ID: <3EC200F1.4BEABC2F@servlets.com> Date: Wed, 14 May 2003 01:40:17 -0700 From: Jason Hunter X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Sander Bos References: <41D11F414A26E942912B7E7696DC8E226C37AA@JAKARTA.xhive.archipel> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: talk@x-query.com Subject: [xquery-talk] Re: Debugging (was: Brainteaser) X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2003 03:00:48 -0000 > [SPOILER....] You got it. :-) > That the test-case is small obviously makes it easier to find what is > the problem: Agreed. That's how I actually found it initially, by simplifying til things worked and expanding back out. Which raises an interesting question: What's the best way people have found to *debug* queries? I notice some engines have log() functions which allows printf() style debugging. That can let you watch some of what's going on. Any other tricks? -jh- From per@bothner.com Fri May 16 10:28:09 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4GHS9ST027023 for ; Fri, 16 May 2003 10:28:09 -0700 Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4GNmv1Q027239 for ; Fri, 16 May 2003 16:48:57 -0700 Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out2.apple.com (8.12.9/8.12.9) with ESMTP id h4GNjI1j027575 for ; Fri, 16 May 2003 16:45:19 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Fri, 16 May 2003 16:45:18 -0700 Received: from bothner.com (il0102a-dhcp124.apple.com [17.201.27.252]) by scv3.apple.com (8.12.9/8.12.9) with ESMTP id h4GNjHGd024118; Fri, 16 May 2003 16:45:17 -0700 (PDT) Message-ID: <3EC57850.70605@bothner.com> Date: Fri, 16 May 2003 16:46:24 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Hunter Subject: Re: [xquery-talk] Re: Debugging References: <41D11F414A26E942912B7E7696DC8E226C37AA@JAKARTA.xhive.archipel> <3EC200F1.4BEABC2F@servlets.com> In-Reply-To: <3EC200F1.4BEABC2F@servlets.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2003 17:28:09 -0000 Jason Hunter wrote: > Which raises an interesting question: What's the best way people have > found to *debug* queries? I notice some engines have log() functions > which allows printf() style debugging. That can let you watch some of > what's going on. Any other tricks? The May specification includes a trace(VALUE, STRING) function that is at least partly intended for debugging. The latest CVS version of Qexo include the trace functions. The second half of the following (draft) article includes some notes on debugging Qexo. It is written in the context of web applications (using servlets), but the debugging notes are generally applicable. http://www.gnu.org/software/qexo/simple-xquery-webapp.html -- --Per Bothner per@bothner.com http://per.bothner.com/ From jhunter@servlets.com Mon May 19 06:02:48 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4JD2lST029921 for ; Mon, 19 May 2003 06:02:48 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h4JK2WFU003626; Mon, 19 May 2003 13:02:32 -0700 (PDT) Message-ID: <3EC93789.19C73199@servlets.com> Date: Mon, 19 May 2003 12:59:05 -0700 From: Jason Hunter X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Per Bothner Subject: Re: [xquery-talk] Re: Debugging References: <41D11F414A26E942912B7E7696DC8E226C37AA@JAKARTA.xhive.archipel> <3EC200F1.4BEABC2F@servlets.com> <3EC57850.70605@bothner.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2003 13:02:48 -0000 Per Bothner wrote: > > The May specification includes a trace(VALUE, STRING) function that > is at least partly intended for debugging. The latest CVS version of > Qexo include the trace functions. Thanks for pointing that out. I hadn't noticed it yet. It does seem odd the order of the two params is left "implementation defined". Per the F&O 4.1 example: -- Consider a situation in which a user wants to investigate the actual value passed to a function. Assume that in a particular execution, $v is an xs:decimal with value 124.84. Writing fn:trace($v, 'the value of $v is:') will put the strings "124.84" and "the value of $v is" in the trace data set in implementation defined order. -- So the output will either be English "the value of $v is 124.84" or Yoda "124.84 the value of $v is". :-) -jh- From per@bothner.com Mon May 19 06:50:26 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4JDoQST030036 for ; Mon, 19 May 2003 06:50:26 -0700 Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4JKnt7B003935 for ; Mon, 19 May 2003 13:49:55 -0700 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.12.9/8.12.9) with ESMTP id h4JKntBx013989 for ; Mon, 19 May 2003 13:49:57 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Mon, 19 May 2003 13:49:41 -0700 Received: from bothner.com (il0102a-dhcp124.apple.com [17.201.27.252]) by scv3.apple.com (8.12.9/8.12.9) with ESMTP id h4JKnsI2020272; Mon, 19 May 2003 13:49:55 -0700 (PDT) Message-ID: <3EC943B8.8010805@bothner.com> Date: Mon, 19 May 2003 13:51:04 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Hunter Subject: Re: [xquery-talk] Re: Debugging References: <41D11F414A26E942912B7E7696DC8E226C37AA@JAKARTA.xhive.archipel> <3EC200F1.4BEABC2F@servlets.com> <3EC57850.70605@bothner.com> <3EC93789.19C73199@servlets.com> In-Reply-To: <3EC93789.19C73199@servlets.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2003 13:50:26 -0000 Jason Hunter wrote: > It does seem odd the order of the two params [to trace] is left > "implementation defined". Per the F&O 4.1 example: > ... > So the output will either be English > "the value of $v is 124.84" > or Yoda > "124.84 the value of $v is". Or: QXuery trace output value: 124.84 label: "the value of $v is" I think the example *suggests* that the label will be written first, bt you cannot count on it. However, I suspect the "implementation defined order" is actually talking about the different invocations of trace. -- --Per Bothner per@bothner.com http://per.bothner.com/ From Sullivan.Sean@menlolog.com Wed May 21 03:40:58 2003 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4LAewST031942 for ; Wed, 21 May 2003 03:40:58 -0700 Received: from cnfqs057.cnf.prod.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id 51EEE7AC for ; Wed, 21 May 2003 11:05:19 -0700 (PDT) Received: by cnfqs057.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Wed, 21 May 2003 11:05:18 -0700 Message-ID: From: "Sullivan, Sean C - MWT" To: "'talk@x-query.com'" Date: Wed, 21 May 2003 11:05:16 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] XQuery page on the JINX wiki X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 10:40:58 -0000 The JINX wiki has an XQuery page: http://jinx.swiki.net/416 Feel free to update the page with additional resources. -Sean From Sullivan.Sean@menlolog.com Wed May 21 07:42:00 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4LEfxST032167 for ; Wed, 21 May 2003 07:42:00 -0700 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4LMAuLl031044 for ; Wed, 21 May 2003 15:10:56 -0700 Received: from cnfqs057.cnf.prod.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id CBC7A86A for ; Wed, 21 May 2003 15:10:53 -0700 (PDT) Received: by cnfqs057.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Wed, 21 May 2003 15:10:53 -0700 Message-ID: From: "Sullivan, Sean C - MWT" To: "'talk@x-query.com'" Date: Wed, 21 May 2003 15:10:48 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C31FE5.D5256C64" Subject: [xquery-talk] XQuery, BEA Liquid Data, Enosys Software X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 14:42:01 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C31FE5.D5256C64 Content-Type: text/plain Is anybody using BEA's Liquid Data product? How does it compare to Enosys Server? Cheers, -Sean http://www.enosyssoftware.com/news/pr111802a.html http://edocs.bea.com/liquiddata/docs10/index.html http://edocs.bea.com/liquiddata/docs10/faq/index.html ------_=_NextPart_001_01C31FE5.D5256C64 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

 

Is anybody using BEA's = Liquid Data product?

 

How does it compare to Enosys Server?

 

Cheers,

 

-Sean

 

http://www.en= osyssoftware.com/news/pr111802a.html

 

http://edocs.= bea.com/liquiddata/docs10/index.html

 

http://ed= ocs.bea.com/liquiddata/docs10/faq/index.html

 

 

------_=_NextPart_001_01C31FE5.D5256C64-- From Sullivan.Sean@menlolog.com Wed May 21 10:54:31 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4LHsTST032328 for ; Wed, 21 May 2003 10:54:31 -0700 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4M1P6vh006891 for ; Wed, 21 May 2003 18:25:08 -0700 Received: from cnfqs057.cnf.prod.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id A126FC4E for ; Wed, 21 May 2003 18:23:03 -0700 (PDT) Received: by cnfqs057.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Wed, 21 May 2003 18:23:03 -0700 Message-ID: From: "Sullivan, Sean C - MWT" To: "'talk@x-query.com'" Date: Wed, 21 May 2003 18:22:58 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] IBM, XML for Tables X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 17:54:31 -0000 IBM's "XML for Tables" project http://www.alphaworks.ibm.com/tech/xtable "XML for Tables allows querying of SQL data (stored in the relational tables) in a new language, XQuery, which is undergoing W3C approval. XML for Tables provides functions for creating XML views of relational tables in such a way that the SQL data are treated as if they are virtual XML documents and they can be queried in XQuery. XML for Tables translates XQuery into SQL and pushes down SQL to DB2. SQL queries produce output in tuple format; XML for Tables tags the tuple result into XML; so the XQuery results are in an XML document. XML for Tables is wrapped as DB2 stored procedures, and queries are submitted by calling the stored procedures." From Sullivan.Sean@menlolog.com Wed May 21 10:59:46 2003 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4LHxjST032341 for ; Wed, 21 May 2003 10:59:46 -0700 Received: from cnfqs057.cnf.prod.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id AB02D47F for ; Wed, 21 May 2003 18:30:28 -0700 (PDT) Received: by cnfqs057.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Wed, 21 May 2003 18:30:28 -0700 Message-ID: From: "Sullivan, Sean C - MWT" To: "'talk@x-query.com'" Date: Wed, 21 May 2003 18:30:22 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] XQuery @ JavaOne 2003 X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 17:59:46 -0000 Oracle is giving a presentation at Sun's upcoming JavaOne conference... June 12, 2003 San Francisco, CA USA Heterogeneous XML-Based Data Integration Using XQuery, JavaTM 2 Platform, Enterprise Edition (J2EETM) and Database Technologies http://servlet.java.sun.com/javaone/sf2003/conf/sessions/display-1212.en.jsp Abstract Data Integration is an important business problem that companies frequently need to solve. It can provide an up-to-the-minute complete view of the whole enterprise by aggregating information from different sources of data scattered within and outside a company, such as multiple databases, legacy sources, Web services, and so on. Given the diverse characteristics of heterogeneous data sources in real life, data integration is not a trivial task. Fortunately, XML and XQuery are relevant standards that simplify this problem domain greatly. The XQuery language can be used to express an aggregated XML-based view over the various data sources. In this session, we discuss in detail the roles of XML and XQuery for data integration using Java TM technology and databases and cover both "push" and "pull" models of data access and parameterized data sources. Heterogeneous data sources in the JavaTM 2 Platform, Enterprise Edition (J2EETM) world do not directly fit into the XQuery engine, and Java technology-based adaptors are needed to feed in the data. We discuss some common types of adaptors and issues in designing them. We also describe optional but useful capabilities that could be associated with data sources, such as caching, security and object mapping services, and how aggregated views could be published and used as programmatic components. We go through a step-by-step example to illustrate how these technologies can be used for building a data integration solution quickly and efficiently. In this session, you learn how to use J2EE and database technologies together with XQuery to achieve heterogeneous XML-based data integration. From Sullivan.Sean@menlolog.com Wed May 21 11:10:42 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4LIAfST032358 for ; Wed, 21 May 2003 11:10:41 -0700 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4M1fYvh007521 for ; Wed, 21 May 2003 18:41:34 -0700 Received: from cnfqs057.cnf.prod.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id AF3A98F8 for ; Wed, 21 May 2003 18:38:23 -0700 (PDT) Received: by cnfqs057.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Wed, 21 May 2003 18:38:23 -0700 Message-ID: From: "Sullivan, Sean C - MWT" To: "'talk@x-query.com'" Date: Wed, 21 May 2003 18:38:18 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] XQuery API's X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 18:10:42 -0000 BEA Liquid Data Query API http://edocs.bea.com/liquiddata/docs10/program/intro.html OJXQI - The Oracle Java XQuery API http://otn.oracle.com/sample_code/tech/xml/xmldb/jxqi.html From per@bothner.com Wed May 21 12:28:41 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4LJSfST032424 for ; Wed, 21 May 2003 12:28:41 -0700 Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4M30Avh010822 for ; Wed, 21 May 2003 20:00:10 -0700 Received: from bothner.com ([216.102.199.253]) by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 HotFix 1.6 (built Oct 18 2002)) with ESMTP id <0HF900EMSPOE12@mta5.snfc21.pbi.net> for talk@x-query.com; Wed, 21 May 2003 20:00:14 -0700 (PDT) Date: Wed, 21 May 2003 20:01:22 -0700 From: Per Bothner Subject: Re: [xquery-talk] XQuery @ JavaOne 2003 In-reply-to: To: "Sullivan, Sean C - MWT" Message-id: <3ECC3D82.2010609@bothner.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030507 References: Cc: "'talk@x-query.com'" X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 19:28:41 -0000 Sullivan, Sean C - MWT wrote: > Oracle is giving a presentation at Sun's upcoming JavaOne conference... I will also be covering XQuery in my JavaOne session: Kawa: Compiling Programming Languages to the Java[TM] Virtual Machine Wednesday, 5:15pm. I will mention the various languages that have been implemented using Kawa, including Qexo, my XQuery implementation. Btw, I gave an XQuery/Qexo talk at JavaOne last year. This year's is more about the implementation rather than the languages, as I use examples from multiple Kawa languages, not just XQuery. -- --Per Bothner per@bothner.com http://per.bothner.com/ From per@bothner.com Wed May 21 12:39:21 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4LJdKST032438 for ; Wed, 21 May 2003 12:39:21 -0700 Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4M3Awvh011230 for ; Wed, 21 May 2003 20:10:58 -0700 Received: from bothner.com ([216.102.199.253]) by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 HotFix 1.6 (built Oct 18 2002)) with ESMTP id <0HF9003NOQ6EMZ@mta5.snfc21.pbi.net> for talk@x-query.com; Wed, 21 May 2003 20:11:02 -0700 (PDT) Date: Wed, 21 May 2003 20:12:14 -0700 From: Per Bothner Subject: Re: [xquery-talk] XQuery API's In-reply-to: To: "Sullivan, Sean C - MWT" Message-id: <3ECC400E.2050009@bothner.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030507 References: Cc: "'talk@x-query.com'" X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 19:39:21 -0000 See http://www.gnu.org/software/qexo/Running.html for some examples of Qexo's APIs. Sullivan, Sean C - MWT wrote: > BEA Liquid Data Query API > http://edocs.bea.com/liquiddata/docs10/program/intro.html They don't support "preparation" unless you're a db admin! > OJXQI - The Oracle Java XQuery API > http://otn.oracle.com/sample_code/tech/xml/xmldb/jxqi.html Using an XMLNode class seems unnecessary and inefficient. It forces all "nodes" to implement XMLNodes, or to wrap them. Why not just use the XQueryResultSet as the interface between the generic API and the implementation? Still, it's a starting point, if they want to propose it as a generic API. (Also I note they use upper-case reserved words ...) -- --Per Bothner per@bothner.com http://per.bothner.com/ From pcp@cerisent.com Wed May 21 14:00:23 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4LL0NST032519 for ; Wed, 21 May 2003 14:00:23 -0700 Received: from cerisent.com (adsl-64-170-128-124.dsl.anhm01.pacbell.net [64.170.128.124]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4M4WetQ014529 for ; Wed, 21 May 2003 21:32:40 -0700 Received: from D5MLGF01.cerisent.com (adsl-63-195-118-157.dsl.snfc21.pacbell.net [63.195.118.157]) by cerisent.com (8.11.6/8.11.6) with ESMTP id h4M4WiG04867 for ; Wed, 21 May 2003 21:32:44 -0700 Message-Id: <5.1.0.14.0.20030521212454.01bb3a38@mail.cerisent.com> X-Sender: pcp@mail.cerisent.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 21 May 2003 21:34:12 -0700 To: talk@x-query.com From: Paul Pedersen Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [xquery-talk] OJXQI -- seems fundamentally broken X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 21:00:23 -0000 From the page: http://otn.oracle.com/sample_code/tech/xml/xmldb/jxqi.html XQueryContext ctx = new XQueryContext(); try { Reader strm = new FileReader("exmpl1.xql"); PreparedXQuery xq = ctx.prepareXQuery(strm); XQueryResultSet rset = xq.executeQuery(); while (rset.next()) { XMLNode node = rset.getNode(); // get result nodes System.out.println(" NODE "+ node.getNodeName()); node.print(System.out); } } catch (Exception e) { // do something.. } What's wrong in this picture? Simply that XQuery returns "items" not nodes. An XQuery expression can return an arbitrary sequence of primitive datatypes, Schema types, disembodied attributes, text nodes, element nodes, etc. So I don't quite see how the interface as shown can be considered an "XQuery" interface. Cerisent constructed an XQuery interface called XDBC (by analogy with JDBC), and handling heterogeneous item sequences was the >main< problem. Cheers, Paul Pedersen Cerisent Corporation From per@bothner.com Thu May 22 01:10:09 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4M8A8ST000525 for ; Thu, 22 May 2003 01:10:08 -0700 Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4MFmwH1010347 for ; Thu, 22 May 2003 08:48:58 -0700 Received: from bothner.com ([216.102.199.253]) by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 HotFix 1.6 (built Oct 18 2002)) with ESMTP id <0HFA008B2P9MPN@mta5.snfc21.pbi.net> for talk@x-query.com; Thu, 22 May 2003 08:48:59 -0700 (PDT) Date: Thu, 22 May 2003 08:50:11 -0700 From: Per Bothner Subject: Re: [xquery-talk] OJXQI -- seems fundamentally broken In-reply-to: <5.1.0.14.0.20030521212454.01bb3a38@mail.cerisent.com> To: Paul Pedersen Message-id: <3ECCF1B3.10803@bothner.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030507 References: <5.1.0.14.0.20030521212454.01bb3a38@mail.cerisent.com> Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2003 08:10:09 -0000 Paul Pedersen wrote: > What's wrong in this picture? Simply that XQuery returns > "items" not nodes. An XQuery expression can return an > arbitrary sequence of primitive datatypes, Schema types, > disembodied attributes, text nodes, element nodes, etc. > So I don't quite see how the interface as shown can be > considered an "XQuery" interface. Cerisent constructed > an XQuery interface called XDBC (by analogy with JDBC), > and handling heterogeneous item sequences was the >main< > problem. A useful API would be that of a "pull parser", or a tree iterator. You'd ask the iterator what's next, and the client can extract it using various methods, skip it, traversing recursively, or send the next object to a "push" SAX-like consumer. The Qexo implementation provides something like that, but it's not as smooth or complete as it should be. -- --Per Bothner per@bothner.com http://per.bothner.com/ From Sullivan.Sean@menlolog.com Thu May 22 08:03:21 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4MF3LST000874 for ; Thu, 22 May 2003 08:03:21 -0700 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4MMmgnc028360 for ; Thu, 22 May 2003 15:48:42 -0700 Received: from cnfqs057.cnf.prod.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id E63A3E14 for ; Thu, 22 May 2003 15:46:46 -0700 (PDT) Received: by cnfqs057.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Thu, 22 May 2003 15:46:46 -0700 Message-ID: From: "Sullivan, Sean C - MWT" To: "'talk@x-query.com'" Date: Thu, 22 May 2003 15:46:44 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] IBM DB2 Information Integrator, J2EE X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2003 15:03:22 -0000 Although this is not XQuery technology, it appears to serve a similar purpose. The article discusses IBM's DB2 Information Integrator in the context of J2EE applications. http://www7b.boulder.ibm.com/dmdd/library/techarticle/0305saracco1/0305sarac co1.html "IBM's new DB2(r) Information Integrator, a product designed to provide a single-site image of data residing on different platforms, stored in different formats, and accessible through different application programming interfaces (APIs). [...]" From lehti@ipsi.fhg.de Mon May 26 15:46:02 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4QMk1ST005231 for ; Mon, 26 May 2003 15:46:02 -0700 Received: from sonne.sit.fraunhofer.de (sonne.sit.fraunhofer.de [141.12.62.20]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4R7YeZ9028994 for ; Tue, 27 May 2003 00:34:43 -0700 Received: from pcspindle (pc-spindle [141.12.28.41]) by sonne.sit.fraunhofer.de (8.8.8/8.8.5) with ESMTP id JAA02438; Tue, 27 May 2003 09:34:33 +0200 (MET DST) From: "Patrick Lehti" To: , , Date: Tue, 27 May 2003 09:35:16 +0200 Message-ID: <000301c32422$849633b0$291c0c8d@pcspindle> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Cc: Subject: [xquery-talk] [ANN] IPSI-XQ v1.3.0 released X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 22:46:03 -0000 Hi, we are proud to announce the release of IPSI-XQ version 1.3.0. IPSI-XQ is an implementation of the upcoming W3C XQuery standard for an XML query language. It is implemented as faithfully as possible along the current W3C Working Drafts. It is available for free for non-commercial usage. It comes along with several user interfaces - a graphical, a command line and web interface - and it has a wide JAVA API to integrate it into other applications. The new version 1.3.0 is based on the latest working drafts of May 2nd. In this version most of the functions and operators have been implemented. Additionally the Java API was widely enhanced. Version 1.3.0 has the following modifications to 1.2.2: - The syntax and semantics is modified to reflect the Working Drafts from 2003-05-02. - Most of the functions and operators are implemented, including support for date, time and durations. - Improved performance. - Global variables are supported. - Strongly enhanced API, supports plug-in of own data model implementations, definition of external functions, definition of external variables, more control when calling IPSI-XQ and exposition of XQuery AST as framework for own XQuery applications. - Improved output window for the GUI. Have a look at our web site (http://ipsi.fhg.de/oasys/projects/ipsi-xq/index_e.html) and download the latest version. Any feedback is extremely welcome! Best regards, The IPSI-XQ team From lehti@ipsi.fhg.de Mon May 26 20:50:57 2003 Received: from sonne.sit.fraunhofer.de (sonne.sit.fraunhofer.de [141.12.62.20]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4R3otST005461 for ; Mon, 26 May 2003 20:50:56 -0700 Received: from pcspindle (pc-spindle [141.12.28.41]) by sonne.sit.fraunhofer.de (8.8.8/8.8.5) with ESMTP id OAA03311 for ; Tue, 27 May 2003 14:42:00 +0200 (MET DST) From: "Patrick Lehti" To: Subject: RE: [xquery-talk] Re: Best engine for learning? Date: Tue, 27 May 2003 14:42:44 +0200 Message-ID: <001001c3244d$787151c0$291c0c8d@pcspindle> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <3EC16446.22D01021@acm.org> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 03:50:57 -0000 Regarding this thread, the comment of one of the users of IPSI-XQ lately made, might be interesting: "IPSI-XQ is the only Java-based, up-to-date, truly embeddable XQuery implementation. All other implementations are closed, out of date or tied to expensive commercial native XML DBs." Regards, Patrick > -----Original Message----- > From: talk-bounces@x-query.com > [mailto:talk-bounces@x-query.com] On Behalf Of Jason Hunter > Sent: Dienstag, 13. Mai 2003 23:32 > To: talk@x-query.com > Subject: Re: [xquery-talk] Re: Best engine for learning? > > > Per Bothner wrote: > > > > 2) The engine must be rigorously faithful to the specs. People > > > shouldn't learn bad habits. > > > > Huh? The most recent specs are about a week old. > > True. I wouldn't expect conformance to the May drafts. November 2002 > would be nice. I actually like any engine that conforms well to a > particular date, rather than being a mix with some-April, > some-November, > and some-May for example. It gets old trying everything > three different > ways. :-) > > > Even those have > > plenty of inconsistencies and unclear issues. Are there any > > implementations are are "regorously faithful to the specs"? Even > > the Novembver '02 version? > > Good question. I'd hope to point newbies at an engine that was as > faithful as possible, with the ideal being one where the > developers say, > "It's not perfect, but we can't do anything to be more > compliant til the > next draft rev clears some things up." > > > One peeve: On the x-query.com homepage, only Qexo is listed as a > > "partial implementation", with the misleading implication that the > > other implementations are complete. Qexo is complete enough > > to do useful work with, as illustrated by the pages linked to > > from Qexo home page (http://www.gnu.org/software/qexo/). > > > > I admit there are big holes; no schema support, very limited > > static typing (though the hooks are there), no sorting, no > > duplicate removal in path expressions, many functions are not > > yet implemented, builtin functions are in the wrong namespace. > > But it has FLWR expressions, functions, typeswitch, some typing > > support, element constructors (both kinds), namespace support > > (except for namespace nodes), an efficient XML parser and DOM > > representation, decent error handling, a Java interface, lots > > of functions, and can be used in various modes, including > > command-line and servlets. > > I knew I was getting myself into hot water by expressing any > opinions about engines. The list of items TBD on Qexo justifies its > "partial" status IMO. Whether the others can or should be inferred to > be "complete" is debatable, but their "pending" lists seem > significantly > shorter. I don't mean to offend anyone, but I do want to provide a > little editorial guidance for visitors so they know what to expect. > > -jh- > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk > From Mark_R_Maxey@raytheon.com Mon May 26 21:51:48 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4R4plST005513 for ; Mon, 26 May 2003 21:51:48 -0700 Received: from dfw-gate1.raytheon.com (dfw-gate1.raytheon.com [199.46.199.230]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4RDiHEr011986 for ; Tue, 27 May 2003 06:44:17 -0700 Received: from ds02c00.directory.ray.com (ds02c00.directory.ray.com [147.25.138.118]) by dfw-gate1.raytheon.com (8.12.9/8.12.9) with ESMTP id h4RDiCF4006905; Tue, 27 May 2003 08:44:12 -0500 (CDT) Received: from ds02c00.directory.ray.com (localhost [127.0.0.1]) by ds02c00.directory.ray.com (8.12.9/8.12.1) with ESMTP id h4RDhxmt022783; Tue, 27 May 2003 13:44:11 GMT Received: Received: from raytheon.com ([162.36.244.78]) by ds02c00.directory.ray.com (8.12.9/8.12.9) with ESMTP id h4RDhvbH022749 sender Mark_R_Maxey@raytheon.com; Tue, 27 May 2003 13:43:57 GMT Message-ID: <3ED36BA1.7000505@raytheon.com> Date: Tue, 27 May 2003 08:44:01 -0500 From: Mark R Maxey Organization: Raytheon User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en,pdf MIME-Version: 1.0 To: "'talk@x-query.com'" Subject: Re: [xquery-talk] XQuery, BEA Liquid Data, Enosys Software References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------090601010509050103090709" Cc: "Sullivan, Sean C - MWT" X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list Reply-To: Mark_R_Maxey@raytheon.com List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 04:51:48 -0000 This is a multi-part message in MIME format. --------------090601010509050103090709 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Enosys is the XQuery engine used by Liquid Data. Enosys delivers its engine to BEA as an OEM. My impression from talking to both parties is that Enosys prefers to remain a small focused team in the background while BEA continues to expand functionality via acquisition. Sullivan, Sean C - MWT wrote: > > > Is anybody using BEA's Liquid Data product? > > > > How does it compare to Enosys Server? > > > > Cheers, > > > > -Sean > > > > http://www.enosyssoftware.com/news/pr111802a.html > > > > http://edocs.bea.com/liquiddata/docs10/index.html > > > > http://edocs.bea.com/liquiddata/docs10/faq/index.html > > > > > >------------------------------------------------------------------------ > >_______________________________________________ >talk@x-query.com >http://www.x-query.com/mailman/listinfo/talk > > -- *Mark Maxey* Senior S/W Engineer II 972.205.5760 972.205.6144 fax Mark_R_Maxey@Raytheon.com --------------090601010509050103090709 Content-Type: multipart/related; boundary="------------090802050707000007060407" --------------090802050707000007060407 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Enosys is the XQuery engine used by Liquid Data.  Enosys delivers its engine to BEA as an OEM.  My impression from talking to both parties is that Enosys prefers to remain a small focused team in the background while BEA continues to expand functionality via acquisition.

Sullivan, Sean C - MWT wrote:

 

Is anybody using BEA's Liquid Data product?

 

How does it compare to Enosys Server?

 

Cheers,

 

-Sean

 

http://www.enosyssoftware.com/news/pr111802a.html

 

http://edocs.bea.com/liquiddata/docs10/index.html

 

http://edocs.bea.com/liquiddata/docs10/faq/index.html

 

 


_______________________________________________
talk@x-query.com
http://www.x-query.com/mailman/listinfo/talk

--

Raytheon
Mark Maxey
 Senior S/W Engineer II
972.205.5760
972.205.6144 fax
Mark_R_Maxey@Raytheon.com
--------------090802050707000007060407 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-ID: Content-Base: "http://raytheonlogo.gif/" Content-Location: "http://raytheonlogo.gif/" ERROR: The requested URL could not be retrieved

The requested URL could not be retrieved

While trying to retrieve the URL: http://raytheonlogo.gif/

The following error was encountered:

Unable to determine IP address from host name for raytheonlogo.gif

The dnsserver returned:

Name Error: The domain name does not exist.

This means that: 

 The cache was not able to resolve the hostname presented in the URL. 
 Check if the address is correct.

Your cache administrator is netsec-ops@ext.ray.com.

Generated Tue, 27 May 2003 13:43:57 GMT by dfw-gate3.raytheon.com (Squid/2.4.STABLE7) --------------090802050707000007060407 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-ID: Content-Base: "http://redbar.gif/" Content-Location: "http://redbar.gif/" ERROR: The requested URL could not be retrieved

The requested URL could not be retrieved

While trying to retrieve the URL: http://redbar.gif/

The following error was encountered:

Unable to determine IP address from host name for redbar.gif

The dnsserver returned:

Name Error: The domain name does not exist.

This means that: 

 The cache was not able to resolve the hostname presented in the URL. 
 Check if the address is correct.

Your cache administrator is netsec-ops@ext.ray.com.

Generated Tue, 27 May 2003 13:43:57 GMT by dfw-gate3.raytheon.com (Squid/2.4.STABLE7) --------------090802050707000007060407-- --------------090601010509050103090709-- From duncan@x180.net Tue May 27 10:43:04 2003 Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4RHh4ST006071 for ; Tue, 27 May 2003 10:43:04 -0700 Received: (qmail 9659 invoked from network); 28 May 2003 02:44:30 -0000 Received: from unknown (HELO x180.net) (x180@[68.0.98.62]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 28 May 2003 02:44:30 -0000 Date: Tue, 27 May 2003 08:37:50 -0700 Subject: Re: [xquery-talk] Best engine for learning? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Jason Hunter From: James Duncan Davidson In-Reply-To: <3EBFFBF2.75CC1C14@servlets.com> Message-Id: <2C542D5A-9059-11D7-B40C-000393DB198C@x180.net> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 17:43:04 -0000 On Monday, May 12, 2003, at 12:54 US/Pacific, Jason Hunter wrote: > 3) The engine should be simple to setup and must be usable without a > large number of non-XQuery pieces. The more unadorned the XQuery > feature, the better for learning. > > 4) The engine should have good, accurate error reporting. I know how > frustrating "Nope, try again" errors can be. > > 5) The engine need not scale or be high performant. What I'd most like to see is an XQuery engine that doesn't try to hard to be an NXD or web application server. All I really want is a command line tool: % xqueryengine [queryfile] [xmlfile] With the result dumping out to stdout. James Duncan Davidson Coder, Speaker, Author http://x180.net/ [life live]; From mike@clarkware.com Tue May 27 11:12:02 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h4RIC2ST006115 for ; Tue, 27 May 2003 11:12:02 -0700 Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h4S3DfXX013496 for ; Tue, 27 May 2003 20:13:41 -0700 Received: from clarkware.com (12-254-54-55.client.attbi.com[12.254.54.55]) by attbi.com (rwcrmhc52) with SMTP id <2003052803134005200p8d5pe>; Wed, 28 May 2003 03:13:40 +0000 Message-ID: <3ED4293F.9000703@clarkware.com> Date: Tue, 27 May 2003 21:13:03 -0600 From: Mike Clark User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: talk@x-query.com Subject: Re: [xquery-talk] Best engine for learning? References: <2C542D5A-9059-11D7-B40C-000393DB198C@x180.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 18:12:02 -0000 James Duncan Davidson wrote: > What I'd most like to see is an XQuery engine that doesn't try to hard > to be an NXD or web application server. All I really want is a command > line tool: > > % xqueryengine [queryfile] [xmlfile] > > With the result dumping out to stdout. +1 I'm trying to come up to speed on XQuery by writing learning tests, so I also want an API I can call from my tests, as in: assertEquals(expectedResult, queryengine.evaluate(queryExpression, xmlString)) An engine that supports such an API is both testable and usable independent of any particular data source or server. Mike From Sullivan.Sean@menlolog.com Tue Jun 10 08:11:34 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h5AFBYST020334 for ; Tue, 10 Jun 2003 08:11:34 -0700 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h5B3MlY0003337 for ; Tue, 10 Jun 2003 20:22:47 -0700 Received: from cnfqs057.cnf.prod.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id 41515522 for ; Tue, 10 Jun 2003 20:22:45 -0700 (PDT) Received: by cnfqs057.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Tue, 10 Jun 2003 20:22:44 -0700 Message-ID: <462D5240F6F9154AB0F9B345A5F03E3E3ABA2B@cnfqe029.cnf.prod.cnf.com> From: "Sullivan, Sean C - MWT" To: "''talk@x-query.com' '" Date: Tue, 10 Jun 2003 20:22:38 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message x-mimeole: Produced By Microsoft Exchange V6.0.6375.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [xquery-talk] JSR-225; Oracle & IBM propose XQuery API for Java X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2003 15:11:34 -0000 June 10, 2003 Oracle, IBM Propose XQuery API for Java "Oracle Corp. and IBM on Tuesday announced a new Java Specification Request to define a Java API for invocations of queries written in XQuery, the XML querying language. [...]" Details: http://www.eweek.com/article2/0,3959,1123034,00.asp JSR-225 http://www.jcp.org/en/jsr/detail?id=225 From jhunter@servlets.com Tue Jul 1 11:24:14 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h61IOEwp010496 for ; Tue, 1 Jul 2003 11:24:14 -0700 Received: from snowball.huntershots.com ([65.122.201.44]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h61IQIlS002308 for ; Tue, 1 Jul 2003 11:26:18 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h61IRjrY001591 for ; Tue, 1 Jul 2003 11:27:47 -0700 (PDT) Message-ID: <3F01D18C.506@servlets.com> Date: Tue, 01 Jul 2003 11:23:08 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@x-query.com Content-Type: multipart/mixed; boundary="------------090301030700060109030601" Subject: [xquery-talk] [Fwd: New XQuery Requirements WD published] X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2003 18:24:15 -0000 This is a multi-part message in MIME format. --------------090301030700060109030601 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit --------------090301030700060109030601 Content-Type: message/rfc822; name="New XQuery Requirements WD published" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="New XQuery Requirements WD published" Return-Path: Received: from alias2.acm.org ([199.222.69.92]) by samuel.mail.atl.earthlink.net (Earthlink Mail Service) with ESMTP id 19xlFQ2XB3Nl3pv0 for ; Tue, 1 Jul 2003 09:59:58 -0400 (EDT) Received: from frink.w3.org ([18.29.1.71]) by alias2.acm.org (ACM Email Forwarding Service) with ESMTP id CRY73883; Tue, 01 Jul 2003 09:59:57 -0400 Received: from frink.w3.org (localhost [127.0.0.1]) by frink.w3.org (8.12.9/8.12.9) with ESMTP id h61DxDSn005045; Tue, 1 Jul 2003 09:59:13 -0400 (EDT) Received: (from lists@localhost) by frink.w3.org (8.12.9/8.12.9/Submit) id h61Dx488004976; Tue, 1 Jul 2003 09:59:04 -0400 (EDT) Resent-Date: Tue, 1 Jul 2003 09:59:04 -0400 (EDT) Resent-Message-Id: <200307011359.h61Dx488004976@frink.w3.org> Received: from tux.w3.org (IDENT:root@tux [18.29.0.27]) by frink.w3.org (8.12.9/8.12.9) with ESMTP id h61Dx3Sn004941 for ; Tue, 1 Jul 2003 09:59:03 -0400 (EDT) Received: from massimolaptop (IDENT:root@localhost [127.0.0.1]) by tux.w3.org (8.12.9/8.12.9) with SMTP id h61Dx2Yu029270 for ; Tue, 1 Jul 2003 09:59:03 -0400 From: "Massimo Marchiori" To: "Www-Ql@W3. Org" Date: Tue, 1 Jul 2003 15:57:56 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Subject: New XQuery Requirements WD published X-Archived-At: http://www.w3.org/mid/NGBBJNKIMLOPPCFHEJEMMECNDDAA.massimo@w3.org Resent-From: www-ql@w3.org X-Mailing-List: archive/latest/519 X-Loop: www-ql@w3.org Sender: www-ql-request@w3.org Resent-Sender: www-ql-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: For those who didn't notice, W3C published a revised version of the XML Query (XQuery) Requirements available at http://www.w3.org/TR/2003/WD-xquery-requirements-20030627 As usual, all the latest info from the Query home page at http://www.w3.org/XML/Query FYI, the revised version of the Requirements fixes an important erratum, described in http://www.w3.org/2003/05/errata-xquery-requirements -M --------------090301030700060109030601-- From Sullivan.Sean@menlolog.com Sun Jul 6 12:53:57 2003 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h66Jruwp015636 for ; Sun, 6 Jul 2003 12:53:57 -0700 Received: from cnfqs039.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id 3B77930F for ; Sun, 6 Jul 2003 12:56:05 -0700 (PDT) Received: by cnfqs039.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Sun, 6 Jul 2003 12:56:04 -0700 Message-ID: <462D5240F6F9154AB0F9B345A5F03E3E3ABB2C@cnfqe029.cnf.prod.cnf.com> From: "Sullivan, Sean C - MWT" To: "'talk@x-query.com'" Date: Sun, 6 Jul 2003 12:56:00 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message x-mimeole: Produced By Microsoft Exchange V6.0.6375.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [xquery-talk] X-Query slides from JavaOne 2003 X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2003 19:53:57 -0000 Oracle's X-Query slides from JavaOne 2003 are online here: http://servlet.java.sun.com/javaone/sf2003/conf/sessions/display-1212.en.jsp From burnside@kattare.com Wed Jul 9 12:42:15 2003 Received: from pyramid-01.kattare.com (pyramid-01.kattare.com [206.163.128.20]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h69JgEwp018670 for ; Wed, 9 Jul 2003 12:42:14 -0700 Received: from localhost (localhost [127.0.0.1]) by pyramid-01.kattare.com (8.12.8/8.12.3) with ESMTP id h69JkOTx027978 for ; Wed, 9 Jul 2003 12:46:24 -0700 Received: from 65.212.181.200 ( [65.212.181.200]) as user burnside@mail.kattare.com by www.kattare.com with HTTP; Wed, 9 Jul 2003 12:46:24 -0700 Message-ID: <1057779984.3f0c71104ee53@www.kattare.com> Date: Wed, 9 Jul 2003 12:46:24 -0700 From: Ethan Burnside To: talk@x-query.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-MailScanner: Found to be clean X-MailScanner-Information: Please contact your ISP for more information - Be sure to include all mail headers X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-7.1, required 5, BAYES_01, USER_AGENT_IMP) Subject: [xquery-talk] testing X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2003 19:42:15 -0000 testing the list, please ignore. -- -------------------------- Ethan Burnside - Founder Kattare Internet Services http://www.kattare.com -------------------------- From burnside@kattare.com Wed Jul 9 12:50:36 2003 Received: from pyramid-01.kattare.com (pyramid-01.kattare.com [206.163.128.20]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h69Joawp018721 for ; Wed, 9 Jul 2003 12:50:36 -0700 Received: from localhost (localhost [127.0.0.1]) by pyramid-01.kattare.com (8.12.8/8.12.3) with ESMTP id h69JsnTx029109 for ; Wed, 9 Jul 2003 12:54:49 -0700 Received: from 65.212.181.200 ( [65.212.181.200]) as user burnside@mail.kattare.com by www.kattare.com with HTTP; Wed, 9 Jul 2003 12:54:49 -0700 Message-ID: <1057780489.3f0c7309cb635@www.kattare.com> Date: Wed, 9 Jul 2003 12:54:49 -0700 From: Ethan Burnside To: talk@x-query.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-MailScanner: Found to be clean X-MailScanner-Information: Please contact your ISP for more information - Be sure to include all mail headers X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-7.1, required 5, BAYES_01, USER_AGENT_IMP) Subject: [xquery-talk] list test X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2003 19:50:36 -0000 list test -- -------------------------- Ethan Burnside - Founder Kattare Internet Services http://www.kattare.com -------------------------- From richard.schochler@lexisnexis.com Mon Jul 7 10:53:34 2003 Received: from tomb.kattare.com (tomb.kattare.com [65.212.180.50]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h67HrXwp016565 for ; Mon, 7 Jul 2003 10:53:33 -0700 Received: from mx02.lexis-nexis.com (mx02.lexis-nexis.com [207.25.178.45]) by tomb.kattare.com (8.12.8/8.12.4) with ESMTP id h67HtFnn013092 for ; Mon, 7 Jul 2003 10:55:16 -0700 Received: from mailgate2.lexis-nexis.com (mailgate2.lexis-nexis.com [138.12.44.45]) by mx02.lexis-nexis.com (8.12.9/8.12.9) with ESMTP id h67HtGnH028973 for ; Mon, 7 Jul 2003 13:55:16 -0400 Received: from lnxdayexch07.lexis-nexis.com (lnxdayexch07.lexis-nexis.com [138.12.12.60]) by mailgate2.lexis-nexis.com (8.12.9/8.12.9) with ESMTP id h67HscuZ011211 for ; Mon, 7 Jul 2003 13:54:39 -0400 Received: by lnxdayexch07.lexis-nexis.com with Internet Mail Service (5.5.2656.59) id ; Mon, 7 Jul 2003 13:55:10 -0400 Message-ID: From: "Schochler, Rick (LNG-DAY)" To: "'talk@x-query.com'" Date: Mon, 7 Jul 2003 13:55:09 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-Mailman-Approved-At: Wed, 09 Jul 2003 14:26:08 -0700 Subject: [xquery-talk] following-sibling and preceding-sibling X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2003 17:53:34 -0000 If I need to do a 'formal' introduction of myself, let me know and I'll do just that...what is the logic/rational behind the apparent restriction of left/right navigation? Is there some other means of accomplishing this that I'm not aware of? Thanks, Rick Schochler From mhk@mhk.me.uk Thu Jul 10 03:34:50 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h6AAYni6020158 for ; Thu, 10 Jul 2003 03:34:50 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (DomainNamesGB Mailserver v4.6.72) with ESMTP id FJMQLY; Thu, 10 Jul 2003 11:50:03 +0100 From: "Michael Kay" To: "'Schochler, Rick \(LNG-DAY\)'" , Subject: RE: [xquery-talk] following-sibling and preceding-sibling Date: Thu, 10 Jul 2003 11:48:27 +0100 Message-ID: <000001c346d0$cb7fad30$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2003 10:34:50 -0000 > what is the logic/rational > behind the apparent restriction of left/right navigation? Is > there some other means of accomplishing this that I'm not aware of? The XQuery WG has had this debate a number of times, and although there are many people who would like to offer the full set of axes, we haven't (so far) been able to sway the argument. But in the next draft, XQuery processors will be *allowed* to offer all the axes, though not "*required* to do so. So we-re making progress... I find it difficult to state the arguments against offering all the axes, since I find them unconvincing. The most common argument is that it's difficult to optimize them - but then, it's even harder to optimize the workaround that the user is forced to write if the axes aren't available. Another argument is that they aren't needed - this seems to come from people who have only ever encountered neat tabular XML that maps directly to relational structures. There is a simple workaround for following-sibling::x, you can write let $current := . return ../child::x[. >> $current] and similarly for preceding-sibling. Michael Kay From alex@ipedo.com Thu Jul 10 16:27:38 2003 Received: from mail.ipedo.com (ip-216-36-69-83.dsl.sjc.megapath.net [216.36.69.83]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h6ANRbi6020831 for ; Thu, 10 Jul 2003 16:27:38 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Subject: RE: [xquery-talk] following-sibling and preceding-sibling Date: Thu, 10 Jul 2003 16:32:58 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: talk Digest, Vol 3, Issue 1 Thread-Index: AcNHFeqbt+u9yf+sS16Ix/6m5vjV2wAJErVg From: "Alex Cheng" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by jhunter.x-query.com id h6ANRbi6020831 X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2003 23:27:38 -0000 > The XQuery WG has had this debate a number of times, and although there > are many people who would like to offer the full set of axes, we haven't > (so far) been able to sway the argument. But in the next draft, XQuery > processors will be *allowed* to offer all the axes, though not > "*required* to do so. So we-re making progress... One axis that many people find very useful is "ancestor", especially when dealing with XML with nested structures, e.g. {-- Find the para in section, subsection, etc. -- Return the book title. --} let $para := .... return $para/ancestor::book/title -- Alex Cheng From schochler3@yahoo.com Fri Jul 11 04:31:51 2003 Received: from web40111.mail.yahoo.com (web40111.mail.yahoo.com [66.218.78.45]) by jhunter.x-query.com (8.12.8/8.12.4) with SMTP id h6BBVpi6021328 for ; Fri, 11 Jul 2003 04:31:51 -0700 Message-ID: <20030711114348.30724.qmail@web40111.mail.yahoo.com> Received: from [198.185.18.207] by web40111.mail.yahoo.com via HTTP; Fri, 11 Jul 2003 04:43:48 PDT Date: Fri, 11 Jul 2003 04:43:48 -0700 (PDT) From: rick schochler Subject: RE: [xquery-talk] following-sibling and preceding-sibling To: Alex Cheng , talk@x-query.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2003 11:31:51 -0000 Sure. Still, it seems that it would be speedier (especially when talking about querying large amounts of data) for an xquery engine to look left or right, rather than having to go back up a node tree and look down again. --- Alex Cheng wrote: > > > The XQuery WG has had this debate a number of > times, and although > there > > are many people who would like to offer the full > set of axes, we > haven't > > (so far) been able to sway the argument. But in > the next draft, XQuery > > processors will be *allowed* to offer all the > axes, though not > > "*required* to do so. So we-re making progress... > > One axis that many people find very useful is > "ancestor", especially > when dealing with XML with nested structures, e.g. > > {-- Find the para in section, subsection, etc. > -- Return the book title. > --} > let $para := .... > return $para/ancestor::book/title > > > -- Alex Cheng > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk From richard.schochler@lexisnexis.com Thu Jul 10 05:17:31 2003 Received: from mx02.lexis-nexis.com (mx02.lexis-nexis.com [207.25.178.45]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h6ACHVi6020312 for ; Thu, 10 Jul 2003 05:17:31 -0700 Received: from mailgate2.lexis-nexis.com (mailgate2.lexis-nexis.com [138.12.44.45]) by mx02.lexis-nexis.com (8.12.9/8.12.9) with ESMTP id h6ACHjnH025823; Thu, 10 Jul 2003 08:17:45 -0400 Received: from lnxdayexch07.lexis-nexis.com (lnxdayexch07.lexis-nexis.com [138.12.12.60]) by mailgate2.lexis-nexis.com (8.12.9/8.12.9) with ESMTP id h6ACH7uZ022766; Thu, 10 Jul 2003 08:17:07 -0400 Received: by lnxdayexch07.lexis-nexis.com with Internet Mail Service (5.5.2656.59) id ; Thu, 10 Jul 2003 08:17:38 -0400 Message-ID: From: "Schochler, Rick (LNG-DAY)" To: "'Michael Kay'" , "Schochler, Rick (LNG-DAY)" , talk@x-query.com Subject: RE: [xquery-talk] following-sibling and preceding-sibling Date: Thu, 10 Jul 2003 08:17:37 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-Mailman-Approved-At: Fri, 11 Jul 2003 11:26:37 -0700 Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2003 12:17:32 -0000 Thanks for the response. The absence of preceding and following sibling axes strikes me as rather odd, if for no other reason than the fact that xquery is being developed side by side with xpath 2.0 (and thus, I'd assume that it would fully implement xpath functionality). -----Original Message----- From: Michael Kay [mailto:mhk@mhk.me.uk] Sent: Thursday, July 10, 2003 6:48 AM To: 'Schochler, Rick (LNG-DAY)'; talk@x-query.com Subject: RE: [xquery-talk] following-sibling and preceding-sibling > what is the logic/rational > behind the apparent restriction of left/right navigation? Is > there some other means of accomplishing this that I'm not aware of? The XQuery WG has had this debate a number of times, and although there are many people who would like to offer the full set of axes, we haven't (so far) been able to sway the argument. But in the next draft, XQuery processors will be *allowed* to offer all the axes, though not "*required* to do so. So we-re making progress... I find it difficult to state the arguments against offering all the axes, since I find them unconvincing. The most common argument is that it's difficult to optimize them - but then, it's even harder to optimize the workaround that the user is forced to write if the axes aren't available. Another argument is that they aren't needed - this seems to come from people who have only ever encountered neat tabular XML that maps directly to relational structures. There is a simple workaround for following-sibling::x, you can write let $current := . return ../child::x[. >> $current] and similarly for preceding-sibling. Michael Kay From alex@ipedo.com Fri Jul 11 11:36:16 2003 Received: from mail.ipedo.com (ip-216-36-69-83.dsl.sjc.megapath.net [216.36.69.83]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h6BIaGi6021694 for ; Fri, 11 Jul 2003 11:36:16 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Subject: RE: [xquery-talk] following-sibling and preceding-sibling Date: Fri, 11 Jul 2003 11:39:07 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [xquery-talk] following-sibling and preceding-sibling Thread-Index: AcNHobFXO+8dKzUCTfGW/44vWdfhCwAOd8aw From: "Alex Cheng" To: "rick schochler" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by jhunter.x-query.com id h6BIaGi6021694 Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2003 18:36:17 -0000 Yes, I agree. Looking left, right, up are all useful axes to have in XQuery. Thanks. -- alex -----Original Message----- From: rick schochler [mailto:schochler3@yahoo.com] Sent: Friday, July 11, 2003 4:44 AM To: Alex Cheng; talk@x-query.com Subject: RE: [xquery-talk] following-sibling and preceding-sibling Sure. Still, it seems that it would be speedier (especially when talking about querying large amounts of data) for an xquery engine to look left or right, rather than having to go back up a node tree and look down again. --- Alex Cheng wrote: > > > The XQuery WG has had this debate a number of > times, and although > there > > are many people who would like to offer the full > set of axes, we > haven't > > (so far) been able to sway the argument. But in > the next draft, XQuery > > processors will be *allowed* to offer all the > axes, though not > > "*required* to do so. So we-re making progress... > > One axis that many people find very useful is > "ancestor", especially > when dealing with XML with nested structures, e.g. > > {-- Find the para in section, subsection, etc. > -- Return the book title. > --} > let $para := .... > return $para/ancestor::book/title > > > -- Alex Cheng > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk From jhunter@servlets.com Fri Jul 18 18:58:42 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h6J1wgi6029181 for ; Fri, 18 Jul 2003 18:58:42 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h6J274cO004217 for ; Fri, 18 Jul 2003 19:07:06 -0700 (PDT) Message-ID: <3F18A6D9.9050705@servlets.com> Date: Fri, 18 Jul 2003 19:03:05 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@x-query.com Content-Type: multipart/mixed; boundary="------------040201010702050604070901" Subject: [xquery-talk] [Fwd: [xml-dev] XQuery Primer] X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 01:58:42 -0000 This is a multi-part message in MIME format. --------------040201010702050604070901 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit --------------040201010702050604070901 Content-Type: message/rfc822; name="[xml-dev] XQuery Primer" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="[xml-dev] XQuery Primer" Return-Path: Received: from alias2.acm.org ([199.222.69.92]) by carlin.mail.atl.earthlink.net (Earthlink Mail Service) with ESMTP id 19Drh7143Nl3q80 for ; Fri, 18 Jul 2003 05:11:37 -0400 (EDT) Received: from mail.oasis-open.org ([209.202.168.102]) by alias2.acm.org (ACM Email Forwarding Service) with SMTP id CRY73883 for ; Fri, 18 Jul 2003 05:11:37 -0400 Received: (qmail 22660 invoked by uid 60909); 18 Jul 2003 08:52:41 -0000 Mailing-List: contact xml-dev-help@lists.xml.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list xml-dev@lists.xml.org Received: (qmail 22652 invoked by uid 60881); 18 Jul 2003 08:52:41 -0000 X-Spam-Status: No, hits=2.4 required=8.0 Message-ID: From: "Harbarth, Juliane" To: "'xml-dev@lists.xml.org'" Date: Fri, 18 Jul 2003 11:09:35 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34D0C.4EA77710" Subject: [xml-dev] XQuery Primer ------_=_NextPart_001_01C34D0C.4EA77710 Content-Type: text/plain Inspired by a request some time ago I have written an XQuery 1.0 Primer as an introduction to the W3C's suite of Working Drafts. It is availabe on my company's website at http://www.softwareag.com/xml/tools/xquery_primer.pdf . I would like others to read it to get introduced to XQuery and give me some feedback. Feel free to post me any suggestions, remarks, complaints, etc. Regards, Juliane. ------_=_NextPart_001_01C34D0C.4EA77710 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Message
Inspired by a=20 request some time ago = I have written an=20 XQuery 1.0 Primer as an =
introduction to the W3C's suite of Working = Drafts. It is availabe on my=20 company's
website at http://ww= w.softwareag.com/xml/tools/xquery_primer.pdf .
 
I would like others to read it to get = introduced=20 to XQuery and give me some
feedback. Feel free to post me any = suggestions,=20 remarks, complaints, etc.
 
Regards,
Juliane. 
 ------_=_NextPart_001_01C34D0C.4EA77710-- --------------040201010702050604070901-- From jhunter@servlets.com Fri Jul 25 01:14:56 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h6P8EtHA000515 for ; Fri, 25 Jul 2003 01:14:55 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h6P8SeoO007823 for ; Fri, 25 Jul 2003 01:28:44 -0700 (PDT) Message-ID: <3F20E914.50209@servlets.com> Date: Fri, 25 Jul 2003 01:23:48 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@x-query.com Content-Type: multipart/mixed; boundary="------------030305050304080704090001" Subject: [xquery-talk] [Fwd: Re: XQuery Risk Assessment] X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 08:14:56 -0000 This is a multi-part message in MIME format. --------------030305050304080704090001 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit --------------030305050304080704090001 Content-Type: message/rfc822; name="Re: XQuery Risk Assessment" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Re: XQuery Risk Assessment" Return-Path: Received: from alias2.acm.org ([199.222.69.92]) by wanamaker.mail.atl.earthlink.net (Earthlink Mail Service) with ESMTP id 19FcaQ5JN3Nl3oJ0 for ; Wed, 23 Jul 2003 01:28:24 -0400 (EDT) Received: from frink.w3.org ([18.29.1.71]) by alias2.acm.org (ACM Email Forwarding Service) with ESMTP id CRY73883; Wed, 23 Jul 2003 01:28:24 -0400 Received: from frink.w3.org (localhost [127.0.0.1]) by frink.w3.org (8.12.9/8.12.9) with ESMTP id h6N5RoEh028800; Wed, 23 Jul 2003 01:27:50 -0400 (EDT) Received: (from lists@localhost) by frink.w3.org (8.12.9/8.12.9/Submit) id h6N5RkSI028794; Wed, 23 Jul 2003 01:27:46 -0400 (EDT) Resent-Date: Wed, 23 Jul 2003 01:27:46 -0400 (EDT) Resent-Message-Id: <200307230527.h6N5RkSI028794@frink.w3.org> Received: from dr-nick.w3.org (dr-nick.w3.org [18.29.1.73]) by frink.w3.org (8.12.9/8.12.9) with ESMTP id h6N5RjEh028760 for ; Wed, 23 Jul 2003 01:27:45 -0400 (EDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by dr-nick.w3.org (8.12.3/8.12.3/Debian-6.4) with ESMTP id h6N5Rivx029767 for ; Wed, 23 Jul 2003 01:27:44 -0400 Received: from xpider (12-230-206-202.client.attbi.com[12.230.206.202](untrusted sender)) by comcast.net (rwcrmhc11) with SMTP id <2003072305273801300ou4ehe>; Wed, 23 Jul 2003 05:27:38 +0000 From: "Michael Brundage" To: "'Howard Katz'" , "'dwight funk'" , Date: Tue, 22 Jul 2003 22:28:01 -0700 Message-ID: <000001c350db$2fe2d2c0$6501a8c0@xpider> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C350A0.8383FAC0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: RE: XQuery Risk Assessment X-Archived-At: http://www.w3.org/mid/000001c350db$2fe2d2c0$6501a8c0@xpider Resent-From: www-ql@w3.org X-Mailing-List: archive/latest/543 X-Loop: www-ql@w3.org Sender: www-ql-request@w3.org Resent-Sender: www-ql-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C350A0.8383FAC0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable You should watch the public-qt-comments alias; plenty of activity there. Hundreds of last call comments on the Data Model and F&O alone. =20 There are some parts of the current working drafts that are very likely = to change: - semantics of modules (new in the May 2 draft) - serialization (new in the May 2 draft) - semantics of construction (e.g., implicit validation is new in the May = 2 draft) - xdt:dayTimeDuration, xdt:yearMonthDuration, and all functions that = work with date/time types - changes to some function definitions - various type system-related issues (implicit conversions, validation, untypedAtomic vs. anySimpleType vs. anyType, etc.) =20 Otherwise, the current drafts do seem pretty stable. However, every publicly available implementation I've tested differs from the current drafts in major areas. =20 Having watched this area closely for the past two years, my opinion is = that implementations will continue to lag behind the drafts by at least six months from now until XQuery is done, and also that a production-quality implementation of XQuery (matching, say, the current best-of-class XSLT implementations in robustness and performance) is at least 6-12 months = away. If your development schedule can accomodate that, then you should be = fine. If you need something sooner, then you should seriously consider = existing technologies. =20 =20 Cheers, =20 Michael Brundage xquery@comcast.net Writing as Author, "XQuery: The XML Query Language" (Addison-Wesley, to appear = 2003) Co-author, "Professional XML Databases" (Wrox Press, 2000) not as Technical Lead Common Query Runtime/XML Query Processing WebData XML Team Microsoft =20 =20 -----Original Message----- From: www-ql-request@w3.org [mailto:www-ql-request@w3.org] On Behalf Of Howard Katz Sent: Tuesday, July 22, 2003 2:40 PM To: dwight funk; www-ql@w3.org Subject: RE: XQuery Risk Assessment No major tectonic plate movement in sight. I'd recommend anybody's query engine but my own. :-) Howard -----Original Message----- From: www-ql-request@w3.org [mailto:www-ql-request@w3.org]On Behalf Of dwight funk Sent: Tuesday, July 22, 2003 1:19 PM To: www-ql@w3.org Subject: XQuery Risk Assessment I've been asked to make a risk assessment of becoming an early adopter = of XQuery based technologies.=20 I've been watching this lists for a while now and the activity seems to = be relatively low. This implies to me the risk is low and the current = working draft is pretty stable. Can anyone provide opinions or observations?=20 Dwight Funk=20 Software Architect - XML Technologies=20 POWERWAY, Inc.=20 (317) 598-6745=20 MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO = WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, = CONFIDENTIAL AND EXEMPT FROM DISCLOSURE. If the reader of this message is not the recipient or an employee or agent responsible for delivering the = message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. = If you have received this communication in error, please notify the sender immediately by E-Mail and return the original message to the sender. = Thank you. ------=_NextPart_000_0001_01C350A0.8383FAC0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
You=20 should watch the public-qt-comments alias; plenty of activity = there. =20 Hundreds of last call comments on the Data Model and F&O=20 alone.
 
There=20 are some parts of the current working drafts that are very likely to=20 change:
-=20 semantics of modules (new in the May 2 draft)
-=20 serialization (new in the May 2 draft)
-=20 semantics of construction (e.g., implicit validation is new in the May 2 = draft)
- xdt:dayTimeDuration, xdt:yearMonthDuration, = and all=20 functions that work with date/time = types
-=20 changes to some function definitions
-=20 various type system-related issues (implicit conversions, validation,=20 untypedAtomic vs. anySimpleType vs. anyType, etc.)
 
Otherwise, the current drafts do seem pretty stable.  = However, every=20 publicly available implementation I've tested differs from the current = drafts in=20 major areas.
 
Having=20 watched this area closely for the past two years, my opinion is that=20 implementations will continue to lag behind the drafts by at least six = months=20 from now until XQuery is done, and also that a production-quality = implementation=20 of XQuery (matching, say, the current best-of-class XSLT implementations = in=20 robustness and performance) is at least 6-12 months away.  If your=20 development schedule can accomodate that, then you should be fine.  = If you=20 need something sooner, then you should seriously consider existing=20 technologies.
 
 
Cheers,
 
Michael Brundage
xquery@comcast.net

Writing = as
Author,=20 "XQuery: The XML Query Language" (Addison-Wesley, to appear = 2003)
Co-author,=20 "Professional XML Databases" (Wrox Press, 2000)

not = as
Technical=20 Lead
Common Query Runtime/XML Query Processing
WebData XML=20 Team
Microsoft
 
 
-----Original = Message-----
From:=20 www-ql-request@w3.org [mailto:www-ql-request@w3.org] On Behalf Of = Howard=20 Katz
Sent: Tuesday, July 22, 2003 2:40 PM
To: dwight = funk;=20 www-ql@w3.org
Subject: RE: XQuery Risk = Assessment

No major=20 tectonic plate movement in sight. I'd recommend anybody's query engine = but my=20 own. :-)
Howard
-----Original Message-----
From: = www-ql-request@w3.org=20 [mailto:www-ql-request@w3.org]On Behalf Of dwight=20 funk
Sent: Tuesday, July 22, 2003 1:19 PM
To:=20 www-ql@w3.org
Subject: XQuery Risk=20 Assessment


I've been asked to make a risk assessment of = becoming an=20 early adopter of XQuery based technologies.

I've been watching this lists for a while now and = the=20 activity seems to be relatively low. This implies to me the risk is = low and=20 the current working draft is pretty stable.

Can anyone provide opinions or = observations?

Dwight Funk
Software = Architect - XML=20 Technologies
POWERWAY, Inc. =
(317) 598-6745

MESSAGE IS INTENDED ONLY FOR THE USE OF THE = INDIVIDUAL OR=20 ENTITY TO WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS=20 PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE. If the reader = of this=20 message is not the recipient or an employee or agent = responsible  for=20 delivering the message to the intended recipient, you are hereby = notified=20 that any dissemination, distribution, or copying of this = communication is=20 strictly prohibited.  If you have received this communication = in error,=20 please notify the sender immediately by E-Mail and return the = original=20 message to the sender.  Thank=20 you.

------=_NextPart_000_0001_01C350A0.8383FAC0-- --------------030305050304080704090001-- From Dmitri.Colebatch@toyota.com.au Thu Jul 31 00:24:42 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h6V7N2HA012943 for ; Thu, 31 Jul 2003 00:23:41 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Thu, 31 Jul 2003 17:17:47 +1000 Sensitivity: To: talk@x-query.com X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Thu, 31 Jul 2003 17:24:30 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 31/07/2003 17:26:17 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [xquery-talk] changing structure based on input value X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2003 07:24:42 -0000 hey all, firstly, I'm new to this list, so if this has been discussed already could someone please point me at the appropriate archive (I did have a short look at them with no joy).. I want to select one document or another based on the content of my input document... I think this is better explained by example: given 4 blah I want to create blah but based on 5 blah I want to create blah Does this make sense? I'm not sure if its possible or not. Any pointers would be appreciated. The closest thing I can think of is to use xpath to check the value, but I'm not sure how to completely change the structure based on that... cheers dim - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From Mark_R_Maxey@raytheon.com Thu Jul 31 06:04:40 2003 Received: from lax-gate3.raytheon.com (lax-gate3.raytheon.com [199.46.200.232]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h6VD4eHA013291 for ; Thu, 31 Jul 2003 06:04:40 -0700 Received: from ds02w00.directory.ray.com (ds02w00.directory.ray.com [147.25.146.118]) by lax-gate3.raytheon.com (8.12.9/8.12.9) with ESMTP id h6VD4XJX019407; Thu, 31 Jul 2003 06:04:33 -0700 (PDT) Received: from ds02w00.directory.ray.com (localhost [127.0.0.1]) by ds02w00.directory.ray.com (8.12.9/8.12.1) with ESMTP id h6VD3lpW014797; Thu, 31 Jul 2003 13:04:31 GMT Received: Received: from mk2-mta01.mck.us.ray.com (mk2-mta01.mck.us.ray.com [138.126.190.145]) by ds02w00.directory.ray.com (8.12.9/8.12.9) with ESMTP id h6VD3gGt014765 sender Mark_R_Maxey@raytheon.com; Thu, 31 Jul 2003 13:03:43 GMT Received: from raytheon.com ([162.36.244.78]) by mk2-mta01.mck.us.ray.com (Lotus Domino Release 5.0.12) with ESMTP id 2003073108033163:243102 ; Thu, 31 Jul 2003 08:03:31 -0500 Message-ID: <3F2913A3.1090500@raytheon.com> Date: Thu, 31 Jul 2003 08:03:31 -0500 From: Mark R Maxey Organization: Raytheon User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en,pdf MIME-Version: 1.0 To: Dmitri.Colebatch@toyota.com.au Subject: Re: [xquery-talk] changing structure based on input value References: In-Reply-To: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list Reply-To: Mark_R_Maxey@raytheon.com List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2003 13:04:40 -0000 You can do something like this: for $indoc in doc("inputDocument.xml") return if (data($indoc/abc) = 4) then { $indoc/xyz/text() } else if (data($indoc/abc) = 5) { $indoc/xyz/text() } Dmitri.Colebatch@toyota.com.au wrote: >hey all, > >firstly, I'm new to this list, so if this has been discussed already could >someone please point me at the appropriate archive (I did have a short look >at them with no joy).. > >I want to select one document or another based on the content of my input >document... I think this is better explained by example: > >given > > > 4 > blah > > >I want to create > > > blah > > >but based on > > > 5 > blah > > >I want to create > > > blah > > >Does this make sense? I'm not sure if its possible or not. Any pointers >would be appreciated. The closest thing I can think of is to use xpath to >check the value, but I'm not sure how to completely change the structure >based on that... > >cheers >dim > >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > DISCLAIMER >* This email and any attachment may contain confidential information. > If you are not the intended recipient you are not authorised to copy > or disclose all or any part of it without the prior written consent > of Toyota. >* Opinions expressed in this email and any attachment are those of the > sender and not necessarily the opinions of Toyota. >* Please scan this email and any attachment for viruses. Toyota does > not accept any responsibility for problems caused by viruses, whether > it is Toyota's fault or not. >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > >_______________________________________________ >talk@x-query.com >http://www.x-query.com/mailman/listinfo/talk > > > -- Mark Maxey (972)205-5760 Mark_R_Maxey@Raytheon.com From schochler3@yahoo.com Thu Jul 31 06:20:14 2003 Received: from web40104.mail.yahoo.com (web40104.mail.yahoo.com [66.218.78.38]) by jhunter.x-query.com (8.12.8/8.12.4) with SMTP id h6VDKEHA013316 for ; Thu, 31 Jul 2003 06:20:14 -0700 Message-ID: <20030731132009.88873.qmail@web40104.mail.yahoo.com> Received: from [198.185.18.207] by web40104.mail.yahoo.com via HTTP; Thu, 31 Jul 2003 06:20:09 PDT Date: Thu, 31 Jul 2003 06:20:09 -0700 (PDT) From: rick schochler Subject: Re: [xquery-talk] changing structure based on input value To: Dmitri.Colebatch@toyota.com.au, talk@x-query.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2003 13:20:14 -0000 Well, you could have two distinct queries on the set of foobar docs, both looking similar. The first one looking something like this: { for $x in /foobar[child::abc/text() = '4'] return {$x/xyz} } and the second one looking like this: { for $x in /foobar[child::abc/text() = '5'] return {$x/xyz} } Or, you could do a conditional test (you may have to tweek this a bit): for $x in /foobar/abc return if($x = '4') then {$x} else if($x = '5') then {$x} Hope this helps, Rick --- Dmitri.Colebatch@toyota.com.au wrote: > hey all, > > firstly, I'm new to this list, so if this has been > discussed already could > someone please point me at the appropriate archive > (I did have a short look > at them with no joy).. > > I want to select one document or another based on > the content of my input > document... I think this is better explained by > example: > > given > > > 4 > blah > > > I want to create > > > blah > > > but based on > > > 5 > blah > > > I want to create > > > blah > > > Does this make sense? I'm not sure if its possible > or not. Any pointers > would be appreciated. The closest thing I can think > of is to use xpath to > check the value, but I'm not sure how to completely > change the structure > based on that... > > cheers > dim > > - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - - - - - - - > DISCLAIMER > * This email and any attachment may contain > confidential information. > If you are not the intended recipient you are not > authorised to copy > or disclose all or any part of it without the > prior written consent > of Toyota. > * Opinions expressed in this email and any > attachment are those of the > sender and not necessarily the opinions of Toyota. > * Please scan this email and any attachment for > viruses. Toyota does > not accept any responsibility for problems caused > by viruses, whether > it is Toyota's fault or not. > - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - - - - - - - > > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk From Dmitri.Colebatch@toyota.com.au Thu Jul 31 17:44:04 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h710hpHA013892 for ; Thu, 31 Jul 2003 17:43:58 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Fri, 01 Aug 2003 10:38:08 +1000 Sensitivity: Subject: Re: [xquery-talk] changing structure based on input value To: Mark_R_Maxey@raytheon.com X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Fri, 1 Aug 2003 10:44:59 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 01/08/2003 10:46:41 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Cc: talk@x-query.com, Dmitri.Colebatch@toyota.com.au X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 00:44:04 -0000 Mark, Thats exactly what I was looking for, thanks... apologies for the simple question (o: btw - I had to make two changes, the "else if" needed a "then" and the whole thing needed an "else": for $input in $this return if ($input/foobar/abc/text() = 4) then { $input/foobar/xyz/text() } else if ($input/foobar/abc/text() = 5) then { $input/foobar/xyz/text() } else { $input/foobar/abc/text() } but it does what is required. thanks again. cheers dim Mark R Maxey on 31/07/2003 11:03:31 PM Please respond to Mark_R_Maxey@raytheon.com To: Dmitri.Colebatch@toyota.com.au cc: talk@x-query.com Subject: Re: [xquery-talk] changing structure based on input value You can do something like this: for $indoc in doc("inputDocument.xml") return if (data($indoc/abc) = 4) then { $indoc/xyz/text() } else if (data($indoc/abc) = 5) { $indoc/xyz/text() } Dmitri.Colebatch@toyota.com.au wrote: >hey all, > >firstly, I'm new to this list, so if this has been discussed already could >someone please point me at the appropriate archive (I did have a short look >at them with no joy).. > >I want to select one document or another based on the content of my input >document... I think this is better explained by example: > >given > > > 4 > blah > > >I want to create > > > blah > > >but based on > > > 5 > blah > > >I want to create > > > blah > > >Does this make sense? I'm not sure if its possible or not. Any pointers >would be appreciated. The closest thing I can think of is to use xpath to >check the value, but I'm not sure how to completely change the structure >based on that... > >cheers >dim > >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > DISCLAIMER >* This email and any attachment may contain confidential information. > If you are not the intended recipient you are not authorised to copy > or disclose all or any part of it without the prior written consent > of Toyota. >* Opinions expressed in this email and any attachment are those of the > sender and not necessarily the opinions of Toyota. >* Please scan this email and any attachment for viruses. Toyota does > not accept any responsibility for problems caused by viruses, whether > it is Toyota's fault or not. >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > >_______________________________________________ >talk@x-query.com >http://www.x-query.com/mailman/listinfo/talk > > > -- Mark Maxey (972)205-5760 Mark_R_Maxey@Raytheon.com - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From Dmitri.Colebatch@toyota.com.au Thu Jul 31 17:45:02 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h710iYHA013904 for ; Thu, 31 Jul 2003 17:44:48 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Fri, 01 Aug 2003 10:38:52 +1000 Sensitivity: Subject: Re: [xquery-talk] changing structure based on input value To: rick schochler X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Fri, 1 Aug 2003 10:45:44 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 01/08/2003 10:47:25 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Cc: talk@x-query.com, Dmitri.Colebatch@toyota.com.au X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 00:45:02 -0000 Rick, Thanks for the response, I was looking to avoid having to have two distinct queries and have gone with the suggestion Mark offered. cheers dim rick schochler @x-query.com on 31/07/2003 11:20:09 PM Sent by: talk-bounces@x-query.com To: Dmitri.Colebatch@toyota.com.au, talk@x-query.com cc: Subject: Re: [xquery-talk] changing structure based on input value Well, you could have two distinct queries on the set of foobar docs, both looking similar. The first one looking something like this: { for $x in /foobar[child::abc/text() = '4'] return {$x/xyz} } and the second one looking like this: { for $x in /foobar[child::abc/text() = '5'] return {$x/xyz} } Or, you could do a conditional test (you may have to tweek this a bit): for $x in /foobar/abc return if($x = '4') then {$x} else if($x = '5') then {$x} Hope this helps, Rick --- Dmitri.Colebatch@toyota.com.au wrote: > hey all, > > firstly, I'm new to this list, so if this has been > discussed already could > someone please point me at the appropriate archive > (I did have a short look > at them with no joy).. > > I want to select one document or another based on > the content of my input > document... I think this is better explained by > example: > > given > > > 4 > blah > > > I want to create > > > blah > > > but based on > > > 5 > blah > > > I want to create > > > blah > > > Does this make sense? I'm not sure if its possible > or not. Any pointers > would be appreciated. The closest thing I can think > of is to use xpath to > check the value, but I'm not sure how to completely > change the structure > based on that... > > cheers > dim > > - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - - - - - - - > DISCLAIMER > * This email and any attachment may contain > confidential information. > If you are not the intended recipient you are not > authorised to copy > or disclose all or any part of it without the > prior written consent > of Toyota. > * Opinions expressed in this email and any > attachment are those of the > sender and not necessarily the opinions of Toyota. > * Please scan this email and any attachment for > viruses. Toyota does > not accept any responsibility for problems caused > by viruses, whether > it is Toyota's fault or not. > - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - - - - - - - > > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk _______________________________________________ talk@x-query.com http://www.x-query.com/mailman/listinfo/talk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From Dmitri.Colebatch@toyota.com.au Thu Jul 31 18:09:22 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7118lHA013949 for ; Thu, 31 Jul 2003 18:09:07 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Fri, 01 Aug 2003 11:03:32 +1000 Sensitivity: To: talk@x-query.com X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Fri, 1 Aug 2003 11:10:02 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 01/08/2003 11:12:05 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [xquery-talk] function definitions X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 01:09:22 -0000 hey all, another question.... hopefully not quite as trivial as the last. I'm trying to define my own function, and have the following in my header, however I am getting parse exceptions from the bea weblogic implementation. Can someone tell me if this is a problem with my code or their implementation... define function convertSAPDateTime($dateNode as node(), $timeNode as node()) as xs:dateTime { let $dateStr := data($dateNode) let $yyyy := xf:substring($dateStr, 1, 4) let $mm := xf:substring($dateStr, 5, 2) let $dd := xf:substring($dateStr,7, 2) let $timeStr := data($timeNode) let $HH := xf:substring($timeStr, 1, 2) let $mi := xf:substring($timeStr, 3, 2) let $ss := xf:substring($timeStr, 5, 2) return xf:dateTime(xf:concat($yyyy, '-', $mm, '-', $dd, 'T', $HH, ':', $mi, ':', $ss)) } the code inside the braces works fine when not defined as part of a function, but I am getting parse exceptions on the "as" in "$dateNode as node()". If I remove the "as node()" then it works fine, however I then have the wrong type for the data function... I assume could cast it, but as I understand it the above should work... fwiw I'm using http://www.w3.org/TR/xquery/#FunctionDefns as my reference. thanks again for your help. cheers dim - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From Dmitri.Colebatch@toyota.com.au Thu Jul 31 20:52:34 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h713pnHA014096 for ; Thu, 31 Jul 2003 20:52:10 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Fri, 01 Aug 2003 13:30:57 +1000 Sensitivity: To: talk@x-query.com X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Fri, 1 Aug 2003 13:30:04 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 01/08/2003 13:39:30 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [xquery-talk] group by queries - a more efficient approach X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 03:52:34 -0000 hey again, hope that I'm not imposing too much on this list... definately making progress, would like some thoughts on group by style queries... Suppose I have this document: Struts Java EJB Java Patterns Design Refactoring Design XSLT XML and I want to create multiple documents (nodes), grouped by subject - I couldn't find any mention of any support for group by queries, so I've used the following: for $s in distinct-values($this/mydata/book/subject) return { for $book in $this/mydata/book[subject/text() = $s/text()] return {$book/name} {$book/subject} } which works, but "feels" like there might be a better approach... has anyone here done this sort of thing before? any ideas? the reason I'm doing this is that I'm receiving a document in batch mode that has address information contained in its items - each item might go to a different destination, so I want to "re-batch" the document into smaller documents to be sent to their final destination. cheers, and thanks again dim - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From jhunter@servlets.com Thu Jul 31 21:00:46 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7140jHA014112 for ; Thu, 31 Jul 2003 21:00:46 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h713xooO010833; Thu, 31 Jul 2003 20:59:53 -0700 (PDT) Message-ID: <3F29E4A9.3060907@servlets.com> Date: Thu, 31 Jul 2003 20:55:21 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitri.Colebatch@toyota.com.au Subject: Re: [xquery-talk] function definitions References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 04:00:46 -0000 Are you sure the BEA implementation supports the May draft? The "as" syntax like you're using is from May. You can see if the round-half-to-even() or trace() functions are implemented. Those being implemented would indicate it's May. -jh- Dmitri.Colebatch@toyota.com.au wrote: > hey all, > > another question.... hopefully not quite as trivial as the last. > > I'm trying to define my own function, and have the following in my header, > however I am getting parse exceptions from the bea weblogic implementation. > Can someone tell me if this is a problem with my code or their > implementation... > > define function convertSAPDateTime($dateNode as node(), $timeNode as > node()) > as xs:dateTime > { > let $dateStr := data($dateNode) > let $yyyy := xf:substring($dateStr, 1, 4) > let $mm := xf:substring($dateStr, 5, 2) > let $dd := xf:substring($dateStr,7, 2) > > let $timeStr := data($timeNode) > let $HH := xf:substring($timeStr, 1, 2) > let $mi := xf:substring($timeStr, 3, 2) > let $ss := xf:substring($timeStr, 5, 2) > > return xf:dateTime(xf:concat($yyyy, '-', $mm, '-', $dd, 'T', $HH, > ':', $mi, ':', $ss)) > } > > the code inside the braces works fine when not defined as part of a > function, but I am getting parse exceptions on the "as" in "$dateNode as > node()". If I remove the "as node()" then it works fine, however I then > have the wrong type for the data function... I assume could cast it, but as > I understand it the above should work... > > fwiw I'm using http://www.w3.org/TR/xquery/#FunctionDefns as my reference. > > thanks again for your help. > > cheers > dim > > > > > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > DISCLAIMER > * This email and any attachment may contain confidential information. > If you are not the intended recipient you are not authorised to copy > or disclose all or any part of it without the prior written consent > of Toyota. > * Opinions expressed in this email and any attachment are those of the > sender and not necessarily the opinions of Toyota. > * Please scan this email and any attachment for viruses. Toyota does > not accept any responsibility for problems caused by viruses, whether > it is Toyota's fault or not. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk > From jhunter@servlets.com Thu Jul 31 21:02:00 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h71420HA014124 for ; Thu, 31 Jul 2003 21:02:00 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h7143MoO010860; Thu, 31 Jul 2003 21:03:23 -0700 (PDT) Message-ID: <3F29E57D.4040900@servlets.com> Date: Thu, 31 Jul 2003 20:58:53 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitri.Colebatch@toyota.com.au Subject: Re: [xquery-talk] group by queries - a more efficient approach References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 04:02:00 -0000 > for $s in distinct-values($this/mydata/book/subject) > return > > { > for $book in $this/mydata/book[subject/text() = $s/text()] > return > > {$book/name} > {$book/subject} > > } > I suspect something like this would work. I haven't run it or anything. Basically you can remove the /text() node tests and can return the book nodes directly without needing a FLWOR. for $s in distinct-values($this/mydata/book/subject) return { $this/mydata/book[subject = $s] } -jh- From Dmitri.Colebatch@toyota.com.au Thu Jul 31 22:49:26 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h715kPHA014203 for ; Thu, 31 Jul 2003 22:47:01 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Fri, 01 Aug 2003 15:39:01 +1000 Sensitivity: Subject: Re: [xquery-talk] group by queries - a more efficient approach To: Jason Hunter X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Fri, 1 Aug 2003 14:14:28 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 01/08/2003 15:47:34 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 05:49:27 -0000 Jason, Thanks for the tip.... problem is that my contrieved example didn't really show what I need to do. I want to modify the structure more than my example shows. Your suggestion does work, but I cant see a way to step from that to having access to a $book variable - am I right that I do need the for loop to get access to that? thanks dim Jason Hunter @x-query.com on 01/08/2003 01:58:53 PM Sent by: talk-bounces@x-query.com To: Dmitri.Colebatch@toyota.com.au cc: talk@x-query.com Subject: Re: [xquery-talk] group by queries - a more efficient approach > for $s in distinct-values($this/mydata/book/subject) > return > > { > for $book in $this/mydata/book[subject/text() = $s/text()] > return > > {$book/name} > {$book/subject} > > } > I suspect something like this would work. I haven't run it or anything. Basically you can remove the /text() node tests and can return the book nodes directly without needing a FLWOR. for $s in distinct-values($this/mydata/book/subject) return { $this/mydata/book[subject = $s] } -jh- _______________________________________________ talk@x-query.com http://www.x-query.com/mailman/listinfo/talk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From Dmitri.Colebatch@toyota.com.au Fri Aug 1 02:08:19 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7197vHA014396 for ; Fri, 1 Aug 2003 02:08:08 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Fri, 01 Aug 2003 19:00:35 +1000 Sensitivity: To: talk@x-query.com X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Fri, 1 Aug 2003 16:57:44 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 01/08/2003 19:09:09 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [xquery-talk] next node (sibling) X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 09:08:19 -0000 hey again, Apologies for bombarding the list with questions, but you're all being very helpful (o: I've also got past most of the stuff I had to do witht his much quicker than I thought I would, thanks to you guys... I'm now working with a document with a structure like the following: hdr update 123 detail bar xyz hdr delete 456 hdr update 789 detail qwerty crazy as the names suggest, this is for updating data between two systems - I need to receive the message from system A and send it to system B in the appropriate format. The structure above is how I receive it from system A. Now, its not immediately obvious how the above is intended to work, but essentially each "item header record" [item/item-type/text() = 'hdr' ] will indicate an update (or new record), or a delete. In the case of an update, I know that the next item record will be an "item detail record" [item/item-type/text() = 'detail'] which I use to get the detail of the changes. The problem of course is that the structure requires a stateful approach to the conversion. What I've tried to do is select all the item header records, and look at whether they are an update or a delete. if they're an update, I somehow need to get the next item, which I know will be a "item detail record" and get the values out of it as they correspond to this id. I'm stuck on trying to get the next sibling.... am I missing something, or is this just plain not possible? Note that I dont have an id element in the detail record so I cant go up to the parent and then select the child with the same id. any (more) help will be much appreciated. cheers dim ps - I want to have the output of the above look something like: 123 bar xyz 456 789 qwerty crazy which of course would be a more logical structure to start with (o: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From Dmitri.Colebatch@toyota.com.au Fri Aug 1 02:45:26 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h719itHA014434 for ; Fri, 1 Aug 2003 02:45:20 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Fri, 01 Aug 2003 18:59:49 +1000 Sensitivity: Subject: Re: [xquery-talk] group by queries - a more efficient approach To: Jason Hunter X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Fri, 1 Aug 2003 16:41:06 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 01/08/2003 19:08:23 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 09:45:26 -0000 Jason, I cant remember if I replied to this or not. Your change works fine, but if I want to in fact change the structure of the xml I would need the flowr expression yes? In any case, thanks a heap for your help. cheers dim Jason Hunter @x-query.com on 01/08/2003 01:58:53 PM Sent by: talk-bounces@x-query.com To: Dmitri.Colebatch@toyota.com.au cc: talk@x-query.com Subject: Re: [xquery-talk] group by queries - a more efficient approach > for $s in distinct-values($this/mydata/book/subject) > return > > { > for $book in $this/mydata/book[subject/text() = $s/text()] > return > > {$book/name} > {$book/subject} > > } > I suspect something like this would work. I haven't run it or anything. Basically you can remove the /text() node tests and can return the book nodes directly without needing a FLWOR. for $s in distinct-values($this/mydata/book/subject) return { $this/mydata/book[subject = $s] } -jh- _______________________________________________ talk@x-query.com http://www.x-query.com/mailman/listinfo/talk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From Mark_R_Maxey@raytheon.com Fri Aug 1 06:12:09 2003 Received: from lax-gate1.raytheon.com (lax-gate1.raytheon.com [199.46.200.230]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h71DC9HA014925 for ; Fri, 1 Aug 2003 06:12:09 -0700 Received: from ds02t00.directory.ray.com (ds02t00.directory.ray.com [147.25.154.117]) by lax-gate1.raytheon.com (8.12.9/8.12.9) with ESMTP id h71DBoZ7020734; Fri, 1 Aug 2003 06:11:51 -0700 (PDT) Received: from ds02t00.directory.ray.com (localhost [127.0.0.1]) by ds02t00.directory.ray.com (8.12.9/8.12.1) with ESMTP id h71DBoOY001010; Fri, 1 Aug 2003 13:11:50 GMT Received: Received: from mk2-mta01.mck.us.ray.com (mk2-mta01.mck.us.ray.com [138.126.190.145]) by ds02t00.directory.ray.com (8.12.9/8.12.9) with ESMTP id h71DBmGG000987 sender Mark_R_Maxey@raytheon.com; Fri, 1 Aug 2003 13:11:48 GMT Received: from raytheon.com ([162.36.244.78]) by mk2-mta01.mck.us.ray.com (Lotus Domino Release 5.0.12) with ESMTP id 2003080108114027:316611 ; Fri, 1 Aug 2003 08:11:40 -0500 Message-ID: <3F2A670C.1000902@raytheon.com> Date: Fri, 01 Aug 2003 08:11:40 -0500 From: Mark R Maxey Organization: Raytheon User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en,pdf MIME-Version: 1.0 To: Jason Hunter Subject: Re: [xquery-talk] function definitions References: <3F29E4A9.3060907@servlets.com> In-Reply-To: <3F29E4A9.3060907@servlets.com> Content-Type: multipart/alternative; boundary="------------080701080805050203050709" Cc: talk@x-query.com, Dmitri.Colebatch@toyota.com.au X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list Reply-To: Mark_R_Maxey@raytheon.com List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 13:12:10 -0000 This is a multi-part message in MIME format. --------------080701080805050203050709 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed If you're talking about BEA LD 1.1, I asked the same question and was told "LD 1.1 does not support User Defined Functions. This feature was omitted for performance reasons." BEA 8.1 which just came out yesterday only supports XQuery |http://www.w3.org/TR/2001/WD-xquery-20011220| XQuery Functions and Operators |http://www.w3.org/TR/2002/WD-xquery-operators-20020430| In looking at the LD 8.1 release notes and other docs, I don't see where they've added support for them yet. Jason Hunter wrote: > Are you sure the BEA implementation supports the May draft? The "as" > syntax like you're using is from May. You can see if the > round-half-to-even() or trace() functions are implemented. Those > being implemented would indicate it's May. > > -jh- > > Dmitri.Colebatch@toyota.com.au wrote: > >> hey all, >> >> another question.... hopefully not quite as trivial as the last. >> >> I'm trying to define my own function, and have the following in my >> header, >> however I am getting parse exceptions from the bea weblogic >> implementation. >> Can someone tell me if this is a problem with my code or their >> implementation... >> >> define function convertSAPDateTime($dateNode as node(), $timeNode as >> node()) >> as xs:dateTime >> { >> let $dateStr := data($dateNode) >> let $yyyy := xf:substring($dateStr, 1, 4) >> let $mm := xf:substring($dateStr, 5, 2) >> let $dd := xf:substring($dateStr,7, 2) >> >> let $timeStr := data($timeNode) >> let $HH := xf:substring($timeStr, 1, 2) >> let $mi := xf:substring($timeStr, 3, 2) >> let $ss := xf:substring($timeStr, 5, 2) >> >> return xf:dateTime(xf:concat($yyyy, '-', $mm, '-', $dd, 'T', $HH, >> ':', $mi, ':', $ss)) >> } >> >> the code inside the braces works fine when not defined as part of a >> function, but I am getting parse exceptions on the "as" in "$dateNode as >> node()". If I remove the "as node()" then it works fine, however I then >> have the wrong type for the data function... I assume could cast it, >> but as >> I understand it the above should work... >> >> fwiw I'm using http://www.w3.org/TR/xquery/#FunctionDefns as my >> reference. >> >> thanks again for your help. >> >> cheers >> dim >> >> >> >> >> >> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> DISCLAIMER >> * This email and any attachment may contain confidential information. >> If you are not the intended recipient you are not authorised to copy >> or disclose all or any part of it without the prior written consent >> of Toyota. >> * Opinions expressed in this email and any attachment are those of the >> sender and not necessarily the opinions of Toyota. >> * Please scan this email and any attachment for viruses. Toyota does >> not accept any responsibility for problems caused by viruses, whether >> it is Toyota's fault or not. >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> >> >> _______________________________________________ >> talk@x-query.com >> http://www.x-query.com/mailman/listinfo/talk >> > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk > -- Mark Maxey (972)205-5760 Mark_R_Maxey@Raytheon.com --------------080701080805050203050709 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii If you're talking about BEA LD 1.1, I asked the same question and was told "LD 1.1 does not support User Defined Functions. This feature was omitted for performance reasons."

BEA 8.1 which just came out yesterday only supports

XQuery 
http://www.w3.org/TR/2001/WD-xquery-20011220

XQuery Functions and Operators

http://www.w3.org/TR/2002/WD-xquery-operators-20020430


In looking at the LD 8.1 release notes and other docs, I don't see where they've added support for them yet.

Jason Hunter wrote:
Are you sure the BEA implementation supports the May draft?  The "as" syntax like you're using is from May.  You can see if the round-half-to-even() or trace() functions are implemented.  Those being implemented would indicate it's May.

-jh-

Dmitri.Colebatch@toyota.com.au wrote:

hey all,

another question.... hopefully not quite as trivial as the last.

I'm trying to define my own function, and have the following in my header,
however I am getting parse exceptions from the bea weblogic implementation.
Can someone tell me if this is a problem with my code or their
implementation...

define function convertSAPDateTime($dateNode as node(), $timeNode as
node())
      as xs:dateTime
{
      let $dateStr := data($dateNode)
      let $yyyy := xf:substring($dateStr, 1, 4)
      let $mm := xf:substring($dateStr, 5, 2)
      let $dd := xf:substring($dateStr,7, 2)

      let $timeStr := data($timeNode)
      let $HH := xf:substring($timeStr, 1, 2)
      let $mi := xf:substring($timeStr, 3, 2)
      let $ss := xf:substring($timeStr, 5, 2)

      return xf:dateTime(xf:concat($yyyy, '-', $mm, '-', $dd, 'T', $HH,
':', $mi, ':', $ss))
}

the code inside the braces works fine when not defined as part of a
function, but I am getting parse exceptions on the "as" in "$dateNode as
node()".  If I remove the "as node()" then it works fine, however I then
have the wrong type for the data function... I assume could cast it, but as
I understand it the above should work...

fwiw I'm using http://www.w3.org/TR/xquery/#FunctionDefns as my reference.

thanks again for your help.

cheers
dim






- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                               DISCLAIMER
* This email and any attachment may contain confidential information.
  If you are not the intended recipient you are not authorised to copy
  or disclose all or any part of it without the prior written consent
  of Toyota.
* Opinions expressed in this email and any attachment are those of the
  sender and not necessarily the opinions of Toyota.
* Please scan this email and any attachment for viruses.  Toyota does
  not accept any responsibility for problems caused by viruses, whether
  it is Toyota's fault or not.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


_______________________________________________
talk@x-query.com
http://www.x-query.com/mailman/listinfo/talk


_______________________________________________
talk@x-query.com
http://www.x-query.com/mailman/listinfo/talk 


-- 
Mark Maxey
(972)205-5760
Mark_R_Maxey@Raytheon.com
--------------080701080805050203050709-- From Mark_R_Maxey@raytheon.com Fri Aug 1 06:34:12 2003 Received: from lax-gate3.raytheon.com (lax-gate3.raytheon.com [199.46.200.232]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h71DYCHA014950 for ; Fri, 1 Aug 2003 06:34:12 -0700 Received: from ds02t00.directory.ray.com (ds02t00.directory.ray.com [147.25.154.117]) by lax-gate3.raytheon.com (8.12.9/8.12.9) with ESMTP id h71DY6JX009587; Fri, 1 Aug 2003 06:34:06 -0700 (PDT) Received: from ds02t00.directory.ray.com (localhost [127.0.0.1]) by ds02t00.directory.ray.com (8.12.9/8.12.1) with ESMTP id h71DY5OY018867; Fri, 1 Aug 2003 13:34:05 GMT Received: Received: from mk2-mta01.mck.us.ray.com (mk2-mta01.mck.us.ray.com [138.126.190.145]) by ds02t00.directory.ray.com (8.12.9/8.12.9) with ESMTP id h71DY4GG018846 sender Mark_R_Maxey@raytheon.com; Fri, 1 Aug 2003 13:34:04 GMT Received: from raytheon.com ([162.36.244.78]) by mk2-mta01.mck.us.ray.com (Lotus Domino Release 5.0.12) with ESMTP id 2003080108334982:318556 ; Fri, 1 Aug 2003 08:33:49 -0500 Message-ID: <3F2A6C3D.6060400@raytheon.com> Date: Fri, 01 Aug 2003 08:33:49 -0500 From: Mark R Maxey Organization: Raytheon User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en,pdf MIME-Version: 1.0 To: Dmitri.Colebatch@toyota.com.au Subject: Re: [xquery-talk] next node (sibling) References: In-Reply-To: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list Reply-To: Mark_R_Maxey@raytheon.com List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 13:34:12 -0000 XQuery doesn't support the following-sibling axis. However, there are work arounds as suggested by Michael Kay. Instead of following-sibling:x use ../child::x[. >> $current] If you're using BEA LD, you're hosed because it doesn't support the order comparison operators ">>" and "<<". Dmitri.Colebatch@toyota.com.au wrote: >hey again, > >Apologies for bombarding the list with questions, but you're all being very >helpful (o: I've also got past most of the stuff I had to do witht his >much quicker than I thought I would, thanks to you guys... > >I'm now working with a document with a structure like the following: > > > > hdr > update > 123 > > > detail > > bar > xyz > > > > hdr > delete > 456 > > > hdr > update > 789 > > > detail > > qwerty > crazy > > > > >as the names suggest, this is for updating data between two systems - I >need to receive the message from system A and send it to system B in the >appropriate format. The structure above is how I receive it from system A. > >Now, its not immediately obvious how the above is intended to work, but >essentially each "item header record" [item/item-type/text() = 'hdr' ] will >indicate an update (or new record), or a delete. In the case of an update, >I know that the next item record will be an "item detail record" >[item/item-type/text() = 'detail'] which I use to get the detail of the >changes. > >The problem of course is that the structure requires a stateful approach to >the conversion. What I've tried to do is select all the item header >records, and look at whether they are an update or a delete. if they're an >update, I somehow need to get the next item, which I know will be a "item >detail record" and get the values out of it as they correspond to this id. > >I'm stuck on trying to get the next sibling.... am I missing something, or >is this just plain not possible? Note that I dont have an id element in >the detail record so I cant go up to the parent and then select the child >with the same id. > >any (more) help will be much appreciated. > >cheers >dim > >ps - I want to have the output of the above look something like: > > > > 123 > bar > xyz > > > 456 > > > 789 > qwerty > crazy > > > >which of course would be a more logical structure to start with (o: >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > DISCLAIMER >* This email and any attachment may contain confidential information. > If you are not the intended recipient you are not authorised to copy > or disclose all or any part of it without the prior written consent > of Toyota. >* Opinions expressed in this email and any attachment are those of the > sender and not necessarily the opinions of Toyota. >* Please scan this email and any attachment for viruses. Toyota does > not accept any responsibility for problems caused by viruses, whether > it is Toyota's fault or not. >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > >_______________________________________________ >talk@x-query.com >http://www.x-query.com/mailman/listinfo/talk > > > -- Mark Maxey (972)205-5760 Mark_R_Maxey@Raytheon.com From jhunter@servlets.com Fri Aug 1 11:11:58 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h71IBwHA015220 for ; Fri, 1 Aug 2003 11:11:58 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h71ID7oO016265; Fri, 1 Aug 2003 11:13:09 -0700 (PDT) Message-ID: <3F2AACA8.6000608@servlets.com> Date: Fri, 01 Aug 2003 11:08:40 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitri.Colebatch@toyota.com.au Subject: Re: [xquery-talk] group by queries - a more efficient approach References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 18:11:58 -0000 If you want a $book variable bound then yes you need a FLWOR. But you may not really need a $book variable bound as my code rewrite shows. Most people write FLWORs because they think "for loop" from procedural programming but they aren't always necessary and at least some engines perform faster without them. -jh- Dmitri.Colebatch@toyota.com.au wrote: > Jason, > > Thanks for the tip.... problem is that my contrieved example didn't really > show what I need to do. I want to modify the structure more than my > example shows. > > Your suggestion does work, but I cant see a way to step from that to having > access to a $book variable - am I right that I do need the for loop to get > access to that? > > thanks > dim > > > > > > Jason Hunter @x-query.com on 01/08/2003 01:58:53 PM > > Sent by: talk-bounces@x-query.com > > > To: Dmitri.Colebatch@toyota.com.au > cc: talk@x-query.com > Subject: Re: [xquery-talk] group by queries - a more efficient approach > > >>for $s in distinct-values($this/mydata/book/subject) >>return >> >> { >> for $book in $this/mydata/book[subject/text() = $s/text()] >> return >> >> {$book/name} >> {$book/subject} >> >> } >> > > > I suspect something like this would work. I haven't run it or anything. > Basically you can remove the /text() node tests and can return the > book nodes directly without needing a FLWOR. > > for $s in distinct-values($this/mydata/book/subject) > return > > { > $this/mydata/book[subject = $s] > } > > > -jh- > > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk > > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > DISCLAIMER > * This email and any attachment may contain confidential information. > If you are not the intended recipient you are not authorised to copy > or disclose all or any part of it without the prior written consent > of Toyota. > * Opinions expressed in this email and any attachment are those of the > sender and not necessarily the opinions of Toyota. > * Please scan this email and any attachment for viruses. Toyota does > not accept any responsibility for problems caused by viruses, whether > it is Toyota's fault or not. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > From jhunter@servlets.com Fri Aug 1 11:15:49 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h71IFnHA015242 for ; Fri, 1 Aug 2003 11:15:49 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h71IH4oO016300; Fri, 1 Aug 2003 11:17:04 -0700 (PDT) Message-ID: <3F2AAD95.5010508@servlets.com> Date: Fri, 01 Aug 2003 11:12:37 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitri.Colebatch@toyota.com.au Subject: Re: [xquery-talk] next node (sibling) References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 18:15:49 -0000 I just skimmed your post, but it sounds like you're wanting to get the next sibling. You should read my "X is for XQuery" article. It's the article listed on the front page of x-query.com. You seem to have a lot of questions, and the article will answer many of them including how to get a next sibling. That question was also answered on this list recently. -jh- Dmitri.Colebatch@toyota.com.au wrote: > hey again, > > Apologies for bombarding the list with questions, but you're all being very > helpful (o: I've also got past most of the stuff I had to do witht his > much quicker than I thought I would, thanks to you guys... > > I'm now working with a document with a structure like the following: > > > > hdr > update > 123 > > > detail > > bar > xyz > > > > hdr > delete > 456 > > > hdr > update > 789 > > > detail > > qwerty > crazy > > > > > as the names suggest, this is for updating data between two systems - I > need to receive the message from system A and send it to system B in the > appropriate format. The structure above is how I receive it from system A. > > Now, its not immediately obvious how the above is intended to work, but > essentially each "item header record" [item/item-type/text() = 'hdr' ] will > indicate an update (or new record), or a delete. In the case of an update, > I know that the next item record will be an "item detail record" > [item/item-type/text() = 'detail'] which I use to get the detail of the > changes. > > The problem of course is that the structure requires a stateful approach to > the conversion. What I've tried to do is select all the item header > records, and look at whether they are an update or a delete. if they're an > update, I somehow need to get the next item, which I know will be a "item > detail record" and get the values out of it as they correspond to this id. > > I'm stuck on trying to get the next sibling.... am I missing something, or > is this just plain not possible? Note that I dont have an id element in > the detail record so I cant go up to the parent and then select the child > with the same id. > > any (more) help will be much appreciated. > > cheers > dim > > ps - I want to have the output of the above look something like: > > > > 123 > bar > xyz > > > 456 > > > 789 > qwerty > crazy > > > > which of course would be a more logical structure to start with (o: > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > DISCLAIMER > * This email and any attachment may contain confidential information. > If you are not the intended recipient you are not authorised to copy > or disclose all or any part of it without the prior written consent > of Toyota. > * Opinions expressed in this email and any attachment are those of the > sender and not necessarily the opinions of Toyota. > * Please scan this email and any attachment for viruses. Toyota does > not accept any responsibility for problems caused by viruses, whether > it is Toyota's fault or not. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk > From mhk@mhk.me.uk Sun Aug 3 15:04:50 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h73M4nHA017916 for ; Sun, 3 Aug 2003 15:04:50 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (DomainNamesGB Mailserver v4.6.72) with ESMTP id FJMQLY; Sun, 03 Aug 2003 23:07:27 +0100 From: "Michael Kay" To: , Subject: RE: [xquery-talk] next node (sibling) Date: Sun, 3 Aug 2003 23:06:11 +0100 Message-ID: <003b01c35a0b$73324400$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Aug 2003 22:04:51 -0000 > > I'm stuck on trying to get the next sibling.... am I missing > something, or is this just plain not possible? Although XQuery doesn't require support for the following-sibling axis of XPath, you can simulate it by replacing $x/following-sibling::*[1] with $x/../*[.>>$x][1] Michael Kay From Dmitri.Colebatch@toyota.com.au Sun Aug 3 21:30:13 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h744TgHA018248 for ; Sun, 3 Aug 2003 21:30:04 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.3.11) id ; Mon, 04 Aug 2003 14:24:17 +1000 Sensitivity: Subject: evaluating BEA's implementation, was: [xquery-talk] next node (sibling) To: talk@x-query.com X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Mon, 4 Aug 2003 14:31:11 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 04/08/2003 14:32:59 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 04:30:13 -0000 Jason, Thanks again for your help. My apologies for not reading your article - I've now read it, and realised how much help if would have been. I have one query regarding the maturity of BEA's implementation. In another email you wrote: > Sounds like BEA's using a 18 month old draft. In my mind, that means > the implementation is pre-alpha and shouldn't be trusted to do anything > reasonable. Given that there are no conformance tests, how should I best address the issue of evaluating BEA's (or anyone else's) implementation? thanks, dim Jason Hunter on 02/08/2003 04:12:37 AM To: Dmitri.Colebatch@toyota.com.au cc: talk@x-query.com Subject: Re: [xquery-talk] next node (sibling) I just skimmed your post, but it sounds like you're wanting to get the next sibling. You should read my "X is for XQuery" article. It's the article listed on the front page of x-query.com. You seem to have a lot of questions, and the article will answer many of them including how to get a next sibling. That question was also answered on this list recently. -jh- Dmitri.Colebatch@toyota.com.au wrote: > hey again, > > Apologies for bombarding the list with questions, but you're all being very > helpful (o: I've also got past most of the stuff I had to do witht his > much quicker than I thought I would, thanks to you guys... > > I'm now working with a document with a structure like the following: > > > > hdr > update > 123 > > > detail > > bar > xyz > > > > hdr > delete > 456 > > > hdr > update > 789 > > > detail > > qwerty > crazy > > > > > as the names suggest, this is for updating data between two systems - I > need to receive the message from system A and send it to system B in the > appropriate format. The structure above is how I receive it from system A. > > Now, its not immediately obvious how the above is intended to work, but > essentially each "item header record" [item/item-type/text() = 'hdr' ] will > indicate an update (or new record), or a delete. In the case of an update, > I know that the next item record will be an "item detail record" > [item/item-type/text() = 'detail'] which I use to get the detail of the > changes. > > The problem of course is that the structure requires a stateful approach to > the conversion. What I've tried to do is select all the item header > records, and look at whether they are an update or a delete. if they're an > update, I somehow need to get the next item, which I know will be a "item > detail record" and get the values out of it as they correspond to this id. > > I'm stuck on trying to get the next sibling.... am I missing something, or > is this just plain not possible? Note that I dont have an id element in > the detail record so I cant go up to the parent and then select the child > with the same id. > > any (more) help will be much appreciated. > > cheers > dim > > ps - I want to have the output of the above look something like: > > > > 123 > bar > xyz > > > 456 > > > 789 > qwerty > crazy > > > > which of course would be a more logical structure to start with (o: > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > DISCLAIMER > * This email and any attachment may contain confidential information. > If you are not the intended recipient you are not authorised to copy > or disclose all or any part of it without the prior written consent > of Toyota. > * Opinions expressed in this email and any attachment are those of the > sender and not necessarily the opinions of Toyota. > * Please scan this email and any attachment for viruses. Toyota does > not accept any responsibility for problems caused by viruses, whether > it is Toyota's fault or not. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From mcarey@bea.com Tue Aug 5 22:52:18 2003 Received: from usmailrelay.bea.com (sj-ez-63-96-163-59.bea.com [63.96.163.59] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h765qIHA022120 for ; Tue, 5 Aug 2003 22:52:18 -0700 Received: from santa-clara.bea.com (santa-clara [206.189.39.47]) by usmailrelay.bea.com (Switch-2.2.5/Switch-2.2.5) with ESMTP id h765qO500762 for ; Tue, 5 Aug 2003 22:52:24 -0700 (PDT) Received: from MCAREY (sj-vpn-192-168-11-35.bea.com [192.168.11.35]) by santa-clara.bea.com (8.10.2+Sun/8.10.2) with SMTP id h765qNt27683 for ; Tue, 5 Aug 2003 22:52:23 -0700 (PDT) From: "Michael Carey" To: Date: Tue, 5 Aug 2003 22:50:31 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Subject: [xquery-talk] XQuery & BEA X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2003 05:52:19 -0000 XQuery-ers, I'm writing in response to recent discussion about BEA products and their support for XQuery. At BEA, I've been the manager of the group that created the XQuery-based data transformation engine for the newly launched BEA WebLogic Integration 8.1 product (which is a part of the BEA Platform 8.1, of course) - and I'm now also the architect for BEA's Liquid Data for WebLogic team, which is the team responsible for BEA's XQuery-based data integration product offering. (These two products were originally developed by different teams at different times based on very different use cases and requirements, by the way. One uses XQuery as a declarative language for transforming business messages as they pass through an application integration/orchestration product. The other uses XQuery as a view definition language and query language for making an enterprise's distributed / disparate data look like a virtual XML repository.) The good news is that BEA is, to the best of my knowledge, the first of the "big four" software vendors to ship generally available products based on XQuery. The bad news, however, is that XQuery is not yet a standard - it changes every few months. To ship a product, one therefore must pick a snapshot of the language, build it, stabilize it, QA it, etc. Someone commented that our being on an older version of the XQuery spec must mean that our XQuery engine is "pre-alpha" and not trustworthy. Not so - in WLI, for example, we tracked all XQuery spec changes up to the version released 11-12 months ago - then we decided to stabilize on that version of the language for our alpha, beta, and GA - and to build out all the facilities around it (transformation editor, XQuery source editor), to do QA on it, and so on. We plan to upgrade to XQuery 1.0 as soon after it's an official spec as possible. Right now, from what I'm hearing, it's likely to become an official spec next spring, so if it stays on track, we should be able to upgrade to XQuery 1.0 in the BEA Platform 9.0 timeframe. Meanwhile, BEA's Liquid Data product, which shipped earlier (late 2002), used a slightly older version of the XQuery specification. We expect to upgrade Liquid Data's XQuery dialect in the same timeframe - both products will then speak a common dialect, XQuery 1.0, with the same functions and operators, etc., at that point. Meanwhile, from our online documentation for these products, here's the scoop on the accents with which our currently shipping products speak the language XQuery: WebLogic Integration (WLI) 8.1 - XQuery - August 2002: http://www.w3.org/TR/2002/WD-xquery-20020816/ XQuery Functions and Operators - August 2002: http://www.w3.org/TR/2002/WD-xquery-operators-20020816/ Liquid Data for WebLogic 8.1 (and earlier) - XQuery - December 2001: http://www.w3.org/TR/2001/WD-xquery-20011220 XQuery Functions and Operators - April 2002: http://www.w3.org/TR/2002/WD-xquery-operators-20020430 I hope this information will be helpful to those of you who are working with these products. (A suggestion for future discussions would be for folks to indicate which product they're using - WLI and/or Liquid Data - since they do have slightly different XQuery dialects at the moment.) Cheers, Mike Carey From mhk@mhk.me.uk Wed Aug 6 00:08:36 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7678ZHA022183 for ; Wed, 6 Aug 2003 00:08:36 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (DomainNamesGB Mailserver v4.6.72) with ESMTP id FJMQLY; Wed, 06 Aug 2003 08:11:17 +0100 From: "Michael Kay" To: "'Michael Carey'" , Subject: RE: [xquery-talk] XQuery & BEA Date: Wed, 6 Aug 2003 08:10:01 +0100 Message-ID: <000101c35be9$c124ae20$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2003 07:08:36 -0000 > The bad news, > however, is that XQuery is not yet a standard - it changes > every few months. To ship a product, one therefore must pick > a snapshot of the language, build it, stabilize it, QA it, > etc. Someone commented that our being on an older version of > the XQuery spec must mean that our XQuery engine is > "pre-alpha" and not trustworthy. Not so - in WLI, for > example, we tracked all XQuery spec changes up to the version > released 11-12 months ago - then we decided to stabilize on > that version of the language for our alpha, beta, and GA - > and to build out all the facilities around it (transformation > editor, XQuery source editor), to do QA on it, and so on. We > plan to upgrade to XQuery 1.0 as soon after it's an official > spec as possible. Let me add that we can say exactly the same thing about the support for XQuery in Software AG's Tamino 4.1. It is possible to release an industrial-strength product based on specifications that are not yet finalized, but it is not possible to track every revision to those specifications, and still deliver an acceptable level of stability to users. Tamino 4.1 came out in January 2003, based on the August 2002 specifications, and although we may add some features from later working drafts in subsequent versions, it is not our intent to track every single change in the working drafts: the primary goal is to deliver a conformant and high-quality XQuery 1.0 implementation as soon as possible after a Recommendation is signed off. This is the opposite of my strategy for Saxon, where I do try to track the changes to specifications as closely as I can, and I specifically warn users that they are on the bleeding edge and should expect a rough ride. Michael Kay Software AG From Sullivan.Sean@menlolog.com Fri Aug 15 10:22:58 2003 Received: from ljcqs053.cnf.com (mailhost2.cnf.com [63.230.177.24]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7FHMvHA001664 for ; Fri, 15 Aug 2003 10:22:58 -0700 Received: from cnfqs039.cnf.com (localhost [127.0.0.1]) by ljcqs053.cnf.com (Postfix) with ESMTP id 053FDAF9 for ; Fri, 15 Aug 2003 10:21:01 -0700 (PDT) Received: by cnfqs039.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Fri, 15 Aug 2003 10:21:00 -0700 Message-ID: <462D5240F6F9154AB0F9B345A5F03E3E3A19DF@cnfqe029.cnf.prod.cnf.com> From: "Sullivan, Sean C - MWT" To: "'talk@x-query.com'" Date: Fri, 15 Aug 2003 10:20:56 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] XQuery webcast, IBM, September 3rd X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2003 17:22:58 -0000 fyi http://webevents.broadcast.com/ibm/insightexchange/technology.asp XQuery: A Query Language for XML Wednesday, September 03, 2003 11:00 a.m. - 12:30 p.m. Eastern, US (New York) Dr. Don Chamberlin, Almaden Research Center, IBM Dr. Don Chamberlin is well-known as one of the primary designers of the SQL database language. Dr. Chamberlin works at IBM's Almaden Research Center, where he specializes in database languages, database systems, and document processing. He was named an ACM Fellow in 1994, and was elected to the National Academy of Engineering in 1997, the top honor in the engineering profession. Currently, he represents IBM in the W3C XML Query Working Group and is an editor of several working drafts on the XQuery language. From mike@clarkware.com Mon Aug 18 19:36:50 2003 Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7J2aoHA005878 for ; Mon, 18 Aug 2003 19:36:50 -0700 Received: from clarkware.com (12-254-54-55.client.attbi.com[12.254.54.55](untrusted sender)) by comcast.net (rwcrmhc12) with SMTP id <200308190236490140069m50e> (Authid: clarkware); Tue, 19 Aug 2003 02:36:49 +0000 Message-ID: <3F418CF3.1050204@clarkware.com> Date: Mon, 18 Aug 2003 20:35:31 -0600 From: Mike Clark User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@x-query.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xquery-talk] Article: "Five Practical XQuery Applications" X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 02:36:50 -0000 FYI. I just ran across this article, published in May: http://www.devx.com/xml/Article/15618 Realizing that the spec is still in working draft, I'd be interested to hear of other real-world problems that folks are tackling, in whole or in part, with XQuery. Mike From mhk@mhk.me.uk Tue Aug 19 00:58:52 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7J7wpHA006213 for ; Tue, 19 Aug 2003 00:58:51 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (DomainNamesGB Mailserver v4.6.72) with ESMTP id FJMQLY; Tue, 19 Aug 2003 09:01:36 +0100 From: "Michael Kay" To: "'Mike Clark'" , Subject: RE: [xquery-talk] Article: "Five Practical XQuery Applications" Date: Tue, 19 Aug 2003 09:00:22 +0100 Message-ID: <002801c36627$f1246dc0$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <3F418CF3.1050204@clarkware.com> Importance: Normal Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 07:58:52 -0000 Actually, my reading of the article is that the examples are entirely hypothetical, I don't read them as case studies of things that people are doing today. Certainly it would be pretty crazy using XQuery for these applications today, given that they can all be done very easily with XSLT, which might be a bit more long-winded but is at least a stable specification with many robust implementations. What articles like this do show is that there seems to be considerable interest in using XQuery for "transformations", not only for database queries. Once both specs are stable and have mature implementations, I think there's going to be a lot of debate about which language to use for which purposes. Michael Kay > -----Original Message----- > From: talk-bounces@x-query.com > [mailto:talk-bounces@x-query.com] On Behalf Of Mike Clark > Sent: 19 August 2003 03:36 > To: talk@x-query.com > Subject: [xquery-talk] Article: "Five Practical XQuery Applications" > > > FYI. I just ran across this article, published in May: > > http://www.devx.com/xml/Article/15618 > > Realizing that the spec is still in working draft, I'd be > interested to > hear of other real-world problems that folks are tackling, in > whole or > in part, with XQuery. > > Mike > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk > From Mark_R_Maxey@raytheon.com Tue Aug 19 05:54:08 2003 Received: from dfw-gate4.raytheon.com (dfw-gate4.raytheon.com [199.46.199.233]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JCs7HA006522 for ; Tue, 19 Aug 2003 05:54:08 -0700 Received: from ds02c00.directory.ray.com (ds02c00.directory.ray.com [147.25.138.118]) by dfw-gate4.raytheon.com (8.12.9/8.12.9) with ESMTP id h7JCrnE2027892; Tue, 19 Aug 2003 07:53:59 -0500 (CDT) Received: from ds02c00.directory.ray.com (localhost [127.0.0.1]) by ds02c00.directory.ray.com (8.12.9/8.12.1) with ESMTP id h7JCri16019535; Tue, 19 Aug 2003 12:53:44 GMT Received: Received: from mk2-mta01.mck.us.ray.com (mk2-mta01.mck.us.ray.com [138.126.190.145]) by ds02c00.directory.ray.com (8.12.9/8.12.9) with ESMTP id h7JCrgLs019526 sender Mark_R_Maxey@raytheon.com; Tue, 19 Aug 2003 12:53:43 GMT Received: from raytheon.com ([162.36.244.78]) by mk2-mta01.mck.us.ray.com (Lotus Domino Release 5.0.12) with ESMTP id 2003081907534168:501550 ; Tue, 19 Aug 2003 07:53:41 -0500 Message-ID: <3F421DDE.1040009@raytheon.com> Date: Tue, 19 Aug 2003 07:53:50 -0500 From: Mark R Maxey Organization: Raytheon User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en,pdf MIME-Version: 1.0 To: Michael Kay Subject: Re: [xquery-talk] Article: "Five Practical XQuery Applications" References: <002801c36627$f1246dc0$6401a8c0@pcukmka> In-Reply-To: <002801c36627$f1246dc0$6401a8c0@pcukmka> Content-Type: multipart/alternative; boundary="------------060106000307030604020206" Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list Reply-To: Mark_R_Maxey@raytheon.com List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 12:54:08 -0000 This is a multi-part message in MIME format. --------------060106000307030604020206 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed I'll throw out the use cases I'm looking at - using web services against heterogeneous data sources. We have a number of data sources - RDBMSs, Excel docs, and proprietary formatted files - which we want to allow to be exposed via web services, i.e., provide services which queries the data sources and returns large XML docs. Sometimes, these queries are for reporting purposes. Sometimes, its to gather meta-data information for cataloging. We hope that updates are added to XQuery so these same clients can someday submit XML via some service we provide and have it placed in the appropriate data source. Michael Kay wrote: >Actually, my reading of the article is that the examples are entirely >hypothetical, I don't read them as case studies of things that people >are doing today. > >Certainly it would be pretty crazy using XQuery for these applications >today, given that they can all be done very easily with XSLT, which >might be a bit more long-winded but is at least a stable specification >with many robust implementations. > >What articles like this do show is that there seems to be considerable >interest in using XQuery for "transformations", not only for database >queries. Once both specs are stable and have mature implementations, I >think there's going to be a lot of debate about which language to use >for which purposes. > >Michael Kay > > > > >>-----Original Message----- >>From: talk-bounces@x-query.com >>[mailto:talk-bounces@x-query.com] On Behalf Of Mike Clark >>Sent: 19 August 2003 03:36 >>To: talk@x-query.com >>Subject: [xquery-talk] Article: "Five Practical XQuery Applications" >> >> >>FYI. I just ran across this article, published in May: >> >> http://www.devx.com/xml/Article/15618 >> >>Realizing that the spec is still in working draft, I'd be >>interested to >>hear of other real-world problems that folks are tackling, in >>whole or >>in part, with XQuery. >> >>Mike >> >>_______________________________________________ >>talk@x-query.com >>http://www.x-query.com/mailman/listinfo/talk >> >> >> > >_______________________________________________ >talk@x-query.com >http://www.x-query.com/mailman/listinfo/talk > > > -- Mark Maxey (972)205-5760 Mark_R_Maxey@Raytheon.com --------------060106000307030604020206 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii I'll throw out the use cases I'm looking at - using web services against heterogeneous data sources.  We have a number of data sources - RDBMSs, Excel docs, and proprietary formatted files - which we want to allow to be exposed via web services, i.e., provide services which queries the data sources and returns large XML docs.  Sometimes, these queries are for reporting purposes.  Sometimes, its to gather meta-data information for cataloging.  We hope that updates are added to XQuery so these same clients can someday submit XML via some service we provide and have it placed in the appropriate data source.

Michael Kay wrote:
Actually, my reading of the article is that the examples are entirely
hypothetical, I don't read them as case studies of things that people
are doing today.

Certainly it would be pretty crazy using XQuery for these applications
today, given that they can all be done very easily with XSLT, which
might be a bit more long-winded but is at least a stable specification
with many robust implementations.

What articles like this do show is that there seems to be considerable
interest in using XQuery for "transformations", not only for database
queries. Once both specs are stable and have mature implementations, I
think there's going to be a lot of debate about which language to use
for which purposes.

Michael Kay


  
-----Original Message-----
From: talk-bounces@x-query.com 
[mailto:talk-bounces@x-query.com] On Behalf Of Mike Clark
Sent: 19 August 2003 03:36
To: talk@x-query.com
Subject: [xquery-talk] Article: "Five Practical XQuery Applications"


FYI.  I just ran across this article, published in May:

     http://www.devx.com/xml/Article/15618

Realizing that the spec is still in working draft, I'd be 
interested to 
hear of other real-world problems that folks are tackling, in 
whole or 
in part, with XQuery.

Mike

_______________________________________________
talk@x-query.com
http://www.x-query.com/mailman/listinfo/talk

    

_______________________________________________
talk@x-query.com
http://www.x-query.com/mailman/listinfo/talk

  

-- 
Mark Maxey
(972)205-5760
Mark_R_Maxey@Raytheon.com
--------------060106000307030604020206-- From mike@clarkware.com Tue Aug 19 08:18:16 2003 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JFIGHA006646 for ; Tue, 19 Aug 2003 08:18:16 -0700 Received: from clarkware.com (12-254-54-55.client.attbi.com[12.254.54.55](untrusted sender)) by comcast.net (rwcrmhc13) with SMTP id <2003081915181201500asc05e> (Authid: clarkware); Tue, 19 Aug 2003 15:18:12 +0000 Message-ID: <3F423F67.3020300@clarkware.com> Date: Tue, 19 Aug 2003 09:16:55 -0600 From: Mike Clark User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@x-query.com Subject: Re: [xquery-talk] Article: "Five Practical XQuery Applications" References: <002801c36627$f1246dc0$6401a8c0@pcukmka> In-Reply-To: <002801c36627$f1246dc0$6401a8c0@pcukmka> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 15:18:17 -0000 Michael Kay wrote: > Actually, my reading of the article is that the examples are entirely > hypothetical, I don't read them as case studies of things that people > are doing today. > Yes, that was my reading of the article, as well. I should have said: Realizing that the spec is still in working draft, I'd be interested to hear of _any_ real-world problems that folks are tackling, in whole or in part, with XQuery. Mike From mike@clarkware.com Tue Aug 19 08:30:49 2003 Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JFUnHA006662 for ; Tue, 19 Aug 2003 08:30:49 -0700 Received: from clarkware.com (12-254-54-55.client.attbi.com[12.254.54.55](untrusted sender)) by comcast.net (rwcrmhc11) with SMTP id <2003081915304401300hvla1e> (Authid: clarkware); Tue, 19 Aug 2003 15:30:44 +0000 Message-ID: <3F424258.6040800@clarkware.com> Date: Tue, 19 Aug 2003 09:29:28 -0600 From: Mike Clark User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark_R_Maxey@raytheon.com, talk@x-query.com Subject: Re: [xquery-talk] Article: "Five Practical XQuery Applications" References: <002801c36627$f1246dc0$6401a8c0@pcukmka> <3F421DDE.1040009@raytheon.com> In-Reply-To: <3F421DDE.1040009@raytheon.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 15:30:49 -0000 Mark R Maxey wrote: > I'll throw out the use cases I'm looking at - using web services against > heterogeneous data sources. We have a number of data sources - RDBMSs, > Excel docs, and proprietary formatted files - which we want to allow to > be exposed via web services, i.e., provide services which queries the > data sources and returns large XML docs. Sometimes, these queries are > for reporting purposes. Indeed, the ability to query multiple, disparate sources in one pass seems to be a distinct advantage to using XQuery over XSLT. Mike From jeni@jenitennison.com Tue Aug 19 08:47:37 2003 Received: from yankee.rb.xcalibre.co.uk (yankee.rb.xcalibre.co.uk [217.8.240.35]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JFlaHA006708 for ; Tue, 19 Aug 2003 08:47:37 -0700 Envelope-to: talk@x-query.com Received: from [217.8.240.35] (helo=malkuth) by yankee.rb.xcalibre.co.uk with esmtp (Exim 3.33 #3) id 19p8wh-0000h5-00; Tue, 19 Aug 2003 16:02:55 +0000 Date: Tue, 19 Aug 2003 16:47:41 +0100 From: Jeni Tennison X-Mailer: The Bat! (v1.62 Christmas Edition) Business Organization: Jeni Tennison Consulting Ltd X-Priority: 3 (Normal) Message-ID: <164106781109.20030819164741@jenitennison.com> To: Mike Clark Subject: Re: [xquery-talk] Article: "Five Practical XQuery Applications" In-Reply-To: <3F424258.6040800@clarkware.com> References: <002801c36627$f1246dc0$6401a8c0@pcukmka> <3F421DDE.1040009@raytheon.com> <3F424258.6040800@clarkware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: talk@x-query.com, Mark_R_Maxey@raytheon.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list Reply-To: Jeni Tennison List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 15:47:37 -0000 Hi Mike, >> I'll throw out the use cases I'm looking at - using web services >> against heterogeneous data sources. We have a number of data >> sources - RDBMSs, Excel docs, and proprietary formatted files - >> which we want to allow to be exposed via web services, i.e., >> provide services which queries the data sources and returns large >> XML docs. Sometimes, these queries are for reporting purposes. > > Indeed, the ability to query multiple, disparate sources in one pass > seems to be a distinct advantage to using XQuery over XSLT. I'm not sure what feature of XQuery you're referring to? XSLT 2.0 processors can have multiple nodes supplied as the input sequence (accessible via the input() function). XSLT 2.0 supports the collection() function, and XSLT 1.0 has always had the document() function for accessing multiple sources of information within a single transformation. XSLT 2.0 also introduces the unparsed-text() function for accessing information that isn't available in an XML format without writing a SAX filter or something equivalent. XQuery doesn't support this function as far as I know. So I don't think there's any real difference at this level? Cheers, Jeni --- Jeni Tennison http://www.jenitennison.com/ From mike@clarkware.com Tue Aug 19 09:05:41 2003 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JG5fHA006725 for ; Tue, 19 Aug 2003 09:05:41 -0700 Received: from clarkware.com (12-254-54-55.client.attbi.com[12.254.54.55](untrusted sender)) by comcast.net (rwcrmhc13) with SMTP id <2003081916053701500fatsfe> (Authid: clarkware); Tue, 19 Aug 2003 16:05:37 +0000 Message-ID: <3F424A85.2000201@clarkware.com> Date: Tue, 19 Aug 2003 10:04:21 -0600 From: Mike Clark User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeni Tennison Subject: Re: [xquery-talk] Article: "Five Practical XQuery Applications" References: <002801c36627$f1246dc0$6401a8c0@pcukmka> <3F421DDE.1040009@raytheon.com> <3F424258.6040800@clarkware.com> <164106781109.20030819164741@jenitennison.com> In-Reply-To: <164106781109.20030819164741@jenitennison.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 16:05:41 -0000 Jeni Tennison wrote: > >>Indeed, the ability to query multiple, disparate sources in one pass >>seems to be a distinct advantage to using XQuery over XSLT. > > I'm not sure what feature of XQuery you're referring to? XSLT 2.0 > processors can have multiple nodes supplied as the input sequence > (accessible via the input() function). XSLT 2.0 supports the > collection() function, and XSLT 1.0 has always had the document() > function for accessing multiple sources of information within a single > transformation. > > XSLT 2.0 also introduces the unparsed-text() function for accessing > information that isn't available in an XML format without writing a > SAX filter or something equivalent. XQuery doesn't support this > function as far as I know. > > So I don't think there's any real difference at this level? > Thanks for that clarification, Jeni! Mike From mike@clarkware.com Tue Aug 19 09:19:00 2003 Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JGJ0HA006748 for ; Tue, 19 Aug 2003 09:19:00 -0700 Received: from clarkware.com (12-254-54-55.client.attbi.com[12.254.54.55](untrusted sender)) by comcast.net (rwcrmhc12) with SMTP id <2003081916185601400641rde> (Authid: clarkware); Tue, 19 Aug 2003 16:18:56 +0000 Message-ID: <3F424DA4.4040101@clarkware.com> Date: Tue, 19 Aug 2003 10:17:40 -0600 From: Mike Clark User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeni Tennison References: <002801c36627$f1246dc0$6401a8c0@pcukmka> <3F421DDE.1040009@raytheon.com> <3F424258.6040800@clarkware.com> <164106781109.20030819164741@jenitennison.com> In-Reply-To: <164106781109.20030819164741@jenitennison.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com Subject: [xquery-talk] Comparing XQuery to XSLT X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 16:19:00 -0000 So for those with XSLT experience, I'd be interested to hear your opinions on what XQuery brings to the table. As the spec matures it's likely to be a reoccurring and important conversation, as Michael pointed out. And since I've already shown how little I know about their differences (thanks, Jeni!), I thought I'd go ahead and start tugging on the thread. It's not my intent to provoke a flame war. I'm here to learn from the collective wisdom of the group. Mike From per@bothner.com Tue Aug 19 09:44:54 2003 Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JGirHA006772 for ; Tue, 19 Aug 2003 09:44:53 -0700 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.12.9/8.12.9) with ESMTP id h7JGiXfR016890 for ; Tue, 19 Aug 2003 09:44:33 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Tue, 19 Aug 2003 09:44:29 -0700 Received: from bothner.com (vpn-scv-x1-14.apple.com [17.219.193.14]) by scv3.apple.com (8.12.9/8.12.9) with ESMTP id h7JGiUeq026371; Tue, 19 Aug 2003 09:44:35 -0700 (PDT) Message-ID: <3F4254AD.9000502@bothner.com> Date: Tue, 19 Aug 2003 09:47:41 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Clark Subject: Re: [xquery-talk] Article: "Five Practical XQuery Applications" References: <3F418CF3.1050204@clarkware.com> In-Reply-To: <3F418CF3.1050204@clarkware.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 16:44:54 -0000 My "digital photo albums" at http://pics.bothner.com/ are generated using XQuery. A sample page that illustrates most of the features is http://pics.bothner.com/2003/NelsonCoveJune/ The XML.com article http://www.xml.com/pub/a/2002/12/23/xquery.html explains how the XQuery code works. The scripts (with documentation on how to use them) are at http://www.gnu.org/software/qexo/qalbum/ An earlier version of the photo album used XSLT, but when I re-wrote it in XQuery it became easier to add extra features. -- --Per Bothner per@bothner.com http://per.bothner.com/ From schochler3@yahoo.com Tue Aug 19 09:55:36 2003 Received: from web40101.mail.yahoo.com (web40101.mail.yahoo.com [66.218.78.35]) by jhunter.x-query.com (8.12.8/8.12.4) with SMTP id h7JGtaHA006813 for ; Tue, 19 Aug 2003 09:55:36 -0700 Message-ID: <20030819165532.29140.qmail@web40101.mail.yahoo.com> Received: from [198.185.18.207] by web40101.mail.yahoo.com via HTTP; Tue, 19 Aug 2003 09:55:32 PDT Date: Tue, 19 Aug 2003 09:55:32 -0700 (PDT) From: rick schochler Subject: Re: [xquery-talk] Comparing XQuery to XSLT To: Mike Clark , Jeni Tennison In-Reply-To: <3F424DA4.4040101@clarkware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 16:55:37 -0000 I had the same question when I first started delving in to XQuery, so I took the use cases presented on the W3C ( http://www.w3.org/TR/xquery-use-cases/ )and attempted to perform the same operation using xslt. I didn't get through all of the use cases, but I got through the first 9 or 10 and was able to replicate the end results using xslt. Here's what I see (so far): xquery syntax is less verbose (we all know that). xquery syntax *seems* to have an easier learning curve for persons with a programming background. As far as transformations, I too see quite a bit of overlap. I suppose this will take some time to get sorted out. One thing I'll point out (with the full knowledge that someone will most likely show me that it can, in fact, be done) is that I don't see an obvious way to do 1 to n transformations using xquery. In other words, using xslt, I can use xsl:document or xsl:result-document to produce multiple xml, xhtml, etc. docs from a single xml source...I don't see an obvious way to do this via XQuery. If this holds up, it would cause me to choose xslt for transformations almost every time, as I'm usually doing more than just a 1 to 1 transformation. Rick --- Mike Clark wrote: > > So for those with XSLT experience, I'd be interested > to hear your > opinions on what XQuery brings to the table. As the > spec matures it's > likely to be a reoccurring and important > conversation, as Michael > pointed out. And since I've already shown how > little I know about their > differences (thanks, Jeni!), I thought I'd go ahead > and start tugging on > the thread. > > It's not my intent to provoke a flame war. I'm here > to learn from the > collective wisdom of the group. > > Mike > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk From per@bothner.com Tue Aug 19 10:19:26 2003 Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JHJPHA006839 for ; Tue, 19 Aug 2003 10:19:25 -0700 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.12.9/8.12.9) with ESMTP id h7JHJ6fR003463 for ; Tue, 19 Aug 2003 10:19:06 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Tue, 19 Aug 2003 10:19:02 -0700 Received: from bothner.com (vpn-scv-x1-14.apple.com [17.219.193.14]) by scv3.apple.com (8.12.9/8.12.9) with ESMTP id h7JHJ8eq014253; Tue, 19 Aug 2003 10:19:08 -0700 (PDT) Message-ID: <3F425CCB.7040706@bothner.com> Date: Tue, 19 Aug 2003 10:22:19 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rick schochler Subject: Re: [xquery-talk] Comparing XQuery to XSLT References: <20030819165532.29140.qmail@web40101.mail.yahoo.com> In-Reply-To: <20030819165532.29140.qmail@web40101.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 17:19:26 -0000 rick schochler wrote: > As far as transformations, I too see quite a bit of > overlap. I suppose this will take some time to get > sorted out. One thing I'll point out (with the full > knowledge that someone will most likely show me that > it can, in fact, be done) is that I don't see an > obvious way to do 1 to n transformations using xquery. The Qexo implementation has a "write-to(DATA, URL)" function to write extra output files. I use this for the "picture album" application I mentioned in the previous message: All of the linked web pages are generated by a single XQuery "run". My XML.com article discuss the alternatives. Of course write-to, in addition to being non-standard, is awkward semantically because it is a side-effect in an otherwise side-efefct-free language. In practice, that may not be a problem, but it would complicate any attempt to formally define XQuery. The same problem is also likely for any attempt to add updates to XQuery. -- --Per Bothner per@bothner.com http://per.bothner.com/ From schochler3@yahoo.com Tue Aug 19 10:24:52 2003 Received: from web40101.mail.yahoo.com (web40101.mail.yahoo.com [66.218.78.35]) by jhunter.x-query.com (8.12.8/8.12.4) with SMTP id h7JHOqHA006869 for ; Tue, 19 Aug 2003 10:24:52 -0700 Message-ID: <20030819172448.33483.qmail@web40101.mail.yahoo.com> Received: from [198.185.18.207] by web40101.mail.yahoo.com via HTTP; Tue, 19 Aug 2003 10:24:48 PDT Date: Tue, 19 Aug 2003 10:24:48 -0700 (PDT) From: rick schochler Subject: Re: [xquery-talk] Comparing XQuery to XSLT To: Per Bothner In-Reply-To: <3F425CCB.7040706@bothner.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 17:24:52 -0000 interesting...I was just taking a look at your photo album and will take a look at your article. So, I suppose the next question is, given that you could do the exact same thing using xslt, do you have a preference? Rick --- Per Bothner wrote: > rick schochler wrote: > > > As far as transformations, I too see quite a bit > of > > overlap. I suppose this will take some time to get > > sorted out. One thing I'll point out (with the > full > > knowledge that someone will most likely show me > that > > it can, in fact, be done) is that I don't see an > > obvious way to do 1 to n transformations using > xquery. > > The Qexo implementation has a "write-to(DATA, URL)" > function > to write extra output files. I use this for the > "picture > album" application I mentioned in the previous > message: > All of the linked web pages are generated by a > single > XQuery "run". My XML.com article discuss the > alternatives. > > Of course write-to, in addition to being > non-standard, > is awkward semantically because it is a side-effect > in > an otherwise side-efefct-free language. In > practice, > that may not be a problem, but it would complicate > any > attempt to formally define XQuery. The same problem > is also likely for any attempt to add updates to > XQuery. > -- > --Per Bothner > per@bothner.com http://per.bothner.com/ > > From per@bothner.com Tue Aug 19 10:39:24 2003 Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JHdOHA006887 for ; Tue, 19 Aug 2003 10:39:24 -0700 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.12.9/8.12.9) with ESMTP id h7JHd4fR013232 for ; Tue, 19 Aug 2003 10:39:04 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Tue, 19 Aug 2003 10:38:59 -0700 Received: from bothner.com (vpn-scv-x1-14.apple.com [17.219.193.14]) by scv3.apple.com (8.12.9/8.12.9) with ESMTP id h7JHd5eq024279; Tue, 19 Aug 2003 10:39:06 -0700 (PDT) Message-ID: <3F426179.5020308@bothner.com> Date: Tue, 19 Aug 2003 10:42:17 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rick schochler Subject: Re: [xquery-talk] Comparing XQuery to XSLT References: <20030819172448.33483.qmail@web40101.mail.yahoo.com> In-Reply-To: <20030819172448.33483.qmail@web40101.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 17:39:24 -0000 rick schochler wrote: > interesting...I was just taking a look at your photo > album and will take a look at your article. > > So, I suppose the next question is, given that you > could do the exact same thing using xslt, do you have > a preference? An earlier version did use XSLT, and worked ok, though it had fewer features. I definitely prefer XSLT - and my article partly explains why. I've thought you could have the best of both with a "minor" XQuery extension to handle patterns: Extend SequenceType to allow: "match" where matches the XSLT definition of pattern. Then a set of XSLT template rules can map directly into a typeswitch: typeswitch ($dot) { case match chapter/title return process-chapter-title($dot) case metch title return process-other-title($dot) } -- --Per Bothner per@bothner.com http://per.bothner.com/ From mhk@mhk.me.uk Tue Aug 19 11:28:59 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JISvHA006946 for ; Tue, 19 Aug 2003 11:28:58 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (DomainNamesGB Mailserver v4.6.72) with ESMTP id FJMQLY; Tue, 19 Aug 2003 19:31:37 +0100 From: "Michael Kay" To: "'Mike Clark'" , "'Jeni Tennison'" Subject: RE: [xquery-talk] Comparing XQuery to XSLT Date: Tue, 19 Aug 2003 19:30:24 +0100 Message-ID: <015d01c3667f$f4a32c40$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <3F424DA4.4040101@clarkware.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 18:28:59 -0000 I think the main advantages of XQuery 1.0 over XSLT 2.0 are (a) concise syntax. Largely a cosmetic/psychological benefit, but a real one. In practice, though, I worry about what a 1000-line XQuery is going to look like. The XML-based syntax of XSLT has some practical advantages when you get to this scale. (b) joins. For people who think in SQL terms, or whose data is organized in a tabular form, complex joins are definitely easier to express in XQuery than in XSLT. (c) database orientation. This isn't really a language feature but it's a feature of the way most implementors will be implementing the language - processors will be designed to handle gigabytes of persistent data, not megabytes of in-memory data. In terms of functionality, XSLT 2.0 has many things that XQuery lacks: template rules, grouping, analyze-string, keys, multiple output files, serialization control, format-number, format-date, xsl:number, generate-id, a full set of axes. One thing I hope eventually to do in Saxon is to allow interoperation between the XSLT and XQuery sides of the product, so you can get the best of both worlds by mixing languages. Michael Kay > -----Original Message----- > From: talk-bounces@x-query.com > [mailto:talk-bounces@x-query.com] On Behalf Of Mike Clark > Sent: 19 August 2003 17:18 > To: Jeni Tennison > Cc: talk@x-query.com > Subject: [xquery-talk] Comparing XQuery to XSLT > > > > So for those with XSLT experience, I'd be interested to hear your > opinions on what XQuery brings to the table. As the spec > matures it's > likely to be a reoccurring and important conversation, as Michael > pointed out. And since I've already shown how little I know > about their > differences (thanks, Jeni!), I thought I'd go ahead and start > tugging on > the thread. > > It's not my intent to provoke a flame war. I'm here to learn > from the > collective wisdom of the group. > > Mike > > _______________________________________________ > talk@x-query.com > http://www.x-query.com/mailman/listinfo/talk > From jhunter@servlets.com Tue Aug 19 11:45:40 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7JIjdHA006968 for ; Tue, 19 Aug 2003 11:45:40 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h7JIlrml006518; Tue, 19 Aug 2003 11:47:53 -0700 (PDT) Message-ID: <3F427050.9040006@servlets.com> Date: Tue, 19 Aug 2003 11:45:36 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rick schochler Subject: Re: [xquery-talk] Comparing XQuery to XSLT References: <20030819165532.29140.qmail@web40101.mail.yahoo.com> In-Reply-To: <20030819165532.29140.qmail@web40101.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 18:45:40 -0000 rick schochler wrote: > In other words, using xslt, I can use xsl:document or > xsl:result-document to produce multiple xml, xhtml, > etc. docs from a single xml source...I don't see an > obvious way to do this via XQuery. Here's a query returning two document nodes: document { } , document { } -jh- From schochler3@yahoo.com Tue Aug 19 13:07:11 2003 Received: from web40110.mail.yahoo.com (web40110.mail.yahoo.com [66.218.78.44]) by jhunter.x-query.com (8.12.8/8.12.4) with SMTP id h7JK7AHA007075 for ; Tue, 19 Aug 2003 13:07:10 -0700 Message-ID: <20030819200704.45421.qmail@web40110.mail.yahoo.com> Received: from [198.185.18.207] by web40110.mail.yahoo.com via HTTP; Tue, 19 Aug 2003 13:07:04 PDT Date: Tue, 19 Aug 2003 13:07:04 -0700 (PDT) From: rick schochler Subject: Re: [xquery-talk] Comparing XQuery to XSLT To: Jason Hunter In-Reply-To: <3F427050.9040006@servlets.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: talk@x-query.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 20:07:11 -0000 I don't think the query you describe solves my request...that is, generating multiple .xml (or whatever) files from a single source. Rather, it will return two distinct nodes, it is then up to you to determine what to do with these nodes...if they're returned to anything checking for well-formedness, you'll get an error message. Rick --- Jason Hunter wrote: > rick schochler wrote: > > > In other words, using xslt, I can use xsl:document > or > > xsl:result-document to produce multiple xml, > xhtml, > > etc. docs from a single xml source...I don't see > an > > obvious way to do this via XQuery. > > Here's a query returning two document nodes: > > document { } , document { } > > -jh- > > From Dmitri.Colebatch@toyota.com.au Tue Aug 19 17:02:09 2003 Received: from mail1.toyota.com.au ([203.44.186.202]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7K01xHA007278 for ; Tue, 19 Aug 2003 17:02:05 -0700 Received: from SHM_ISD_A2_80.tmca.com.au (Not Verified[150.45.153.90]) by mail1.toyota.com.au with NetIQ MailMarshal (v5.5.4.16) id ; Wed, 20 Aug 2003 09:56:08 +1000 Sensitivity: Subject: Re: [xquery-talk] Article: "Five Practical XQuery Applications" To: talk@x-query.com X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Dmitri.Colebatch@toyota.com.au Date: Wed, 20 Aug 2003 10:03:33 +1000 X-MIMETrack: Serialize by Router on SHM_ISD_A2_80/TMCA(Release 5.0.12 |February 13, 2003) at 20/08/2003 10:05:30 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2003 00:02:10 -0000 We are using it, in part at least, for converting data from SAP into an industry format. However, the implementation we're using is based on the August 2002 draft, and misses a few things from that (user functions and binding external variables come to mind) - as such we have a bit of a bastardized approach using XQuery (really just XPath) for querying the incoming data, and then using XMLBeans (http://dev2dev.bea.com/technologies/xmlbeans/index.jsp - can be used on any 1.4 jvm, no requirement for WL unless you want to use the XQuery interface with it) to construct the outgoing object. its a fairly awkward approach, but we found that due to limitations in the xquery implementation we couldn't do the transformation purely in xquery... my 2c cheers dim Mike Clark @x-query.com on 20/08/2003 01:16:55 AM Sent by: talk-bounces@x-query.com To: talk@x-query.com cc: Subject: Re: [xquery-talk] Article: "Five Practical XQuery Applications" Michael Kay wrote: > Actually, my reading of the article is that the examples are entirely > hypothetical, I don't read them as case studies of things that people > are doing today. > Yes, that was my reading of the article, as well. I should have said: Realizing that the spec is still in working draft, I'd be interested to hear of _any_ real-world problems that folks are tackling, in whole or in part, with XQuery. Mike _______________________________________________ talk@x-query.com http://www.x-query.com/mailman/listinfo/talk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DISCLAIMER * This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of Toyota. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Toyota. * Please scan this email and any attachment for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From jhunter@servlets.com Thu Aug 21 10:26:51 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7LHQptt009603 for ; Thu, 21 Aug 2003 10:26:51 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h7LHSvml025590 for ; Thu, 21 Aug 2003 10:28:58 -0700 (PDT) Message-ID: <3F4500D7.50509@servlets.com> Date: Thu, 21 Aug 2003 10:26:47 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: [xquery-talk] Testing as xquery.com X-BeenThere: talk@x-query.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2003 17:26:51 -0000 I'm now the proud owner of xquery.com (without the dash) and I'm testing that the list is now configured to work correctly as talk@xquery.com. Test #3. -jh- From jhunter@servlets.com Fri Aug 22 16:34:26 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7MNYPtt011152 for ; Fri, 22 Aug 2003 16:34:26 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h7MNaTml007928 for ; Fri, 22 Aug 2003 16:36:30 -0700 (PDT) Message-ID: <3F46A881.2010305@servlets.com> Date: Fri, 22 Aug 2003 16:34:25 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xquery-talk] New XQuery drafts X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Aug 2003 23:34:26 -0000 New XQuery drafts came out today. The updated docs are: XQuery 1.0 Use Cases Formal Semantics Requirements (noting how each is satisfied or why it isn't) Not updated are the two docs that earlier went to Last Call: F&O Data Model The fast links on xquery.com always point at the latest. -jh- From mike@clarkware.com Mon Aug 25 16:15:05 2003 Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by jhunter.x-query.com (8.12.8/8.12.4) with ESMTP id h7PNF2tt014949 for ; Mon, 25 Aug 2003 16:15:05 -0700 Received: from clarkware.com (12-254-54-55.client.attbi.com[12.254.54.55](untrusted sender)) by comcast.net (rwcrmhc12) with SMTP id <20030825231501014006epghe> (Authid: clarkware); Mon, 25 Aug 2003 23:15:01 +0000 Message-ID: <3F4A981A.7030400@clarkware.com> Date: Mon, 25 Aug 2003 17:13:30 -0600 From: Mike Clark User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xquery-talk] XQuery Engines X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2003 23:15:05 -0000 I've been experimenting with XQuery using both Qexo and IPSI-XQ. What other engines are folks having good success with? Mike From schochler3@yahoo.com Mon Aug 25 16:21:13 2003 Received: from web40106.mail.yahoo.com (web40106.mail.yahoo.com [66.218.78.40]) by jhunter.x-query.com (8.12.8/8.12.4) with SMTP id h7PNLDtt014970 for ; Mon, 25 Aug 2003 16:21:13 -0700 Message-ID: <20030825232111.49129.qmail@web40106.mail.yahoo.com> Received: from [24.209.13.13] by web40106.mail.yahoo.com via HTTP; Mon, 25 Aug 2003 16:21:11 PDT Date: Mon, 25 Aug 2003 16:21:11 -0700 (PDT) From: rick schochler Subject: Re: [xquery-talk] XQuery Engines To: Mike Clark , talk@xquery.com In-Reply-To: <3F4A981A.7030400@clarkware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2003 23:21:13 -0000 For a free engine, try the latest version of Saxon. Rick --- Mike Clark wrote: > > I've been experimenting with XQuery using both Qexo > and IPSI-XQ. What > other engines are folks having good success with? > > Mike > > _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk From Sullivan.Sean@menlolog.com Thu Sep 4 11:30:18 2003 Received: from ljcqs031.cnf.com (mail-cluster.cnf.com [63.230.177.41]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h84IUIm9018655 for ; Thu, 4 Sep 2003 11:30:18 -0700 Received: from cnfqs039.cnf.com (localhost [127.0.0.1]) by ljcqs031.cnf.com (Postfix) with ESMTP id 3B82326F69D for ; Thu, 4 Sep 2003 11:30:20 -0700 (PDT) Received: by cnfqs039.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Thu, 4 Sep 2003 11:30:19 -0700 Message-ID: <462D5240F6F9154AB0F9B345A5F03E3E3A1A44@cnfqe029.cnf.prod.cnf.com> From: "Sullivan, Sean C - MWT" To: "'talk@xquery.com'" Date: Thu, 4 Sep 2003 11:30:17 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] IBM article: XQuery, Don Chamberlin's book X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Sep 2003 18:30:18 -0000 This book excerpt explores the origins of the XQuery language: http://www-106.ibm.com/developerworks/xml/library/x-xqbook.html From jhunter@servlets.com Tue Sep 9 23:27:51 2003 Received: from servlets.com ([65.122.201.44]) (authenticated bits=0) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h8A6Rom9030654 for ; Tue, 9 Sep 2003 23:27:51 -0700 Message-ID: <3F5EC46D.7060808@servlets.com> Date: Tue, 09 Sep 2003 23:27:57 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xquery-talk] Test post X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2003 06:27:51 -0000 Some people have reported problems posting. Trying myself. -jh- From Sullivan.Sean@menlolog.com Wed Sep 10 08:49:58 2003 Received: from ljcqs030.cnf.com (mail-cluster.cnf.com [63.230.177.41]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h8AFnwm9003166 for ; Wed, 10 Sep 2003 08:49:58 -0700 Received: from cnfqs039.cnf.com (localhost [127.0.0.1]) by ljcqs030.cnf.com (Postfix) with ESMTP id 99D42143DA4 for ; Wed, 10 Sep 2003 08:49:57 -0700 (PDT) Received: by cnfqs039.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Wed, 10 Sep 2003 08:49:57 -0700 Message-ID: <462D5240F6F9154AB0F9B345A5F03E3E012E277B@cnfqe029.cnf.prod.cnf.com> From: "Sullivan, Sean C - MWT" To: "'talk@xquery.com'" Date: Wed, 10 Sep 2003 08:49:55 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] IBM article: XQuery, Don Chamberlin's book X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2003 15:49:58 -0000 This book excerpt explores the origins of the XQuery language: http://www-106.ibm.com/developerworks/xml/library/x-xqbook.html From Steve.Tolkin@FMR.COM Mon Sep 15 12:57:59 2003 Received: from maillnx-us112.fmr.com (maillnx-us112.fmr.com [192.223.198.27]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h8FJvx32010317 for ; Mon, 15 Sep 2003 12:57:59 -0700 Received: from virmro111nts.fmr.com (VIRMRO111NTS.fmr.com [172.26.5.99]) by maillnx-us112.fmr.com (Switch-2.2.6/Switch-2.2.6) with SMTP id h8FJw1Z01815 for ; Mon, 15 Sep 2003 15:58:01 -0400 Received: by MSGBOS102NTS.fmr.com with Internet Mail Service (5.5.2654.89) id ; Mon, 15 Sep 2003 15:58:00 -0400 Message-ID: <176FDD8DC56B4946946917ECEBA4DA55CD4352@MSGBOSCLA2WIN.DMN1.FMR.COM> From: "Tolkin, Steve" To: "'talk@x-query.com'" Date: Mon, 15 Sep 2003 15:57:52 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2654.89) Content-Type: multipart/mixed; boundary="----=_NextPartTM-000-0eeca3bf-dfe9-4097-bd6d-5430e8de5516" X-Mailman-Approved-At: Mon, 15 Sep 2003 13:24:19 -0700 Cc: Subject: [xquery-talk] Please remove "PS: Don't forget the dash!" X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 19:58:00 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------=_NextPartTM-000-0eeca3bf-dfe9-4097-bd6d-5430e8de5516 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C37BC3.A560F6FC" ------_=_NextPart_001_01C37BC3.A560F6FC Content-Type: text/plain The home page still says: PS: Don't forget the dash! even though in http://xquery.com/pipermail/talk/2003-August/000081.html you say: I'm now the proud owner of xquery.com (without the dash) and I'm testing that the list is now configured to work correctly as talk at xquery.com. Hopefully helpfully yours, Steve -- Steven Tolkin steve . tolkin at fmr dot com 617-563-0516 Fidelity Investments 82 Devonshire St. V4D Boston MA 02109 There is nothing so practical as a good theory. Comments are by me, not Fidelity Investments, its subsidiaries or affiliates. ------_=_NextPart_001_01C37BC3.A560F6FC Content-Type: text/html Content-Transfer-Encoding: quoted-printable Please remove "PS: Don't forget the dash!"

The home page still says:
PS: Don't forget the dash!
even though in http://xquery.com/pipermail/talk/2003-August/000081.html<= /FONT> you say:
I'm now the proud owner of = xquery.com (without the dash) and I'm testing that the list is now = configured to work correctly as talk at = xquery.com.


Hopefully helpfully = yours,
Steve
--
Steven Tolkin    = steve . tolkin at fmr dot com   617-563-0516
Fidelity = Investments   82 Devonshire St. V4D     = Boston MA 02109
There is nothing so practical = as a good theory.  Comments are by me,
not Fidelity Investments, its = subsidiaries or affiliates.


------_=_NextPart_001_01C37BC3.A560F6FC-- ------=_NextPartTM-000-0eeca3bf-dfe9-4097-bd6d-5430e8de5516-- From jhunter@servlets.com Mon Sep 15 14:24:07 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h8FLO632011698 for ; Mon, 15 Sep 2003 14:24:07 -0700 Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h8FLQHxr021841; Mon, 15 Sep 2003 14:26:18 -0700 (PDT) Message-ID: <3F662DF0.1060603@servlets.com> Date: Mon, 15 Sep 2003 14:24:00 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Tolkin, Steve" Subject: Re: [xquery-talk] Please remove "PS: Don't forget the dash!" References: <176FDD8DC56B4946946917ECEBA4DA55CD4352@MSGBOSCLA2WIN.DMN1.FMR.COM> In-Reply-To: <176FDD8DC56B4946946917ECEBA4DA55CD4352@MSGBOSCLA2WIN.DMN1.FMR.COM> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: "'talk@x-query.com'" X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 21:24:07 -0000 Done! I fixed the graphic too. Had this cleanup on my to do list, but you popped it to the top. :-) -jh- Tolkin, Steve wrote: > The home page still says: > PS: Don't forget the dash! > even though in > _http://xquery.com/pipermail/talk/2003-August/000081.html_ you say: > I'm now the proud owner of xquery.com (without the dash) and I'm testing > that the list is now configured to work correctly as _talk at > xquery.com._ > > > Hopefully helpfully yours, > Steve > -- > Steven Tolkin steve . tolkin at fmr dot com 617-563-0516 > Fidelity Investments 82 Devonshire St. V4D Boston MA 02109 > There is nothing so practical as a good theory. Comments are by me, > not Fidelity Investments, its subsidiaries or affiliates. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk From D.McBeath@elsevier.com Wed Sep 17 17:51:51 2003 Received: from elsoxfs03089.elsevier.co.uk (elsoxfs03089.elsevier.co.uk [193.131.223.7]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h8I0po32005621 for ; Wed, 17 Sep 2003 17:51:51 -0700 Received: from elsoxfs30373.elsevier.com (unverified) by elsoxfs03089.elsevier.co.uk (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Thu, 18 Sep 2003 01:52:26 +0100 Received: by elsoxfs30373.elsevier.co.uk with Internet Mail Service (5.5.2655.55) id ; Thu, 18 Sep 2003 01:48:28 +0100 Message-ID: From: "McBeath, Darin W. (ELS)" To: "'talk@xquery.com'" Date: Thu, 18 Sep 2003 01:47:38 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain Subject: [xquery-talk] Library Modules and URIs X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 00:51:51 -0000 I was curious how everyone is using the URI field (string literal) to define a library module within xquery. I have been considering the following approach (within Java) and would like some opinions from this group on the approach. The approach centers around using a Java packaging scheme style as the URI for a library module. For example, I could place a group of utility functions within a library module with a URI of "com.elsevier.xquery.functions.util". The XQuery engine would conceivably either directly map this URI to the physical location of the library module (would not require the "at location" when importing the module) or else it would provide a base path for the location of library modules (via some form of configuration option) and would require the "at location" when importing the module. If the latter approach is used, the URI described above could easily become the path (by replacing the '.' with '/') appending to the base path for locating the library module. One could then easily author a 'wrapper' object which accepts the URI for the library module contianing the needed function, function name, and array of parms to then invoke the function. This nicely separates the XQuery code from the Java code. This also allows a Java style of packaging for XQuery functions. In any case, I would be curious to anyones thoughts on this approach. From mhk@mhk.me.uk Thu Sep 18 08:34:16 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h8IFYE32012517 for ; Thu, 18 Sep 2003 08:34:15 -0700 Received: from pcukmka ([216.95.193.120]) by mail.domainnamesgb.com (DomainNamesGB Mailserver v4.6.72) with ESMTP id FJMQLY; Thu, 18 Sep 2003 16:37:05 +0100 From: "Michael Kay" To: "'McBeath, Darin W. \(ELS\)'" , Subject: RE: [xquery-talk] Library Modules and URIs Date: Thu, 18 Sep 2003 16:35:56 +0100 Message-ID: <000501c37dfa$8e123600$78c15fd8@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 15:34:16 -0000 I think some people are thinking in terms of having a fairly close association between the namespace used for a set of elements and attributes, and a module that contains functions applicable to those elements. Michael Kay > -----Original Message----- > From: talk-bounces@xquery.com > [mailto:talk-bounces@xquery.com] On Behalf Of McBeath, Darin W. (ELS) > Sent: 18 September 2003 01:48 > To: 'talk@xquery.com' > Subject: [xquery-talk] Library Modules and URIs > > > I was curious how everyone is using the URI field (string > literal) to define a library module within xquery. I have > been considering the following approach (within Java) and > would like some opinions from this group on the approach. > > The approach centers around using a Java packaging scheme > style as the URI for a library module. For example, I could > place a group of utility functions within a library module > with a URI of "com.elsevier.xquery.functions.util". The > XQuery engine would conceivably either directly map this URI > to the physical location of the library module (would not > require the "at location" when importing the module) or else > it would provide a base path for the location of library > modules (via some form of configuration option) and would > require the "at location" when importing the module. If the > latter approach is used, the URI described above could easily > become the path (by replacing the '.' with '/') appending to > the base path for locating the library module. > > One could then easily author a 'wrapper' object which accepts > the URI for the library module contianing the needed > function, function name, and array of parms to then invoke > the function. This nicely separates the XQuery code from the > Java code. This also allows a Java style of packaging for > XQuery functions. > > In any case, I would be curious to anyones thoughts on this > approach. _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk > From Sullivan.Sean@menlolog.com Thu Sep 18 11:05:14 2003 Received: from ljcqs031.cnf.com (mail-cluster.cnf.com [63.230.177.41]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h8II5E32014007 for ; Thu, 18 Sep 2003 11:05:14 -0700 Received: from cnfqs039.cnf.com (localhost [127.0.0.1]) by ljcqs031.cnf.com (Postfix) with ESMTP id BBC6426F2A6 for ; Thu, 18 Sep 2003 11:05:14 -0700 (PDT) Received: by cnfqs039.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Thu, 18 Sep 2003 11:05:14 -0700 Message-ID: <462D5240F6F9154AB0F9B345A5F03E3E3A1A98@cnfqe029.cnf.prod.cnf.com> From: "Sullivan, Sean C - MWT" To: talk@xquery.com Date: Thu, 18 Sep 2003 11:05:08 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xquery-talk] Per Bothner's XQuery article X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 18:05:14 -0000 Per Bothner's XQuery article Published on September 10, 2003 http://www.xml.com/pub/a/2003/09/10/xquery.html From per@bothner.com Thu Sep 18 13:06:52 2003 Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h8IK6q32015360 for ; Thu, 18 Sep 2003 13:06:52 -0700 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.12.9/8.12.9) with ESMTP id h8IK6miZ020700 for ; Thu, 18 Sep 2003 13:06:48 -0700 (PDT) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Thu, 18 Sep 2003 13:06:22 -0700 Received: from bothner.com (vpn-scv-x1-96.apple.com [17.219.193.96]) by scv1.apple.com (8.12.9/8.12.9) with ESMTP id h8IK6TsH024840; Thu, 18 Sep 2003 13:06:30 -0700 (PDT) Message-ID: <3F6A1127.5020106@bothner.com> Date: Thu, 18 Sep 2003 13:10:15 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "McBeath, Darin W. (ELS)" Subject: Re: [xquery-talk] Library Modules and URIs References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: "'talk@xquery.com'" X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 20:06:52 -0000 McBeath, Darin W. (ELS) wrote: > I was curious how everyone is using the URI field (string literal) to define > a library module within xquery. I have been considering the following > approach (within Java) and would like some opinions from this group on the > approach. My plan is that Qexo would compile a Library Module to a Java class, generating the Java class name from the StringLiteral, probably using a "mangling" based on the one in JAXB. Each function would be compiled to a static Java method, as well as a static field whose value is a Procedure object that describes the function. (This is based on how Kawa compiles modules written in the Scheme language to classes.) When importing a module, I'd just ignore the 'at' clause. (At least initially. A later version might search for a jar by the specified name.) It would just map the namespace url to a class name, and "load" that. I hadn't planned on implementing modules for the next Kawa release, but I guess I should just do it, given that most of work is already done. -- --Per Bothner per@bothner.com http://per.bothner.com/ From john.zink@prudential.com Thu Oct 2 11:34:11 2003 Received: from pa-mailgate2.prudential.com (ny-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h92IYA32005278 for ; Thu, 2 Oct 2003 11:34:11 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h92IYBcJ021846 for ; Thu, 2 Oct 2003 14:34:11 -0400 (EDT) From: john.zink@prudential.com To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: Sender: john.zink@prudential.com Date: Thu, 2 Oct 2003 14:34:08 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/02/2003 02:34:10 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [xquery-talk] Date Arithmetic X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2003 18:34:11 -0000 I need the ability to compare 2 dates and be able to specify if the results are returned in months or days. Is there a built-in XQuery function that can perform this type of arithmetic. For example: 10-31-2003 - 10-01-2003 = 30 days 10-31-2003 - 8-01-2003 = 2 months From xfranc@online.fr Thu Oct 2 14:01:43 2003 Received: from ns18.abergement.ch ([62.50.79.8]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h92L1g32006414 for ; Thu, 2 Oct 2003 14:01:43 -0700 Received: from online.fr (lns-th2-11-82-64-240-52.adsl.proxad.net [82.64.240.52]) (authenticated) by ns18.abergement.ch (8.11.6/8.11.6) with ESMTP id h92Ixd414443 for ; Thu, 2 Oct 2003 20:59:39 +0200 Message-ID: <3F7C920F.8020706@online.fr> Date: Thu, 02 Oct 2003 23:01:03 +0200 From: Xavier Franc User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Subject: [xquery-talk] Date Arithmetic Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2003 21:01:44 -0000 The current XML Query specifications define a '-' operator on dates, yielding a result of type xdt:dayTimeDuration. From this thing you can in principle extract a number of days or months, but this is neither very easy nor very clear. To the best of my knowledge, no current XML Query engine actually implements these specifications. However, my own implementation (Qizx/open), which is dissident wrt the specs in this respect, provides exactly what you want: the difference of two dates yields a number of days as an integer. the difference of two dateTimes yields a number of seconds as a double. There is apparently a move towards more sensible specifications inited by Michael Kay. Note: dates must be specified according to ISO 8601 standard: 10-31-2003 should be written 2003-10-31 [ precisely: xs:date("2003-10-31") ] -- Xavier FRANC From mhk@mhk.me.uk Thu Oct 2 15:28:48 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h92MSk32007277 for ; Thu, 2 Oct 2003 15:28:48 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (DomainNamesGB Mailserver v4.6.72) with ESMTP id FJMQLY; Thu, 02 Oct 2003 23:31:45 +0100 From: "Michael Kay" To: , Subject: RE: [xquery-talk] Date Arithmetic Date: Thu, 2 Oct 2003 23:30:38 +0100 Message-ID: <002e01c38934$cea65da0$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2003 22:28:48 -0000 See: http://www.w3.org/TR/xpath-functions/#func-subtract-dateTimes-yielding-d ayTimeDuration http://www.w3.org/TR/xpath-functions/#func-subtract-dateTimes-yielding-y earMonthDuration But don't necessarily expect to find these functions implemented; this area of the spec hasn't been all that stable between drafts. Michael Kay > -----Original Message----- > From: talk-bounces@xquery.com > [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com > Sent: 02 October 2003 19:34 > To: talk@xquery.com > Subject: [xquery-talk] Date Arithmetic > > > I need the ability to compare 2 dates and be able to specify > if the results are returned in months or days. Is there a > built-in XQuery function that can perform this type of arithmetic. > > For example: > > 10-31-2003 - 10-01-2003 = 30 days > 10-31-2003 - 8-01-2003 = 2 months > > > _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk > From jhunter@xquery.com Tue Oct 14 15:31:15 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9EMVFZK009208 for ; Tue, 14 Oct 2003 15:31:15 -0700 Received: from xquery.com ([192.168.1.49]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9EMbLD9004973 for ; Tue, 14 Oct 2003 15:37:21 -0700 (PDT) Message-ID: <3F8C7A0E.4090803@xquery.com> Date: Tue, 14 Oct 2003 15:34:54 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 14 Oct 2003 15:33:53 -0700 Subject: [xquery-talk] BumbleBee XQuery Test Harness X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2003 22:31:15 -0000 Hi everyone, I'm proud to announce here a product I've helped develop: the BumbleBee XQuery test harness. It's an automated test harness that you can use both for evaluating XQuery engines (seeing which vendor is more spec compliant and scalable) and for validating your own queries (making sure your queries continue to work as you upgrade or change engines). BumbleBee -- named because it buzzes around FLWORs -- has the following features: * Includes over 70 automated tests representative of the W3C XQuery Use Cases * Includes over 1000 automated tests representative of the NIST XQuery Test Suite * Includes adapters to 6 different free and commercial XQuery engines * Includes the runtime libraries for 3 free XQuery engines * Allows you to write and run your own custom XQuery tests * Tests are automated, self checking, and report an unambiguous pass or fail status * Tests can define multiple, possible expected results * Can run arbitrary suites of standard and/or custom tests * Can run tests against one or more XQuery engines * Generates a comprehensive report of passed and failed tests per XQuery engine being tested * Supports the addition of new XQuery engines through a pluggable adapter design * Allows disabling and enabling tests, globally or on a per-engine basis * Allows customization of whitespace comparison behavior * Supports negative testing, where the engine must report an error to pass * Written in Java for maximum portability A free, no-login-required, fully-functioning 30-day evaluation copy of BumbleBee and the "Getting Started With BumbleBee" quick-start guide is available at: http://xquery.com/bumblebee Licensed copies of BumbleBee are available free of charge for developers of open source XQuery implementations, and for qualified non-profit and educational use. Licenses of BumbleBee are available for commercial use by contacting "buzz" at xquery.com with your usage requirements. I hope that this mailing list will host some discussion about the tool and what it discovers about engine quality, so if you have any thoughts please write in. -jh- From philippe.michiels@ua.ac.be Wed Oct 15 00:27:45 2003 Received: from zeus.ruca.ua.ac.be (ns2.ruca.ua.ac.be [143.129.201.210]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9F7RiZK012862 for ; Wed, 15 Oct 2003 00:27:45 -0700 Received: from hmacs.ruca.ua.ac.be (hmacs.ruca.ua.ac.be [143.129.75.10]) by zeus.ruca.ua.ac.be (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id JAA26185 for ; Wed, 15 Oct 2003 09:34:26 +0200 (METDST) Received: from pcinf39.ruca.ua.ac.be (pcinf39.ruca.ua.ac.be [143.129.75.207]) by hmacs.ruca.ua.ac.be (8.11.6/Switch-2.0.0) with ESMTP id h9F7YPC04299 for ; Wed, 15 Oct 2003 09:34:25 +0200 (CEST) From: Philippe Michiels Organization: Universiteit Antwerpen To: talk@xquery.com Date: Wed, 15 Oct 2003 09:32:08 +0200 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310150932.08719.philippe.michiels@ua.ac.be> X-MailScanner-Information: Please contact the HelpDesk for more information X-MailScanner: Found to be clean Subject: [xquery-talk] bubmlebee API implementation X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 07:27:45 -0000 Hi, I read your bumblebee-announcement with great intrest. I'm currently doing some optimization development work on Galax and I wanted to write an adapter for Galax into bumblebee. The problem however, is that I don't know where in de package (bumblebee.jar) the Adapter interface is located and where the AdapterException is located. I tried to find them by unzipping the jar-file but I did not see any corresponding class files. Can anyone help? -- Philippe ----------------------------------------- Philippe Michiels ADReM Research Group -- dept. WisInf Universiteit Antwerpen Middelheimlaan 1 2020 Antwerpen tel: 32 (3) 218 0880 http://win-www.ruca.ua.ac.be/u/michiels ----------------------------------------- From sander@x-hive.com Wed Oct 15 00:31:09 2003 Received: from x-hive.com (a194-109-160-206.adsl.xs4all.nl [194.109.160.206]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9F7V6ZK012920 for ; Wed, 15 Oct 2003 00:31:08 -0700 content-class: urn:content-classes:message Subject: RE: [xquery-talk] BumbleBee XQuery Test Harness Date: Wed, 15 Oct 2003 09:37:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <41D11F414A26E942912B7E7696DC8E2284829D@JAKARTA.xhive.archipel> X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 X-MS-TNEF-Correlator: Thread-Topic: [xquery-talk] BumbleBee XQuery Test Harness Thread-Index: AcOS7z7rxXxvLUCoQr6OJoabparVMg== From: "Sander Bos" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by jhunter.x-query.com id h9F7V6ZK012920 X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 07:31:09 -0000 Dear Jason, > * Supports the addition of new XQuery engines through a pluggable > adapter design > A free, no-login-required, fully-functioning 30-day > evaluation copy of > BumbleBee and the "Getting Started With BumbleBee" > quick-start guide is > available at: A first remark: Is it the idea that you can add your own XQuery adapter with the evaluation copy? If so, it may be an idea not to obfuscate the bumblebee.Adapter interface in the jar. Kind regards, --Sander. From sander@x-hive.com Wed Oct 15 03:07:02 2003 Received: from x-hive.com (a194-109-160-206.adsl.xs4all.nl [194.109.160.206]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FA71ZK014202 for ; Wed, 15 Oct 2003 03:07:02 -0700 content-class: urn:content-classes:message Subject: RE: [xquery-talk] BumbleBee XQuery Test Harness Date: Wed, 15 Oct 2003 12:14:32 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <41D11F414A26E942912B7E7696DC8E2284829E@JAKARTA.xhive.archipel> X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 X-MS-TNEF-Correlator: Thread-Topic: [xquery-talk] BumbleBee XQuery Test Harness Thread-Index: AcOTBSBT/pFYVE2TRAqLNIfC8YUDRA== From: "Sander Bos" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by jhunter.x-query.com id h9FA71ZK014202 X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 10:07:03 -0000 Dear Jason, > I hope that this mailing list will host some discussion about > the tool > and what it discovers about engine quality, so if you have > any thoughts > please write in. I like it very much. IntelliJ did not have much problems deciphering what I was supposed to implement (a possible DMCA violation in your country?). I could write and test an adapter for our product (X-Hive/DB) in about 1.5 hours, including a little 'hacking' (turns out we read over the document -> doc function renaming in the spec), and query adjusting (we implement the later 22 August version of the spec). So congratulations on such an easy to use product! I will post my adapter class on this list once I can run it against a non-obfuscated version of Adapter. With respect to our success percentage, well we have a little work to do.... I did look into detail into the usecases tests (also to tune the adapter against the test-framework). What I saw is that we had some problems with doc(...) as mentioned, maybe we include incorrectly at some points (not sure whether that's a bug), so 800.0 instead of 800, we do not implement import schema yet, we include default attributes when importing into another constructed element (very probably a bug), and then there were a few test failures I could not directly explain (I am not one of the XQuery programmers here). I think there is also a bug in the test-framework that causes hundreds of tests to fail (596 mentions in the log), we have a lot of results like: Query: {fn:boolean(xs:integer("-99999999999999999999"))} Actual Result: true Expected Possible Result 1: true Failure Message 1: Expected node type '3' but was '1' - comparing true at /BumbleBee_Result[1]/text()[1] to at /BumbleBee_Result[1]/results[1] I think we produce the result in the right way, so surrounded by a results element? But BumbleBee does not like it. Kind regards, --Sander. From per@bothner.com Wed Oct 15 07:55:19 2003 Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FEtJZK016642; Wed, 15 Oct 2003 07:55:19 -0700 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id h9FEuBk0004449; Wed, 15 Oct 2003 07:56:11 -0700 (PDT) Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Wed, 15 Oct 2003 07:55:41 -0700 Received: from bothner.com (vpn-scv-x1-70.apple.com [17.219.193.70]) by scv2.apple.com (8.12.9/8.12.9) with ESMTP id h9FEtuWI025798; Wed, 15 Oct 2003 07:55:57 -0700 (PDT) Message-ID: <3F8D60F5.1040003@bothner.com> Date: Wed, 15 Oct 2003 08:00:05 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Hunter Subject: Re: [xquery-talk] BumbleBee XQuery Test Harness References: <3F8C7A0E.4090803@xquery.com> In-Reply-To: <3F8C7A0E.4090803@xquery.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 14:55:19 -0000 I think it is very useful to have a standard framework for writing tests - though an open-osurce framework might be preferable. (Of course you guys have to live, but perhaps dual GPL/commercial license might be worth considering.) Here are some (I hope constructive) questions: The most obvious question is the format of the test cases, and the obvious sub-question is why not XML? Look at the use-cases.xml in Kawa's gnu/xquery/testsuite directory. That is an xml file that contains a subset of the XQuery uses-cases. The file TestSuite.java (which extends TestMisc.java) is the driver. There are pluses and minus on both sides. The bee format is slightly easier for humans to read and write, and it is probably easier to write a bee parser than an xml parser. On the other hand, you presumably already have an xml parser (doesn't jdk 1.4 include one, or does it just have the interfaces?), and having the test file be xml allows yoo to filter and process it - perhaps using xquery. Why do you require jdk 1.4 to run bumblebee? What features do you need not in earlier jdks? Have you tried gcj or kaffe? Why do you use JAVA_HOME? It seems you only use it to get the java executable. Why not just use a $JAVA variable, which defaults to the java in PATH? That seems more portable, given that JAVA_HOME isn't even a Sun standard. Have you written any adapters to XQuery implementations that are *not* Java-based? I see hints of it - the manual implies the cerisent adapter connects over the network. -- --Per Bothner per@bothner.com http://per.bothner.com/ From john.zink@prudential.com Wed Oct 15 08:51:33 2003 Received: from pa-mailgate2.prudential.com (pa-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FFpWZK017426 for ; Wed, 15 Oct 2003 08:51:32 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h9FFqddZ004152 for ; Wed, 15 Oct 2003 11:52:40 -0400 (EDT) From: john.zink@prudential.com To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: Sender: john.zink@prudential.com Date: Wed, 15 Oct 2003 11:52:33 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/15/2003 11:52:39 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [xquery-talk] XQuery Platform Support X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 15:51:33 -0000 Does anyone know what platforms XQuery will be supported on ? Any plans to be supported on the mainframe ? From mhk@mhk.me.uk Wed Oct 15 11:19:33 2003 Received: from mail2.ksc.th.com (mail2.ksc.th.com [203.155.0.233]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FIJUZK019249 for ; Wed, 15 Oct 2003 11:19:33 -0700 Received: from pcukmka ([203.155.16.163]) by mail2.ksc.th.com (8.12.1/8.12.0) with ESMTP id h9FIFopI011769; Thu, 16 Oct 2003 01:15:51 +0700 From: "Michael Kay" To: , Subject: RE: [xquery-talk] XQuery Platform Support Date: Wed, 15 Oct 2003 19:23:17 +0100 Message-ID: <000a01c39349$69439bc0$6900000a@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 18:19:34 -0000 > > Does anyone know what platforms XQuery will be supported on ? > > Any plans to be supported on the mainframe ? > Tamino is supported ("is", not "will be") on a full range of platforms including IBM Mainframes. Michael Kay Software AG From john.zink@prudential.com Wed Oct 15 12:23:34 2003 Received: from pa-mailgate2.prudential.com (ny-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FJNYZK020061 for ; Wed, 15 Oct 2003 12:23:34 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h9FJM7dY025134; Wed, 15 Oct 2003 15:22:07 -0400 (EDT) Subject: RE: [xquery-talk] XQuery Platform Support To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: john.zink@prudential.com Date: Wed, 15 Oct 2003 15:22:00 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/15/2003 03:22:06 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Cc: ktegels@msn.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 19:23:35 -0000 I actually have a program up and running that is using the .Net demo version of the XQuery classes. I need to know the future of XQuery on the mainframe and here is why. I have .Net server programming running that is generating XQuery statements as part of a rules engine, but I also need the rules to run on the mainframe. If I can export the statements into a host program I'll be golden;otherwise, I will need to rethink my approach. thanks for your responses, John Z "kent tegels" To: cc: Wednesday October 15, 2003 01:41 PM Subject: RE: [xquery-talk] XQuery Platform Support Without getting into the details due to NDA issues, I can say that SQL Server Yukon and version 1.2 of the .NET CLR will *likely* have support. kt -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Wednesday, October 15, 2003 10:53 AM To: talk@xquery.com Subject: [xquery-talk] XQuery Platform Support Does anyone know what platforms XQuery will be supported on ? Any plans to be supported on the mainframe ? _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From per@bothner.com Wed Oct 15 12:40:33 2003 Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FJeWZK020279 for ; Wed, 15 Oct 2003 12:40:33 -0700 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id h9FJh5k0016385 for ; Wed, 15 Oct 2003 12:43:05 -0700 (PDT) Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Wed, 15 Oct 2003 12:42:34 -0700 Received: from bothner.com (vpn-scv-x1-70.apple.com [17.219.193.70]) by scv2.apple.com (8.12.9/8.12.9) with ESMTP id h9FJgoWI026571; Wed, 15 Oct 2003 12:42:50 -0700 (PDT) Message-ID: <3F8DA433.9020709@bothner.com> Date: Wed, 15 Oct 2003 12:46:59 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: john.zink@prudential.com Subject: Re: [xquery-talk] XQuery Platform Support References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com, ktegels@msn.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 19:40:33 -0000 john.zink@prudential.com wrote: > I need to know the future of XQuery on the mainframe and here is why. A number of XQuery implementations come as source code or as Java bytecodes. So they will probably run if you have a compiler for that language they're written in or a JVM on your mainframe. For example my own Qexo is pure portable Java, so should run anywhere that runs Java. (It can run on JVM 1.1, if you re-build Qexo.) A separate issue is the form of your data. If your XQuery rules just need to read and write XML text files, then must XQuery implementation can handle that. If you need to interface to some database then it may be a different matter. -- --Per Bothner per@bothner.com http://per.bothner.com/ From jhunter@xquery.com Wed Oct 15 13:51:41 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FKpfZK020982 for ; Wed, 15 Oct 2003 13:51:41 -0700 Received: from xquery.com ([192.168.1.44]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9FKuvD9014064; Wed, 15 Oct 2003 13:56:57 -0700 (PDT) Message-ID: <3F8DB40A.2040108@xquery.com> Date: Wed, 15 Oct 2003 13:54:34 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Philippe Michiels Subject: Re: [xquery-talk] bubmlebee API implementation References: <200310150932.08719.philippe.michiels@ua.ac.be> In-Reply-To: <200310150932.08719.philippe.michiels@ua.ac.be> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 20:51:41 -0000 Philippe Michiels wrote: > Hi, > > I read your bumblebee-announcement with great intrest. I'm currently doing > some optimization development work on Galax and I wanted to write an adapter > for Galax into bumblebee. The problem however, is that I don't know where in > de package (bumblebee.jar) the Adapter interface is located and where the > AdapterException is located. I tried to find them by unzipping the jar-file > but I did not see any corresponding class files. > > Can anyone help? Hi Philippe, We'd be very happy to have a Galax adapter! The "Getting Started" guide has instructions for writing a custom adapter. However, the classes were mistakenly not fully open in the 1.0 distribution. We've re-released a 1.0.1 that includes the Adapter classes. Please be in touch with us if you need help or when you've finished. -jh- From jhunter@xquery.com Wed Oct 15 14:06:05 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FL65ZK021101 for ; Wed, 15 Oct 2003 14:06:05 -0700 Received: from xquery.com ([192.168.1.44]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9FLBUD9014158; Wed, 15 Oct 2003 14:11:32 -0700 (PDT) Message-ID: <3F8DB776.3050505@xquery.com> Date: Wed, 15 Oct 2003 14:09:10 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sander Bos Subject: Re: [xquery-talk] BumbleBee XQuery Test Harness References: <41D11F414A26E942912B7E7696DC8E2284829E@JAKARTA.xhive.archipel> In-Reply-To: <41D11F414A26E942912B7E7696DC8E2284829E@JAKARTA.xhive.archipel> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 21:06:05 -0000 Sander Bos wrote: > I could write and test an adapter for our product (X-Hive/DB) in about > 1.5 hours, including a little 'hacking' (turns out we read over the > document -> doc function renaming in the spec), and query adjusting (we > implement the later 22 August version of the spec). So congratulations > on such an easy to use product! Thanks for the props! I'm glad BumbleBee helped you discover a spec compliance issue in its first day. We'll be adding August tests in the 2003-08 directory before long. > I will post my adapter class on this > list once I can run it against a non-obfuscated version of Adapter. The open Adapter classes are available in the 1.0.1 release, now online. > With respect to our success percentage, well we have a little work to > do.... I did look into detail into the usecases tests (also to tune the > adapter against the test-framework). What I saw is that we had some > problems with doc(...) as mentioned, maybe we include incorrectly at > some points (not sure whether that's a bug), so 800.0 instead of 800 Yes, some vendors serialize an xs:double without the .0 but http://www.w3.org/TR/xmlschema-2/#double says this is incorrect and the .0 is necessary. In the 1.0.1 release we updated a few test results accordingly. BTW, you can see what's new in the CHANGES.txt file with the distribution. > we > do not implement import schema yet, we include default attributes when > importing into another constructed element (very probably a bug), and > then there were a few test failures I could not directly explain (I am > not one of the XQuery programmers here). I look forward to everyone reaching 100% compliance on the use cases. Then we'll be able to expand beyond. The Use Cases themselves cover just a portion of the full specification. If people want to contribute tests, we have a "custom" area specifically for this. You'll see some tests I've written in there. > I think there is also a bug in the test-framework that causes hundreds > of tests to fail (596 mentions in the log), we have a lot of results > like: > Query: > > {fn:boolean(xs:integer("-99999999999999999999"))} > > Actual Result: > true > Expected Possible Result 1: > true > Failure Message 1: > Expected node type '3' but was '1' - comparing > true at /BumbleBee_Result[1]/text()[1] to > at /BumbleBee_Result[1]/results[1] > > I think we produce the result in the right way, so surrounded by a > results element? But BumbleBee does not like it. Yes, you are correct. That also is fixed in 1.0.1. -jh- From jhunter@xquery.com Wed Oct 15 14:43:17 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FLhHZK021589 for ; Wed, 15 Oct 2003 14:43:17 -0700 Received: from xquery.com ([192.168.1.44]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9FLmvD9014421; Wed, 15 Oct 2003 14:48:57 -0700 (PDT) Message-ID: <3F8DC03D.50408@xquery.com> Date: Wed, 15 Oct 2003 14:46:37 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Per Bothner Subject: Re: [xquery-talk] BumbleBee XQuery Test Harness References: <3F8C7A0E.4090803@xquery.com> <3F8D60F5.1040003@bothner.com> In-Reply-To: <3F8D60F5.1040003@bothner.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 21:43:18 -0000 Per Bothner wrote: > I think it is very useful to have a standard framework for > writing tests Absolutely! In my mind, the most likely achilles heel of XQuery is its portability. BumbleBee should help keep that in check. > Here are some (I hope constructive) questions: > > The most obvious question is the format of the test cases, and the > obvious sub-question is why not XML? Look at the use-cases.xml > in Kawa's gnu/xquery/testsuite directory. That is an xml file > that contains a subset of the XQuery uses-cases. The file > TestSuite.java (which extends TestMisc.java) is the driver. > > There are pluses and minus on both sides. The bee format is > slightly easier for humans to read and write, and it is probably > easier to write a bee parser than an xml parser. On the other hand, > you presumably already have an xml parser (doesn't jdk 1.4 include > one, or does it just have the interfaces?), and having the test file > be xml allows yoo to filter and process it - perhaps using xquery. I believe it's all too common to use XML just for the sake of using XML. That's especially true for technologies related in some way to XML. In this situation, looking at the plusses and minuses, we see XML as a more difficult format to author in, and the primary goal here is to author tests. We should remove as many burdens as we can toward that goal. Side note: It's especially difficult to author tests in XML not just because XML is more verbose, but because the query and result contents themselves use XML. Thus the tests would have to be escaped or in CDATA sections, and neither of those solutions is human friendly. What's more, when the query or result use CDATA sections themselves, then it gets extremely difficult to decipher what's what. > Why do you require jdk 1.4 to run bumblebee? What features do > you need not in earlier jdks? Have you tried gcj or kaffe? The Saxon engine and the Cerisent adapter both require JDK 1.4. JDK 1.4 has been out for several years and has been widely ported, and using JDK 1.4 makes XML work much more reliable (no need to shuffle JARs), so we thought it natural to set JDK 1.4 as the current minimum level. We could change that, but it would require discussions with a customer having that need. > Why do you use JAVA_HOME? It seems you only use it to get > the java executable. Why not just use a $JAVA variable, > which defaults to the java in PATH? That seems more portable, > given that JAVA_HOME isn't even a Sun standard. JAVA_HOME seems the most widely used name for this type of variable. I remember seeing it even back in 1996. Just looking at my current code bases I see it used by Ant, Tomcat, JDOM, and Xindice. > Have you written any adapters to XQuery implementations that > are *not* Java-based? I see hints of it - the manual implies > the cerisent adapter connects over the network. The Cerisent and Ipedo adapters connect over the network. Cerisent is not written in Java. Thanks for the feedback! -jh- From ktegels@msn.com Wed Oct 15 10:40:07 2003 Received: from hotmail.com (bay5-dav120.bay5.hotmail.com [65.54.173.150]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9FHe6ZK018727 for ; Wed, 15 Oct 2003 10:40:06 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 15 Oct 2003 10:41:56 -0700 Received: from 63.165.129.137 by bay5-dav120.bay5.hotmail.com with DAV; Wed, 15 Oct 2003 17:41:56 +0000 X-Originating-IP: [63.165.129.137] X-Originating-Email: [ktegels@msn.com] From: "kent tegels" To: Subject: RE: [xquery-talk] XQuery Platform Support Date: Wed, 15 Oct 2003 12:41:56 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcOTOWhf2ynupWVfS8uIzhlJHURlVAACgsZA X-OriginalArrivalTime: 15 Oct 2003 17:41:56.0758 (UTC) FILETIME=[A0DF3360:01C39343] X-Mailman-Approved-At: Wed, 15 Oct 2003 18:23:43 -0700 Cc: john.zink@prudential.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 17:40:07 -0000 Without getting into the details due to NDA issues, I can say that SQL Server Yukon and version 1.2 of the .NET CLR will *likely* have support. kt -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Wednesday, October 15, 2003 10:53 AM To: talk@xquery.com Subject: [xquery-talk] XQuery Platform Support Does anyone know what platforms XQuery will be supported on ? Any plans to be supported on the mainframe ? _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From mhk@mhk.me.uk Wed Oct 15 18:49:31 2003 Received: from mail2.ksc.th.com (mail2.ksc.th.com [203.155.0.233]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9G1nTZK024265; Wed, 15 Oct 2003 18:49:30 -0700 Received: from pcukmka ([203.155.16.163]) by mail2.ksc.th.com (8.12.1/8.12.0) with ESMTP id h9G1mCfE005314; Thu, 16 Oct 2003 08:48:17 +0700 From: "Michael Kay" To: "'Jason Hunter'" , "'Sander Bos'" Subject: RE: [xquery-talk] BumbleBee XQuery Test Harness Date: Thu, 16 Oct 2003 02:55:41 +0100 Message-ID: <003001c39388$a08fa670$6900000a@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <3F8DB776.3050505@xquery.com> Importance: Normal Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 01:49:31 -0000 > Yes, some vendors serialize an xs:double without the .0 but > http://www.w3.org/TR/xmlschema-2/#double says this is > incorrect and the > .0 is necessary. In the 1.0.1 release we updated a few test results > accordingly. We've had great difficulty getting everyone to agree on the rules for converting doubles to strings, partly because it's hard to get people to focus their attention on something so trivial. In Saxon, I have stuck to the XPath 1.0 rules until now, partly because I didn't feel that the 2.0 rules were stable yet and partly because they are unusable (e.g. in XSLT, chapters numbered 2.0e0). The WGs have now agreed the rules and they will appear in the next versions of the specs. In rough terms, the output will follow the XPath 1.0 rules for numbers in the range 1e-6 to 1e+6, but will use exponential notation outside that range. Michael Kay From seanj@xyke.com Wed Oct 15 19:00:47 2003 Received: from xyke.com (sense-ah72d-163.oz.net [216.39.164.163]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9G20lZK024470 for ; Wed, 15 Oct 2003 19:00:47 -0700 Received: by xyke.com (Postfix, from userid 1003) id 1CF75214; Wed, 15 Oct 2003 19:07:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by chronotechnic.com (Postfix) with ESMTP id 18838212; Wed, 15 Oct 2003 19:07:01 -0700 (PDT) Date: Wed, 15 Oct 2003 19:07:01 -0700 (PDT) From: seanj X-X-Sender: seanj@chronotechnic.com To: talk@xquery.com Subject: RE: [xquery-talk] XQuery Platform Support In-Reply-To: Message-ID: <0310151859580.-3@example.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: john.zink@prudential.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 02:00:47 -0000 I think a better question would have been, "what platforms will XQuery not be supported on." Any platform with a C compiler (GCC), Java runtime or OCAML runtime will support XQuery. Sean. On Wed, 15 Oct 2003, kent tegels wrote: > Without getting into the details due to NDA issues, I can say that SQL > Server Yukon and version 1.2 of the .NET CLR will *likely* have support. > > kt > > -----Original Message----- > From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of > john.zink@prudential.com > Sent: Wednesday, October 15, 2003 10:53 AM > To: talk@xquery.com > Subject: [xquery-talk] XQuery Platform Support > > Does anyone know what platforms XQuery will be supported on ? > > Any plans to be supported on the mainframe ? > > > _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk > _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk > From jhunter@servlets.com Wed Oct 15 21:46:47 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9G4kkZK025855 for ; Wed, 15 Oct 2003 21:46:46 -0700 Received: from servlets.com ([192.168.1.44]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9G4shD9017333 for ; Wed, 15 Oct 2003 21:54:43 -0700 (PDT) Message-ID: <3F8E2403.5040609@servlets.com> Date: Wed, 15 Oct 2003 21:52:19 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Subject: Re: [xquery-talk] BumbleBee XQuery Test Harness References: <003001c39388$a08fa670$6900000a@pcukmka> In-Reply-To: <003001c39388$a08fa670$6900000a@pcukmka> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 04:46:47 -0000 Michael Kay wrote: >>Yes, some vendors serialize an xs:double without the .0 but >>http://www.w3.org/TR/xmlschema-2/#double says this is >>incorrect and the >>.0 is necessary. In the 1.0.1 release we updated a few test results >>accordingly. > > We've had great difficulty getting everyone to agree on the rules for > converting doubles to strings, partly because it's hard to get people to > focus their attention on something so trivial. In Saxon, I have stuck to > the XPath 1.0 rules until now, partly because I didn't feel that the 2.0 > rules were stable yet and partly because they are unusable (e.g. in > XSLT, chapters numbered 2.0e0). The WGs have now agreed the rules and > they will appear in the next versions of the specs. In rough terms, the > output will follow the XPath 1.0 rules for numbers in the range 1e-6 to > 1e+6, but will use exponential notation outside that range. Thanks for the clarification! Here's the pertinent section from http://www.w3.org/TR/xpath: "otherwise, the number is represented in decimal form as a Number including a decimal point with at least one digit before the decimal point and at least one digit after the decimal point, preceded by a minus sign (-) if the number is negative; there must be no leading zeros before the decimal point apart possibly from the one required digit immediately before the decimal point; beyond the one required digit after the decimal point there must be as many, but only as many, more digits as are needed to uniquely distinguish the number from all other IEEE 754 numeric values." -jh- From sander@x-hive.com Thu Oct 16 01:23:19 2003 Received: from x-hive.com (a194-109-160-206.adsl.xs4all.nl [194.109.160.206]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9G8NIZK027628 for ; Thu, 16 Oct 2003 01:23:18 -0700 content-class: urn:content-classes:message Subject: RE: [xquery-talk] BumbleBee XQuery Test Harness Date: Thu, 16 Oct 2003 10:30:10 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C393BF.B634A699" Message-ID: <41D11F414A26E942912B7E7696DC8E228482A0@JAKARTA.xhive.archipel> X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 X-MS-TNEF-Correlator: Thread-Topic: [xquery-talk] BumbleBee XQuery Test Harness Thread-Index: AcOTv7Y0P3thyUr3RTCCKyQDCkWybQ== From: "Sander Bos" To: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 08:23:19 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C393BF.B634A699 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear Jason, > > I think we produce the result in the right way, so surrounded by a > > results element? But BumbleBee does not like it. >=20 > Yes, you are correct. That also is fixed in 1.0.1. 'fraid not, it just went from 596 such errors to 546, e.g. Query:=20 {xdt:yearMonthDuration("P0Y0M") * xs:decimal("-99999999999999999999")} Actual Result:=20 P0M Expected Possible Result 1:=20 P0M Failure Message 1:=20 Expected node type '3' but was '1' - comparing P0M at /BumbleBee_Result[1]/text()[1] to at /BumbleBee_Result[1]/results[1] Because of these errors, is it reasonable to assume that none of the products you wrote adapters for currently have a close to 100% score on all the tests? Your other changes helped quite a bit. We now have an 83.3% (*) score on the usecases tests (I may as well say it as I attach an Adapter for X-Hive/DB). We have failures in Strong.bee because we do not implement import schema yet, and errors in R.bee that we have to look into further. I attached my adapter implementation for X-Hive/DB as indicated that I would yesterday, maybe it can be useful to others. Kind regards, --Sander. *) with doc -> document rewrite in adapter and adjustment of declarations in queries to latest spec. ------_=_NextPart_001_01C393BF.B634A699 Content-Type: application/octet-stream; name="XhiveAdapter.java" Content-Transfer-Encoding: base64 Content-Description: XhiveAdapter.java Content-Disposition: attachment; filename="XhiveAdapter.java" cGFja2FnZSBidW1ibGViZWUuYWRhcHRlcnM7DQoNCmltcG9ydCBidW1ibGViZWUuQWRhcHRlcjsN CmltcG9ydCBidW1ibGViZWUuQWRhcHRlckV4Y2VwdGlvbjsNCmltcG9ydCBjb20ueGhpdmUuWGhp dmVEcml2ZXJGYWN0b3J5Ow0KaW1wb3J0IGNvbS54aGl2ZS5jb3JlLmludGVyZmFjZXMuWGhpdmVE cml2ZXJJZjsNCmltcG9ydCBjb20ueGhpdmUuY29yZS5pbnRlcmZhY2VzLlhoaXZlU2Vzc2lvbklm Ow0KaW1wb3J0IGNvbS54aGl2ZS5kb20uaW50ZXJmYWNlcy5YaGl2ZURvY3VtZW50SWY7DQppbXBv cnQgY29tLnhoaXZlLmRvbS5pbnRlcmZhY2VzLlhoaXZlTGlicmFyeUlmOw0KaW1wb3J0IGNvbS54 aGl2ZS5xdWVyeS5pbnRlcmZhY2VzLlhoaXZlWFF1ZXJ5VmFsdWVJZjsNCmltcG9ydCBvcmcudzNj LmRvbS54aGl2ZWxzLkRPTUJ1aWxkZXI7DQppbXBvcnQgb3JnLnczYy5kb20ueGhpdmVscy5ET01J bnB1dFNvdXJjZTsNCmltcG9ydCBvcmcudzNjLmRvbS54aGl2ZWxzLkRPTVdyaXRlcjsNCg0KaW1w b3J0IGphdmEuaW8uRmlsZUlucHV0U3RyZWFtOw0KaW1wb3J0IGphdmEudXRpbC5JdGVyYXRvcjsN CmltcG9ydCBqYXZhLnV0aWwuUHJvcGVydGllczsNCmltcG9ydCBqYXZhLnV0aWwuU3RhY2s7DQpp bXBvcnQgamF2YS51dGlsLlN0cmluZ1Rva2VuaXplcjsNCmltcG9ydCBqYXZhLnV0aWwucmVnZXgu TWF0Y2hlcjsNCmltcG9ydCBqYXZhLnV0aWwucmVnZXguUGF0dGVybjsNCg0KcHVibGljIGNsYXNz IFhoaXZlQWRhcHRlciBpbXBsZW1lbnRzIEFkYXB0ZXIgew0KDQogIC8vIFByb3BlcnRpZXMgd2l0 aCBkZWZhdWx0cywgaWYgbm9uZSBzcGVjZmllZCBpbiBjb25maWcgZmlsZQ0KICBwcml2YXRlIFN0 cmluZyBCT09UU1RSQVBfTE9DQVRJT04gPSAieGhpdmU6Ly9sb2NhbGhvc3Q6MTIzNSI7DQogIHBy aXZhdGUgU3RyaW5nIERBVEFCQVNFX05BTUUgPSAiTXlEYXRhYmFzZSI7DQogIHByaXZhdGUgU3Ry aW5nIFVTRVJfTkFNRSA9ICJBZG1pbmlzdHJhdG9yIjsNCiAgcHJpdmF0ZSBTdHJpbmcgVVNFUl9Q QVNTV09SRCA9ICJzZWNyZXQiOw0KDQogIHByaXZhdGUgU3RhY2sgc2Vzc2lvbnM7DQogIHByaXZh dGUgRE9NV3JpdGVyIHdyaXRlcjsNCg0KICBwdWJsaWMgWGhpdmVBZGFwdGVyKFByb3BlcnRpZXMg cHJvcGVydGllcykgew0KICAgIHRoaXMuc2Vzc2lvbnMgPSBuZXcgU3RhY2soKTsNCiAgICBCT09U U1RSQVBfTE9DQVRJT04gPSBzZXRQcm9wZXJ0eShwcm9wZXJ0aWVzLCAieGhpdmUuYm9vdHN0cmFw IiwgQk9PVFNUUkFQX0xPQ0FUSU9OKTsNCiAgICBEQVRBQkFTRV9OQU1FID0gc2V0UHJvcGVydHko cHJvcGVydGllcywgInhoaXZlLmRhdGFiYXNlbmFtZSIsIERBVEFCQVNFX05BTUUpOw0KICAgIFVT RVJfTkFNRSA9IHNldFByb3BlcnR5KHByb3BlcnRpZXMsICJ4aGl2ZS51c2VybmFtZSIsIFVTRVJf TkFNRSk7DQogICAgVVNFUl9QQVNTV09SRCA9IHNldFByb3BlcnR5KHByb3BlcnRpZXMsICJ4aGl2 ZS5wYXNzd29yZCIsIFVTRVJfUEFTU1dPUkQpOw0KICB9DQoNCiAgLyoNCiAgICogSW50ZXJmYWNl IGltcGxlbWVudGF0aW9uDQogICAqLw0KDQogIHB1YmxpYyB2b2lkIGxvYWQoU3RyaW5nIHVyaSkg dGhyb3dzIEFkYXB0ZXJFeGNlcHRpb24gew0KICAgIGRlYnVnKCJ1cmkgPSAiICsgdXJpKTsNCiAg ICBpZiAodXJpLmluZGV4T2YoJy8nKSA9PSAtMSkgew0KICAgICAgdGhyb3cgbmV3IEFkYXB0ZXJF eGNlcHRpb24oIlRoaXMgSSBkaWQgbm90IGV4cGVjdCwgYSBwYXRoIHdpdGhvdXQgLydzIik7DQog ICAgfQ0KDQogICAgWGhpdmVTZXNzaW9uSWYgc2Vzc2lvbiA9IGdldFNlc3Npb24oKTsNCiAgICB0 cnkgew0KICAgICAgc2Vzc2lvbi5iZWdpbigpOw0KICAgICAgWGhpdmVMaWJyYXJ5SWYgcm9vdExp YiA9IHNlc3Npb24uZ2V0RGF0YWJhc2UoKS5nZXRSb290KCk7DQoNCiAgICAgIC8vIENyZWF0ZSBs aWJyYXJpZXMgaWYgbmVjZXNzYXJ5DQogICAgICBYaGl2ZUxpYnJhcnlJZiB0YXJnZXRMaWIgPSBt a0xpYnMocm9vdExpYiwgdXJpKTsNCg0KICAgICAgLy8gUmVtb3ZlIGV4aXN0aW5nIGRvY3VtZW50 IGlmIGF2YWlsYWJsZQ0KICAgICAgU3RyaW5nIGRvY05hbWUgPSB1cmkuc3Vic3RyaW5nKHVyaS5s YXN0SW5kZXhPZignLycpICsgMSk7DQogICAgICBpZiAodGFyZ2V0TGliLm5hbWVFeGlzdHMoZG9j TmFtZSkpIHsNCiAgICAgICAgdGFyZ2V0TGliLnJlbW92ZUNoaWxkKHRhcmdldExpYi5nZXQoZG9j TmFtZSkpOw0KICAgICAgfQ0KDQogICAgICAvLyBMb2FkIG5ldyBkb2N1bWVudA0KICAgICAgRmls ZUlucHV0U3RyZWFtIGZpcyA9IG5ldyBGaWxlSW5wdXRTdHJlYW0odXJpKTsNCiAgICAgIERPTUJ1 aWxkZXIgYnVpbGRlciA9IHRhcmdldExpYi5jcmVhdGVET01CdWlsZGVyKCk7DQogICAgICBET01J bnB1dFNvdXJjZSBpcyA9IHRhcmdldExpYi5jcmVhdGVET01JbnB1dFNvdXJjZSgpOw0KICAgICAg aXMuc2V0Qnl0ZVN0cmVhbShmaXMpOw0KICAgICAgaXMuc2V0U3lzdGVtSWQodXJpKTsNCiAgICAg IFhoaXZlRG9jdW1lbnRJZiBuZXdEb2MgPSAoWGhpdmVEb2N1bWVudElmKSBidWlsZGVyLnBhcnNl KGlzKTsNCiAgICAgIG5ld0RvYy5zZXROYW1lKGRvY05hbWUpOw0KICAgICAgdGFyZ2V0TGliLmFw cGVuZENoaWxkKG5ld0RvYyk7DQogICAgICAvLyBJZiBwYXJzaW5nIGZhaWxzIGZpcyB3b24ndCBi ZSBjbG9zZWQsIG5vIGJpZ2dpZQ0KICAgICAgZmlzLmNsb3NlKCk7DQoNCiAgICAgIHNlc3Npb24u Y29tbWl0KCk7DQogICAgfSBjYXRjaCAoRXhjZXB0aW9uIGV4Y2VwdGlvbikgew0KICAgICAgdGhy b3cgbmV3IEFkYXB0ZXJFeGNlcHRpb24oZXhjZXB0aW9uLmdldE1lc3NhZ2UoKSwgZXhjZXB0aW9u KTsNCiAgICB9IGZpbmFsbHkgew0KICAgICAgcmVsZWFzZVNlc3Npb24oc2Vzc2lvbik7DQogICAg fQ0KICB9DQoNCiAgcHVibGljIFN0cmluZyBldmFsdWF0ZShTdHJpbmcgcXVlcnkpIHRocm93cyBB ZGFwdGVyRXhjZXB0aW9uIHsNCiAgICBxdWVyeSA9IGFsdGVyUXVlcnkocXVlcnkpOw0KICAgIGRl YnVnKHF1ZXJ5KTsNCiAgICBTdHJpbmdCdWZmZXIgcmVzdWx0U3RyaW5nID0gbmV3IFN0cmluZ0J1 ZmZlcigpOw0KICAgIFhoaXZlU2Vzc2lvbklmIHNlc3Npb24gPSBnZXRTZXNzaW9uKCk7DQogICAg dHJ5IHsNCiAgICAgIHNlc3Npb24uYmVnaW4oKTsNCiAgICAgIFhoaXZlTGlicmFyeUlmIHJvb3RM aWIgPSBzZXNzaW9uLmdldERhdGFiYXNlKCkuZ2V0Um9vdCgpOw0KICAgICAgaW5pdFdyaXRlcihy b290TGliKTsNCiAgICAgIEl0ZXJhdG9yIHJlc3VsdHMgPSByb290TGliLmV4ZWN1dGVYUXVlcnko cXVlcnkpOw0KICAgICAgd2hpbGUgKHJlc3VsdHMuaGFzTmV4dCgpKSB7DQogICAgICAgIFhoaXZl WFF1ZXJ5VmFsdWVJZiByZXN1bHQgPSAoWGhpdmVYUXVlcnlWYWx1ZUlmKSByZXN1bHRzLm5leHQo KTsNCiAgICAgICAgcmVzdWx0U3RyaW5nLmFwcGVuZChzZXJpYWxpemUocmVzdWx0KSk7DQogICAg ICB9DQogICAgICBzZXNzaW9uLmNvbW1pdCgpOw0KICAgIH0gY2F0Y2ggKEV4Y2VwdGlvbiBleGNl cHRpb24pIHsNCiAgICAgIHRocm93IG5ldyBBZGFwdGVyRXhjZXB0aW9uKGV4Y2VwdGlvbi5nZXRN ZXNzYWdlKCksIGV4Y2VwdGlvbik7DQogICAgfSBmaW5hbGx5IHsNCiAgICAgIHJlbGVhc2VTZXNz aW9uKHNlc3Npb24pOw0KICAgIH0NCiAgICByZXR1cm4gcmVzdWx0U3RyaW5nLnRvU3RyaW5nKCk7 DQogIH0NCg0KICAvKg0KICAgKiBTZXNzaW9uIHBvb2xpbmcNCiAgICovDQoNCiAgcHJpdmF0ZSBz eW5jaHJvbml6ZWQgWGhpdmVTZXNzaW9uSWYgZ2V0U2Vzc2lvbigpIHsNCiAgICBYaGl2ZVNlc3Np b25JZiBzZXNzaW9uOw0KICAgIGlmIChzZXNzaW9ucy5pc0VtcHR5KCkpIHsNCiAgICAgIC8vIENy ZWF0ZSBuZXcgc2Vzc2lvbg0KICAgICAgWGhpdmVEcml2ZXJJZiBkcml2ZXIgPSBYaGl2ZURyaXZl ckZhY3RvcnkuZ2V0RHJpdmVyKEJPT1RTVFJBUF9MT0NBVElPTik7DQogICAgICBpZiAoIWRyaXZl ci5pc0luaXRpYWxpemVkKCkpIHsNCiAgICAgICAgZHJpdmVyLmluaXQoMTAyNCk7DQogICAgICB9 DQogICAgICBzZXNzaW9uID0gZHJpdmVyLmNyZWF0ZVNlc3Npb24oKTsNCiAgICAgIHNlc3Npb24u Y29ubmVjdChVU0VSX05BTUUsIFVTRVJfUEFTU1dPUkQsIERBVEFCQVNFX05BTUUpOw0KICAgIH0g ZWxzZSB7DQogICAgICAvLyBHZXQgc2Vzc2lvbiBmcm9tIHBvb2wNCiAgICAgIHNlc3Npb24gPSAo WGhpdmVTZXNzaW9uSWYpIHNlc3Npb25zLnBvcCgpOw0KICAgICAgc2Vzc2lvbi5qb2luKCk7DQog ICAgfQ0KICAgIHJldHVybiBzZXNzaW9uOw0KICB9DQoNCiAgcHJpdmF0ZSBzeW5jaHJvbml6ZWQg dm9pZCByZWxlYXNlU2Vzc2lvbihYaGl2ZVNlc3Npb25JZiBzZXNzaW9uKSB7DQogICAgaWYgKHNl c3Npb24uaXNPcGVuKCkpIHsNCiAgICAgIHNlc3Npb24ucm9sbGJhY2soKTsNCiAgICB9DQogICAg aWYgKHNlc3Npb24uaXNKb2luZWQoKSkgew0KICAgICAgc2Vzc2lvbi5sZWF2ZSgpOw0KICAgIH0N CiAgICBzZXNzaW9ucy5wdXNoKHNlc3Npb24pOw0KICB9DQoNCiAgLyoNCiAgICogVXRpbGl0eSBm dW5jdGlvbnMNCiAgICovDQoNCiAgcHJpdmF0ZSBTdHJpbmcgc2V0UHJvcGVydHkoUHJvcGVydGll cyBwcm9wZXJ0aWVzLCBTdHJpbmcgcHJvcGVydHlOYW1lLCBTdHJpbmcgZGVmYXVsdFZhbHVlKSB7 DQogICAgaWYgKHByb3BlcnRpZXMgIT0gbnVsbCkgew0KICAgICAgcmV0dXJuIHByb3BlcnRpZXMu Z2V0UHJvcGVydHkocHJvcGVydHlOYW1lLCBkZWZhdWx0VmFsdWUpOw0KICAgIH0gZWxzZSB7DQog ICAgICByZXR1cm4gZGVmYXVsdFZhbHVlOw0KICAgIH0NCiAgfQ0KDQogIHByaXZhdGUgdm9pZCBp bml0V3JpdGVyKFhoaXZlTGlicmFyeUlmIHJvb3RMaWIpIHsNCiAgICBpZiAod3JpdGVyID09IG51 bGwpIHsNCiAgICAgIHdyaXRlciA9IHJvb3RMaWIuY3JlYXRlRE9NV3JpdGVyKCk7DQogICAgfQ0K ICB9DQoNCiAgLyoqDQogICAqIENyZWF0ZSBsaWJyYXJpZXMgaWYgbm90IGFscmVhZHkgdGhlcmUN CiAgICovDQogIHByaXZhdGUgWGhpdmVMaWJyYXJ5SWYgbWtMaWJzKFhoaXZlTGlicmFyeUlmIGJh c2VMaWIsIFN0cmluZyB1cmkpIHsNCiAgICBYaGl2ZUxpYnJhcnlJZiBjdXJyZW50TGliID0gYmFz ZUxpYjsNCiAgICBTdHJpbmcgbGliUGF0aCA9IHVyaS5zdWJzdHJpbmcoMCwgdXJpLmxhc3RJbmRl eE9mKCcvJykpOw0KICAgIFN0cmluZ1Rva2VuaXplciBsaWJTdGVwcyA9IG5ldyBTdHJpbmdUb2tl bml6ZXIobGliUGF0aCwgIi8iKTsNCiAgICB3aGlsZSAobGliU3RlcHMuaGFzTW9yZVRva2Vucygp KSB7DQogICAgICBTdHJpbmcgcGF0aFN0ZXAgPSBsaWJTdGVwcy5uZXh0VG9rZW4oKTsNCiAgICAg IGlmICghY3VycmVudExpYi5uYW1lRXhpc3RzKHBhdGhTdGVwKSkgew0KICAgICAgICBYaGl2ZUxp YnJhcnlJZiBuZXdMaWIgPSBjdXJyZW50TGliLmNyZWF0ZUxpYnJhcnkoKTsNCiAgICAgICAgbmV3 TGliLnNldE5hbWUocGF0aFN0ZXApOw0KICAgICAgICBjdXJyZW50TGliLmFwcGVuZENoaWxkKG5l d0xpYik7DQogICAgICB9DQogICAgICBjdXJyZW50TGliID0gKFhoaXZlTGlicmFyeUlmKSBjdXJy ZW50TGliLmdldChwYXRoU3RlcCk7DQogICAgfQ0KICAgIHJldHVybiBjdXJyZW50TGliOw0KICB9 DQoNCiAgLyoqDQogICAqIENyZWF0ZSBTdHJpbmcgZnJvbSBvbmUgcmVzdWx0IGVudHJ5LCBhbGxv dyBmb3IgTm9kZSBzZXJpYWxpemF0aW9uIG9wdGlvbnMuDQogICAqLw0KICBwcml2YXRlIFN0cmlu ZyBzZXJpYWxpemUoWGhpdmVYUXVlcnlWYWx1ZUlmIHJlc3VsdCkgew0KICAgIFN0cmluZyByZXN1 bHRTdHJpbmc7DQogICAgaWYgKHJlc3VsdC5pc05vZGUoKSkgew0KICAgICAgLy8gTWFzc2FnZSBy ZXN1bHQgYXMgQnVtYmxlYmVlIGV4cGVjdHMNCiAgICAgIHdyaXRlci5nZXRDb25maWcoKS5zZXRQ YXJhbWV0ZXIoIm5hbWVzcGFjZXMiLCBCb29sZWFuLlRSVUUpOyAvLyBuYW1lc3BhY2UgZml4dXAN CiAgICAgIHdyaXRlci5nZXRDb25maWcoKS5zZXRQYXJhbWV0ZXIoImRpc2NhcmQtZGVmYXVsdC1j b250ZW50IiwgQm9vbGVhbi5GQUxTRSk7IC8vIHJlbW92ZSBkZWZhdWx0IGF0dHJpYnV0ZXMNCiAg ICAgIHJlc3VsdFN0cmluZyA9IHdyaXRlci53cml0ZVRvU3RyaW5nKHJlc3VsdC5hc05vZGUoKSk7 DQogICAgfSBlbHNlIHsNCiAgICAgIC8vIERlZmF1bHQNCiAgICAgIHJlc3VsdFN0cmluZyA9IHJl c3VsdC50b1N0cmluZygpOw0KICAgIH0NCiAgICByZXR1cm4gcmVzdWx0U3RyaW5nOw0KICB9DQoN CiAgLyoqDQogICAqIFgtSGl2ZS9EQiA1LjAuMSBkb2VzIG5vdCBoYXZlIGEgZG9jIGZ1bmN0aW9u IG1pc3Rha2VubHksIGFuZCBkb2VzIG5vdCBhbGxvdyBmb3INCiAgICogcmVsYXRpdmUgcGF0aHMs IHNvIGhhY2sgdG8gcmV3cml0ZSBtb3N0IHF1ZXJpZXMuDQogICAqLw0KICBwcml2YXRlIFN0cmlu ZyBhbHRlclF1ZXJ5KFN0cmluZyBxdWVyeSkgew0KICAgIHF1ZXJ5ID0gcmVwbGFjZShxdWVyeSwg ImRvY1xcKCciLCAiZG9jdW1lbnQoJy8iKTsNCiAgICBxdWVyeSA9IHJlcGxhY2UocXVlcnksICJk b2NcXChcIiIsICJkb2N1bWVudChcIi8iKTsNCiAgICByZXR1cm4gcXVlcnk7DQogIH0NCg0KICBw cml2YXRlIFN0cmluZyByZXBsYWNlKFN0cmluZyBpbnB1dCwgU3RyaW5nIGZyb20sIFN0cmluZyB0 bykgew0KICAgIFBhdHRlcm4gcGF0dGVybiA9IFBhdHRlcm4uY29tcGlsZShmcm9tKTsNCiAgICBN YXRjaGVyIG1hdGNoZXIgPSBwYXR0ZXJuLm1hdGNoZXIoaW5wdXQpOw0KICAgIHJldHVybiBtYXRj aGVyLnJlcGxhY2VBbGwodG8pOw0KICB9DQoNCiAgcHJpdmF0ZSB2b2lkIGRlYnVnKFN0cmluZyBz KSB7DQovLyAgICBTeXN0ZW0ub3V0LnByaW50bG4oIltERUJVR10gIiArIHMpOw0KICB9DQp9DQo= ------_=_NextPart_001_01C393BF.B634A699-- From jeni@jenitennison.com Thu Oct 16 03:46:42 2003 Received: from yankee.rb.xcalibre.co.uk (yankee.rb.xcalibre.co.uk [217.8.240.35]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9GAkfZK028927 for ; Thu, 16 Oct 2003 03:46:42 -0700 Envelope-to: talk@xquery.com Received: from [213.104.74.52] (helo=chokmah) by yankee.rb.xcalibre.co.uk with esmtp (Exim 3.33 #4) id 1AA5lc-0004IU-00; Thu, 16 Oct 2003 10:54:04 +0000 Date: Thu, 16 Oct 2003 11:53:58 +0100 From: Jeni Tennison X-Mailer: The Bat! (v1.62i) Business Organization: Jeni Tennison Consulting Ltd X-Priority: 3 (Normal) Message-ID: <1691632577131.20031016115358@jenitennison.com> To: Jason Hunter Subject: Re: [xquery-talk] BumbleBee XQuery Test Harness In-Reply-To: <3F8E2403.5040609@servlets.com> References: <003001c39388$a08fa670$6900000a@pcukmka> <3F8E2403.5040609@servlets.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list Reply-To: Jeni Tennison List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 10:46:43 -0000 Jason Hunter wrote: > Michael Kay wrote: >> We've had great difficulty getting everyone to agree on the rules >> for converting doubles to strings, partly because it's hard to get >> people to focus their attention on something so trivial. In Saxon, >> I have stuck to the XPath 1.0 rules until now, partly because I >> didn't feel that the 2.0 rules were stable yet and partly because >> they are unusable (e.g. in XSLT, chapters numbered 2.0e0). The WGs >> have now agreed the rules and they will appear in the next versions >> of the specs. In rough terms, the output will follow the XPath 1.0 >> rules for numbers in the range 1e-6 to 1e+6, but will use >> exponential notation outside that range. > > Thanks for the clarification! Here's the pertinent section from > http://www.w3.org/TR/xpath: > > "otherwise, the number is represented in decimal form as a Number > including a decimal point with at least one digit before the decimal > point and at least one digit after the decimal point, preceded by a > minus sign (-) if the number is negative; there must be no leading zeros > before the decimal point apart possibly from the one required digit > immediately before the decimal point; beyond the one required digit > after the decimal point there must be as many, but only as many, more > digits as are needed to uniquely distinguish the number from all other > IEEE 754 numeric values." Don't forget the additional rules: - NaN is converted to the string NaN - positive zero is converted to the string 0 - negative zero is converted to the string 0 - positive infinity is converted to the string Infinity (I guess this will be INF in XPath 2.0) - negative infinity is converted to the string -Infinity (I guess this will be -INF in XPath 2.0) - if the number is an integer, the number is represented in decimal form as a Number with no decimal point and no leading zeros, preceded by a minus sign (-) if the number is negative The last is particularly important: if the value is an integer (i.e. it has no significant decimal digits), then it's formatted as an integer, without a trailing ".0". The exact URL is: http://www.w3.org/TR/xpath#function-string Cheers, Jeni --- Jeni Tennison http://www.jenitennison.com/ From john.zink@prudential.com Thu Oct 16 06:10:51 2003 Received: from pa-mailgate2.prudential.com (ny-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9GDApZK030304 for ; Thu, 16 Oct 2003 06:10:51 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h9GD7AdZ022404; Thu, 16 Oct 2003 09:07:11 -0400 (EDT) Subject: RE: [xquery-talk] XQuery Platform Support To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: john.zink@prudential.com Date: Thu, 16 Oct 2003 09:07:05 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/16/2003 09:07:11 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Cc: ktegels@msn.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 13:10:51 -0000 Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. "kent tegels" To: cc: Wednesday October 15, 2003 03:57 PM Subject: RE: [xquery-talk] XQuery Platform Support What MainFrame OS are you running? Are you in the Yukon beta? Thousand more questions for you :) kt -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Wednesday, October 15, 2003 2:22 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support I actually have a program up and running that is using the .Net demo version of the XQuery classes. I need to know the future of XQuery on the mainframe and here is why. I have .Net server programming running that is generating XQuery statements as part of a rules engine, but I also need the rules to run on the mainframe. If I can export the statements into a host program I'll be golden;otherwise, I will need to rethink my approach. thanks for your responses, John Z "kent tegels" To: cc: Wednesday October 15, 2003 01:41 PM Subject: RE: [xquery-talk] XQuery Platform Support Without getting into the details due to NDA issues, I can say that SQL Server Yukon and version 1.2 of the .NET CLR will *likely* have support. kt -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Wednesday, October 15, 2003 10:53 AM To: talk@xquery.com Subject: [xquery-talk] XQuery Platform Support Does anyone know what platforms XQuery will be supported on ? Any plans to be supported on the mainframe ? _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From jgovernor@redmonk.com Thu Oct 16 06:54:22 2003 Received: from fecls-03.atlarge.net (fecls-03.atlarge.net [129.41.63.139]) by jhunter.x-query.com (8.12.8/8.12.9) with SMTP id h9GDsMZK030658 for ; Thu, 16 Oct 2003 06:54:22 -0700 Received: from MAIL-04VS.atlarge.net ([129.41.63.191]) by fecls-03.atlarge.net with Microsoft SMTPSVC(5.0.2195.6713); Thu, 16 Oct 2003 08:48:31 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [xquery-talk] XQuery Platform Support Date: Thu, 16 Oct 2003 08:48:15 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [xquery-talk] XQuery Platform Support Thread-Index: AcOT6DXzHH6piPI4R6CV6yCVbm8GcgAAKtrw From: "James Governor" To: , X-OriginalArrivalTime: 16 Oct 2003 13:48:31.0335 (UTC) FILETIME=[2F66FF70:01C393EC] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by jhunter.x-query.com id h9GDsMZK030658 Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 13:54:23 -0000 I am not sure from your question exactly what scenario you're talking to. However it is worth noting that IBM this week acquired a mainframe data integration firm called CrossAccess, which was pitched as filling out its DB2 Information Integrator (II) strategy http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. From john.zink@prudential.com Thu Oct 16 07:27:58 2003 Received: from pa-mailgate2.prudential.com (pa-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9GERvZK031045 for ; Thu, 16 Oct 2003 07:27:58 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h9GESfdY021601 for ; Thu, 16 Oct 2003 10:28:41 -0400 (EDT) Subject: RE: [xquery-talk] XQuery Platform Support To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: john.zink@prudential.com Date: Thu, 16 Oct 2003 10:28:36 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/16/2003 10:28:40 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 14:27:58 -0000 OK..Let me see if I can explain it a bit clearer. We basically have 2 scenarios where a rules engine needs to be implemented. For our "new business" process I need an engine that examines application type questions and returns a result for the policy. The result can be either accept or reject the policy. The decision is made based upon a collection of rules. For example if you have 3 speeding tickets in the last month you will be declined. This engine has been created as I explained before. The new engine is replacing COM components that have all the rules hard coded in the form of "IF-THEN-ELSE" statements. The user can now create the rules based on a schema that describes the message the client will pass to the engine. The engine takes the rules entered by the user and converts them to XQuery expressions. The engine than runs the XQuery expressions against the XML being passed from the client to determine the result for the policy (hold or accept). The second scenario is we have another engine running on the mainframe that processes policies when they renew on a yearly basis. This engine is basically a COBOL program that processes a sequential input file and updates a VSAM file with the results. This engine processes thousands of records every night in a batch process. I would like to use the same client application for building the rules as I mentioned in the first scenario. I would then need a way to get a mainframe program that runs in a batch process to somehow process the XQuery statements. I believe it would be too slow to send mainframe records down to the server to run against the distributed engine. I only have a short window for the mainframe batch process. Hope this clarifies my situation. I've just started to examine the mainframe process so I haven't really formulated any real solutions for the mainframe side of the problem. John Z "James Governor" To: , cc: Thursday October 16, 2003 09:48 AM Subject: RE: [xquery-talk] XQuery Platform Support I am not sure from your question exactly what scenario you're talking to. However it is worth noting that IBM this week acquired a mainframe data integration firm called CrossAccess, which was pitched as filling out its DB2 Information Integrator (II) strategy http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. From jhunter@xquery.com Thu Oct 16 10:04:52 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9GH4qZK000421 for ; Thu, 16 Oct 2003 10:04:52 -0700 Received: from xquery.com ([192.168.1.44]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9GH8nD9022296; Thu, 16 Oct 2003 10:08:49 -0700 (PDT) Message-ID: <3F8ED00C.3080704@xquery.com> Date: Thu, 16 Oct 2003 10:06:20 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sander Bos Subject: Re: [xquery-talk] BumbleBee XQuery Test Harness References: <41D11F414A26E942912B7E7696DC8E228482A0@JAKARTA.xhive.archipel> In-Reply-To: <41D11F414A26E942912B7E7696DC8E228482A0@JAKARTA.xhive.archipel> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 17:04:53 -0000 Sander Bos wrote: >>>I think we produce the result in the right way, so surrounded by a >>>results element? But BumbleBee does not like it. >> >>Yes, you are correct. That also is fixed in 1.0.1. > > > 'fraid not, it just went from 596 such errors to 546, e.g. Alas. > Because of these errors, is it reasonable to assume that none of the > products you wrote adapters for currently have a close to 100% score on > all the tests? That would be a good guess, but actually the issue with these NIST tests is that they use numeric values exceeding the bounds that engines are required to support. That's why you see ERROR listed as one of two legal results. I don't recall finding an engine until now that both supported the arbitrarily sized numeric values and had a good understanding of the surrounding calls used by the NIST tests. Awkwardly the NIST tests themselves are just the queries, no results, so I had to write some of them in by hand. Your engine is better at calculating results than my hands. :-) I'm hoping Carmelo updates the NIST tests to have numeric values within the mandatory-to-support range. That'll make the NIST set of tests more interesting. > Your other changes helped quite a bit. We now have an 83.3% (*) score on > the usecases tests (I may as well say it as I attach an Adapter for > X-Hive/DB). We have failures in Strong.bee because we do not implement > import schema yet, and errors in R.bee that we have to look into > further. OK, great! > I attached my adapter implementation for X-Hive/DB as indicated that I > would yesterday, maybe it can be useful to others. Absolutely. -jh- From mhk@mhk.me.uk Thu Oct 16 12:23:55 2003 Received: from mail2.ksc.th.com (mail2.ksc.th.com [203.155.0.233]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9GJNsZK002124 for ; Thu, 16 Oct 2003 12:23:55 -0700 Received: from pcukmka ([203.155.16.163]) by mail2.ksc.th.com (8.12.1/8.12.0) with ESMTP id h9GJKeQX025267; Fri, 17 Oct 2003 02:20:41 +0700 From: "Michael Kay" To: , Subject: RE: [xquery-talk] XQuery Platform Support Date: Thu, 16 Oct 2003 20:28:09 +0100 Message-ID: <001c01c3941b$a322f1b0$6900000a@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 19:23:55 -0000 Surely, if this is a real application, you should be writing it in XSLT? Never mind the merits of the languages, surely a technology that has been stable for nearly four years is more appropriate to your needs than one that is still in beta? Michael Kay > -----Original Message----- > From: talk-bounces@xquery.com > [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com > Sent: 16 October 2003 15:29 > To: talk@xquery.com > Subject: RE: [xquery-talk] XQuery Platform Support > > > > OK..Let me see if I can explain it a bit clearer. > We basically have 2 scenarios where a rules engine needs to > be implemented. For our "new business" process I need an > engine that examines application type questions and returns a > result for the policy. The result can be either accept or > reject the policy. The decision is made based upon a > collection of rules. For example if you have 3 speeding > tickets in the last month you will be declined. This engine > has been created as I explained before. The new engine is > replacing COM components that have all the rules hard coded > in the form of "IF-THEN-ELSE" statements. The user can now > create the rules based on a schema that describes the message > the client will pass to the engine. The engine takes the > rules entered by the user and converts them to XQuery > expressions. The engine than runs the XQuery expressions > against the XML being passed from the client to > determine the result for the policy (hold or accept). The second > scenario is we have another engine running on the mainframe > that processes policies when they renew on a yearly basis. > This engine is basically a COBOL program that processes a > sequential input file and updates a VSAM file with the > results. This engine processes thousands of records every > night in a batch process. I would like to use the same > client application > for building the rules as I mentioned in the first scenario. > I would then need a way to get a mainframe program that runs > in a batch process to somehow process the XQuery statements. > I believe it would be too slow to send mainframe records down > to the server to run against the distributed > engine. I only have a short window for the mainframe batch > process. Hope > this clarifies my situation. I've just started to examine > the mainframe process so I haven't really formulated any real > solutions for the mainframe side of the problem. > > > John Z > > > > > > "James Governor" > > > To: > > , > > > > cc: > > > Thursday October 16, 2003 09:48 AM > Subject: RE: [xquery-talk] XQuery Platform Support > > > > > > > > > > > > I am not sure from your question exactly what scenario you're > talking to. > > However it is worth noting that IBM this week acquired a > mainframe data integration firm called CrossAccess, which was > pitched as filling out its DB2 Information Integrator (II) strategy > http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From lehti@ipsi.fhg.de Fri Oct 17 01:22:49 2003 Received: from sonne.sit.fraunhofer.de (sonne.sit.fraunhofer.de [141.12.62.20]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9H8MlZK008225 for ; Fri, 17 Oct 2003 01:22:48 -0700 Received: from pcspindle (pc-spindle [141.12.28.41]) by sonne.sit.fraunhofer.de (8.8.8/8.8.5) with ESMTP id KAA28906; Fri, 17 Oct 2003 10:30:13 +0200 (MET DST) From: "Patrick Lehti" To: "'Jason Hunter'" Subject: RE: [xquery-talk] BumbleBee XQuery Test Harness Date: Fri, 17 Oct 2003 10:29:09 +0200 Message-ID: <001501c39488$bd1ad020$291c0c8d@pcspindle> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <3F8ED00C.3080704@xquery.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: talk@x-query.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 08:22:49 -0000 > That would be a good guess, but actually the issue with these > NIST tests > is that they use numeric values exceeding the bounds that engines are > required to support. That's why you see ERROR listed as one of two > legal results. I don't recall finding an engine until now that both > supported the arbitrarily sized numeric values and had a good > understanding of the surrounding calls used by the NIST tests. So far as I see, ERROR is not one of two legal results, but the only legal result for all numeric functions using decimal, integer, nonPositiveInteger, nonNegativeInteger, positiveInteger and negativeInteger. This results in "passed" tests for all non- or minimal-conforming query engines and "failed" tests for conforming engines! This seems not to be fair and makes the (NIST)results unable to compare! If you need a tool to calculate the correct results for these tests, I suggest using IPSI-XQ, which supports decimal und integer values with arbitrary length since its very first release! ;-) Patrick From john.zink@prudential.com Fri Oct 17 06:45:46 2003 Received: from pa-mailgate2.prudential.com (ny-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9HDjjZK010484 for ; Fri, 17 Oct 2003 06:45:46 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h9HDkFdZ025858 for ; Fri, 17 Oct 2003 09:46:16 -0400 (EDT) Subject: RE: [xquery-talk] XQuery Platform Support To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: john.zink@prudential.com Date: Fri, 17 Oct 2003 09:46:13 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/17/2003 09:46:15 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 13:45:46 -0000 If I had to have this app out the door next week I would be using XSLT, but luckily it doesn't need to be completed until about 3rd QTR next year. In my opinion XQuery appears to be a bit more powerful with it's built in functions, ability to create user defined functions and it's SQL like FLWR expressions. I've never been a big fan of the XSLT syntax. "Michael Kay" To: , Thursday October 16, 2003 03:28 PM cc: Subject: RE: [xquery-talk] XQuery Platform Support Surely, if this is a real application, you should be writing it in XSLT? Never mind the merits of the languages, surely a technology that has been stable for nearly four years is more appropriate to your needs than one that is still in beta? Michael Kay > -----Original Message----- > From: talk-bounces@xquery.com > [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com > Sent: 16 October 2003 15:29 > To: talk@xquery.com > Subject: RE: [xquery-talk] XQuery Platform Support > > > > OK..Let me see if I can explain it a bit clearer. > We basically have 2 scenarios where a rules engine needs to > be implemented. For our "new business" process I need an > engine that examines application type questions and returns a > result for the policy. The result can be either accept or > reject the policy. The decision is made based upon a > collection of rules. For example if you have 3 speeding > tickets in the last month you will be declined. This engine > has been created as I explained before. The new engine is > replacing COM components that have all the rules hard coded > in the form of "IF-THEN-ELSE" statements. The user can now > create the rules based on a schema that describes the message > the client will pass to the engine. The engine takes the > rules entered by the user and converts them to XQuery > expressions. The engine than runs the XQuery expressions > against the XML being passed from the client to > determine the result for the policy (hold or accept). The second > scenario is we have another engine running on the mainframe > that processes policies when they renew on a yearly basis. > This engine is basically a COBOL program that processes a > sequential input file and updates a VSAM file with the > results. This engine processes thousands of records every > night in a batch process. I would like to use the same > client application > for building the rules as I mentioned in the first scenario. > I would then need a way to get a mainframe program that runs > in a batch process to somehow process the XQuery statements. > I believe it would be too slow to send mainframe records down > to the server to run against the distributed > engine. I only have a short window for the mainframe batch > process. Hope > this clarifies my situation. I've just started to examine > the mainframe process so I haven't really formulated any real > solutions for the mainframe side of the problem. > > > John Z > > > > > > "James Governor" > > > To: > > , > > > > cc: > > > Thursday October 16, 2003 09:48 AM > Subject: RE: [xquery-talk] XQuery Platform Support > > > > > > > > > > > > I am not sure from your question exactly what scenario you're > talking to. > > However it is worth noting that IBM this week acquired a > mainframe data integration firm called CrossAccess, which was > pitched as filling out its DB2 Information Integrator (II) strategy > http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From jhunter@xquery.com Fri Oct 17 13:13:28 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9HKDRZK014009 for ; Fri, 17 Oct 2003 13:13:28 -0700 Received: from xquery.com ([192.168.1.44]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9HKIoig010779; Fri, 17 Oct 2003 13:18:50 -0700 (PDT) Message-ID: <3F904DFB.1050604@xquery.com> Date: Fri, 17 Oct 2003 13:15:55 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Patrick Lehti Subject: Re: [xquery-talk] BumbleBee XQuery Test Harness References: <001501c39488$bd1ad020$291c0c8d@pcspindle> In-Reply-To: <001501c39488$bd1ad020$291c0c8d@pcspindle> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@x-query.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 20:13:28 -0000 Patrick Lehti wrote: > So far as I see, ERROR is not one of two legal results, but the only > legal result for all numeric functions using decimal, integer, > nonPositiveInteger, nonNegativeInteger, positiveInteger and > negativeInteger. This results in "passed" tests for all non- or > minimal-conforming query engines and "failed" tests for conforming > engines! This seems not to be fair and makes the (NIST)results unable to > compare! > > If you need a tool to calculate the correct results for these tests, I > suggest using IPSI-XQ, which supports decimal und integer values with > arbitrary length since its very first release! ;-) Yes, we've been working to add correct answers by hand for the next release, and there's no joy in that mudville. Automated population is the goal, and I hope IPSI-XQ and X-Hive provide help here because both support arbitrarily large numbers, but the behavior for numeric serialization seems to vary quite a lot between the vendors so the correct numeric answer may be encoded incorrectly. To distinguish this requires a persistent element of human involvement. -jh- From Sullivan.Sean@menlolog.com Fri Oct 17 14:09:21 2003 Received: from ljcqs030.cnf.com (mail-cluster.cnf.com [63.230.177.41]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9HL9LZK014304 for ; Fri, 17 Oct 2003 14:09:21 -0700 Received: from cnfqs039.cnf.com (localhost [127.0.0.1]) by ljcqs030.cnf.com (Postfix) with ESMTP id DE9181439D8 for ; Fri, 17 Oct 2003 14:12:26 -0700 (PDT) Received: by cnfqs039.cnf.prod.cnf.com with Internet Mail Service (5.5.2653.19) id ; Fri, 17 Oct 2003 14:12:24 -0700 Message-ID: <462D5240F6F9154AB0F9B345A5F03E3E3A1B15@cnfqe029.cnf.prod.cnf.com> From: "Sullivan, Sean C - MWT" To: talk@x-query.com Date: Fri, 17 Oct 2003 14:12:22 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Cc: Subject: [xquery-talk] Microsoft's XQuery demo X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 21:09:21 -0000 Does Microsoft plan to support XQuery? I found Microsoft's demo site: http://xqueryservices.com/ http://xqueryservices.com/xqueryinfo.html -Sean From ktegels@msn.com Fri Oct 17 14:14:03 2003 Received: from hotmail.com (bay5-dav48.bay5.hotmail.com [65.54.173.78]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9HLE2ZK014340 for ; Fri, 17 Oct 2003 14:14:02 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 17 Oct 2003 14:17:14 -0700 Received: from 63.165.129.137 by bay5-dav48.bay5.hotmail.com with DAV; Fri, 17 Oct 2003 21:17:14 +0000 X-Originating-IP: [63.165.129.137] X-Originating-Email: [ktegels@msn.com] From: "kent tegels" To: "'Sullivan, Sean C - MWT'" Subject: RE: [xquery-talk] Microsoft's XQuery demo Date: Fri, 17 Oct 2003 16:17:14 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcOU83Nd5V7UFm0WQTiz7LXiLgaSQQAAF3iA In-Reply-To: <462D5240F6F9154AB0F9B345A5F03E3E3A1B15@cnfqe029.cnf.prod.cnf.com> X-OriginalArrivalTime: 17 Oct 2003 21:17:14.0822 (UTC) FILETIME=[0976D660:01C394F4] X-Mailman-Approved-At: Fri, 17 Oct 2003 14:24:07 -0700 Cc: talk@x-query.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 21:14:03 -0000 I can't speak for the company, but I can say that the are certainly *currently* Xquery features in the products to be introduced in the next 18 to 24 months. kt -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of Sullivan, Sean C - MWT Sent: Friday, October 17, 2003 4:12 PM To: talk@x-query.com Subject: [xquery-talk] Microsoft's XQuery demo Does Microsoft plan to support XQuery? I found Microsoft's demo site: http://xqueryservices.com/ http://xqueryservices.com/xqueryinfo.html -Sean _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From seanj@xyke.com Fri Oct 17 16:45:32 2003 Received: from xyke.com (sense-ah72d-163.oz.net [216.39.164.163]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9HNjWZK015746 for ; Fri, 17 Oct 2003 16:45:32 -0700 Received: by xyke.com (Postfix, from userid 1003) id 8B08E205; Fri, 17 Oct 2003 16:51:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by chronotechnic.com (Postfix) with ESMTP id 863E3D1; Fri, 17 Oct 2003 16:51:08 -0700 (PDT) Date: Fri, 17 Oct 2003 16:51:08 -0700 (PDT) From: seanj@xyke.com X-X-Sender: seanj@chronotechnic.com To: talk@x-query.com Subject: RE: [xquery-talk] Microsoft's XQuery demo In-Reply-To: Message-ID: <0310171642170.-3@example.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "'Sullivan, Sean C - MWT'" , ktegels@msn.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 23:45:33 -0000 Well the search "xquery site:microsoft.com" on google returns 203 hits. And I have second hand source information that says microsoft's favorite xml technology is xquery. And I am sure Kent has a Wrox book titled, "XQUERY programming with .NET" on the way. Sean. On Fri, 17 Oct 2003, kent tegels wrote: > I can't speak for the company, but I can say that the are certainly > *currently* Xquery features in the products to be introduced in the next 18 > to 24 months. > > kt > > -----Original Message----- > From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of > Sullivan, Sean C - MWT > Sent: Friday, October 17, 2003 4:12 PM > To: talk@x-query.com > Subject: [xquery-talk] Microsoft's XQuery demo > > > Does Microsoft plan to support XQuery? > > I found Microsoft's demo site: > > http://xqueryservices.com/ > > http://xqueryservices.com/xqueryinfo.html > > -Sean > > _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk > _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk > From xfranc@online.fr Sat Oct 18 03:21:01 2003 Received: from ns18.abergement.ch ([62.50.79.8]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9IAL0ZK019565 for ; Sat, 18 Oct 2003 03:21:00 -0700 Received: from online.fr (lns-th2-8-82-64-124-184.adsl.proxad.net [82.64.124.184]) (authenticated) by ns18.abergement.ch (8.11.6/8.11.6) with ESMTP id h9I8Imr10648 for ; Sat, 18 Oct 2003 10:18:48 +0200 Message-ID: <3F9115D1.4030204@online.fr> Date: Sat, 18 Oct 2003 12:28:33 +0200 From: Xavier Franc User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xquery-talk] issue in use-cases R X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Oct 2003 10:21:01 -0000 There is still an issue in "r" use-cases, that make results of queries Q6, Q7, Q10, Q11 irrelevant for most processors. It comes from the may 2003 use-cases and has been fixed in the latest version (aug 2003) the use of fn:max function on data of type xdt:untypedAtomic implies a string comparison (as far I as understand), but the expected results are based on a numeric comparison. The aug 2003 use-cases fix that by explicitly casting the values to xs:decimal. -- Xavier Franc From mhk@mhk.me.uk Sat Oct 18 23:54:02 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9J6s1ZK027820 for ; Sat, 18 Oct 2003 23:54:02 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (VisNetic.MailServer.v6.2.2.0) with ESMTP id LTN37901; Sun, 19 Oct 2003 08:03:04 +0100 From: "Michael Kay" To: , Subject: RE: [xquery-talk] XQuery Platform Support Date: Sun, 19 Oct 2003 08:02:04 +0100 Message-ID: <000201c3960e$e71f1bb0$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Oct 2003 06:54:03 -0000 > If I had to have this app out the door next week I would be > using XSLT, but luckily it doesn't need to be completed until > about 3rd QTR next year. In my opinion XQuery appears to be a > bit more powerful with it's built in functions, ability to > create user defined functions and it's SQL like FLWR > expressions. I've never been a big fan of the XSLT syntax. > It's your decision, and I certainly haven't got enough information to do a risk assessment for you, so I won't try. Syntax considerations are a matter of subjective preference (unless and until someone does a scientific study of the ergonomics). As with many other languages, XSLT users typically love the syntax, and non-users hate it. But in terms of functionality, XSLT 2.0 is richer than XQuery 1.0. It does have user-defined functions, and it has constructs that are equivalent in power to FLWR expressions (with a couple of minor exceptions in the area of sorting). If I were asked to choose which language to use for a given project, I would say without much hesitation: Use XQuery if you accessing persistent data in a database, use XSLT if you are accessing transient XML documents in memory. Michael Kay From mcarey@bea.com Sun Oct 19 22:20:13 2003 Received: from ussjmh01.bea.com (ussjmh01-ext.bea.com [63.96.162.5]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9K5KDZK004624 for ; Sun, 19 Oct 2003 22:20:13 -0700 Received: from santa-clara.bea.com (santa-clara.bea.com [206.189.39.47]) by ussjmh01.bea.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id h9K5Pb5I024893; Sun, 19 Oct 2003 22:25:37 -0700 Received: from MCAREY ([192.168.11.14]) by santa-clara.bea.com (8.10.2+Sun/8.10.2) with SMTP id h9K5PWk12669; Sun, 19 Oct 2003 22:25:37 -0700 (PDT) From: "Michael Carey" To: , Subject: RE: [xquery-talk] XQuery Platform Support Date: Sun, 19 Oct 2003 22:22:55 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 05:20:14 -0000 Just chiming in to agree with John. There are now commercial-grade XQuery implementations available, and it sure seems nicer for implementing transformations than XSLT.... -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com]On Behalf Of john.zink@prudential.com Sent: Friday, October 17, 2003 6:46 AM To: talk@xquery.com Subject: RE: [xquery-talk] XQuery Platform Support If I had to have this app out the door next week I would be using XSLT, but luckily it doesn't need to be completed until about 3rd QTR next year. In my opinion XQuery appears to be a bit more powerful with it's built in functions, ability to create user defined functions and it's SQL like FLWR expressions. I've never been a big fan of the XSLT syntax. "Michael Kay" To: , Thursday October 16, 2003 03:28 PM cc: Subject: RE: [xquery-talk] XQuery Platform Support Surely, if this is a real application, you should be writing it in XSLT? Never mind the merits of the languages, surely a technology that has been stable for nearly four years is more appropriate to your needs than one that is still in beta? Michael Kay > -----Original Message----- > From: talk-bounces@xquery.com > [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com > Sent: 16 October 2003 15:29 > To: talk@xquery.com > Subject: RE: [xquery-talk] XQuery Platform Support > > > > OK..Let me see if I can explain it a bit clearer. > We basically have 2 scenarios where a rules engine needs to > be implemented. For our "new business" process I need an > engine that examines application type questions and returns a > result for the policy. The result can be either accept or > reject the policy. The decision is made based upon a > collection of rules. For example if you have 3 speeding > tickets in the last month you will be declined. This engine > has been created as I explained before. The new engine is > replacing COM components that have all the rules hard coded > in the form of "IF-THEN-ELSE" statements. The user can now > create the rules based on a schema that describes the message > the client will pass to the engine. The engine takes the > rules entered by the user and converts them to XQuery > expressions. The engine than runs the XQuery expressions > against the XML being passed from the client to > determine the result for the policy (hold or accept). The second > scenario is we have another engine running on the mainframe > that processes policies when they renew on a yearly basis. > This engine is basically a COBOL program that processes a > sequential input file and updates a VSAM file with the > results. This engine processes thousands of records every > night in a batch process. I would like to use the same > client application > for building the rules as I mentioned in the first scenario. > I would then need a way to get a mainframe program that runs > in a batch process to somehow process the XQuery statements. > I believe it would be too slow to send mainframe records down > to the server to run against the distributed > engine. I only have a short window for the mainframe batch > process. Hope > this clarifies my situation. I've just started to examine > the mainframe process so I haven't really formulated any real > solutions for the mainframe side of the problem. > > > John Z > > > > > > "James Governor" > > > To: > > , > > > > cc: > > > Thursday October 16, 2003 09:48 AM > Subject: RE: [xquery-talk] XQuery Platform Support > > > > > > > > > > > > I am not sure from your question exactly what scenario you're > talking to. > > However it is worth noting that IBM this week acquired a > mainframe data integration firm called CrossAccess, which was > pitched as filling out its DB2 Information Integrator (II) strategy > http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From danielaf@bea.com Sun Oct 19 22:20:57 2003 Received: from ussjmh01.bea.com (ussjmh01-ext.bea.com [63.96.162.5]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9K5KvZK004646 for ; Sun, 19 Oct 2003 22:20:57 -0700 Received: from santa-clara.bea.com (santa-clara.bea.com [206.189.39.47]) by ussjmh01.bea.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id h9K5QK5I024955; Sun, 19 Oct 2003 22:26:20 -0700 Received: from bea.com ([10.61.4.37]) by santa-clara.bea.com (8.10.2+Sun/8.10.2) with ESMTP id h9K5QHk12709; Sun, 19 Oct 2003 22:26:17 -0700 (PDT) Date: Sun, 19 Oct 2003 22:26:32 -0700 Subject: Re: [xquery-talk] XQuery Platform Support Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: "Michael Kay" From: Daniela Florescu In-Reply-To: <000201c3960e$e71f1bb0$6401a8c0@pcukmka> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Cc: john.zink@prudential.com, talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 05:20:57 -0000 > But in terms of functionality, XSLT 2.0 is richer than XQuery 1.0. !? I was left with the impression the two languages have equivalent expressive power. Could you detail please ? What would be an example of a query that can be expressed in XSLT 2.0 and cannot be expressed in Xquery 1.0 ? Moreover, I know at least 10 relatively good implementations of Xquery 1.0 but I am not aware of so many XSLT 2.0 implementations (if any). Regards, Dana From mhk@mhk.me.uk Mon Oct 20 00:54:23 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9K7sLZK006860 for ; Mon, 20 Oct 2003 00:54:22 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (VisNetic.MailServer.v6.2.2.0) with ESMTP id LTN37901; Mon, 20 Oct 2003 09:03:31 +0100 From: "Michael Kay" To: "'Daniela Florescu'" Subject: RE: [xquery-talk] XQuery Platform Support Date: Mon, 20 Oct 2003 09:02:31 +0100 Message-ID: <000001c396e0$8399c7c0$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: john.zink@prudential.com, talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 07:54:23 -0000 > > But in terms of functionality, XSLT 2.0 is richer than XQuery 1.0. > > !? I was left with the impression the two languages have > equivalent expressive power. Both languages are computationally complete, so in that sense they have equivalent expressive power. The differences are in terms of use cases that can be done easily in one language and cannot be done easily in the other. The only constructs in XQuery that don't translate trivially into XSLT 2.0, as far as I am aware, are: (a) order by (ability to sort a tuple stream, rather than just a sequence) (b) separately-compilable modules > Could you detail please ? What > would be an example of a query that can be expressed in XSLT > 2.0 and cannot be expressed in Xquery 1.0 ? > Constructs in XSLT 2.0 that don't translate trivially into XQuery include: (a) template rules (b) attribute sets (c) analyze-string (d) for-each-group (e) keys (f) format-number (g) format-date (h) unparsed-text (i) multiple result documents (j) serialization control (k) import precedence Most of these features are appropriate to a transformation (and rendition) language and are not appropriate to a query language. This is why I advise people to use XQuery for database query and XSLT for document transformation (including for rendering the results of a query). You asked for an example of a "query" that can be expressed in XSLT 2.0 but not in XQuery 1.0: that's the wrong question, because XSLT 2.0 is not designed to express queries. > Moreover, I know at least 10 relatively good implementations > of Xquery 1.0 but I am > not aware of so many XSLT 2.0 implementations (if any). > There are about 20 XSLT 1.0 processors around, but only three XSLT 2.0 processors that I know of (one of which has not yet shipped). I think this is an inevitable consequence of the fact that it is a 2.0 spec: for most 1.0 vendors, it makes sense to hold back until the 2.0 specs are completely stable. I suspect there will never be more than five or six XSLT 2.0 implementations, because the weaker products will drop out of the race, and because commercial vendors can't see how to make money competing against open source offerings. Five is plenty to give users an effective choice. Of course my advice to someone planning a production application about the risks of building it on XQuery 1.0 apply equally to XSLT 2.0. The stable risk-free platform that's available today is XSLT 1.0. Michael Kay From john.zink@prudential.com Mon Oct 20 04:32:51 2003 Received: from pa-mailgate2.prudential.com (ny-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9KBWoZK008432 for ; Mon, 20 Oct 2003 04:32:51 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h9KBe9dY007671 for ; Mon, 20 Oct 2003 07:40:09 -0400 (EDT) Subject: RE: [xquery-talk] XQuery Platform Support To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: john.zink@prudential.com Date: Mon, 20 Oct 2003 07:40:06 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/20/2003 07:40:08 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 11:32:51 -0000 I do not need to do any transformations. I am only interested in querying XML to determine if a condition(s) exists. I've only done one project with XSLT and I did not like the syntax. With this project I am currently working on I need the ability to generate XQuery expressions on the fly from a relational database that I have designed. The database contains conditions entered by a business user. The database is built on a hierarchy of rules, conditions and expressions. A rule can contain multiple conditions, a condition can contain multiple expressions. From the research I have done it seemed quite a bit simpler to generate XQuery. "Michael Kay" To: "'Daniela Florescu'" Monday October 20, 2003 04:02 AM cc: , Subject: RE: [xquery-talk] XQuery Platform Support > > But in terms of functionality, XSLT 2.0 is richer than XQuery 1.0. > > !? I was left with the impression the two languages have > equivalent expressive power. Both languages are computationally complete, so in that sense they have equivalent expressive power. The differences are in terms of use cases that can be done easily in one language and cannot be done easily in the other. The only constructs in XQuery that don't translate trivially into XSLT 2.0, as far as I am aware, are: (a) order by (ability to sort a tuple stream, rather than just a sequence) (b) separately-compilable modules > Could you detail please ? What > would be an example of a query that can be expressed in XSLT > 2.0 and cannot be expressed in Xquery 1.0 ? > Constructs in XSLT 2.0 that don't translate trivially into XQuery include: (a) template rules (b) attribute sets (c) analyze-string (d) for-each-group (e) keys (f) format-number (g) format-date (h) unparsed-text (i) multiple result documents (j) serialization control (k) import precedence Most of these features are appropriate to a transformation (and rendition) language and are not appropriate to a query language. This is why I advise people to use XQuery for database query and XSLT for document transformation (including for rendering the results of a query). You asked for an example of a "query" that can be expressed in XSLT 2.0 but not in XQuery 1.0: that's the wrong question, because XSLT 2.0 is not designed to express queries. > Moreover, I know at least 10 relatively good implementations > of Xquery 1.0 but I am > not aware of so many XSLT 2.0 implementations (if any). > There are about 20 XSLT 1.0 processors around, but only three XSLT 2.0 processors that I know of (one of which has not yet shipped). I think this is an inevitable consequence of the fact that it is a 2.0 spec: for most 1.0 vendors, it makes sense to hold back until the 2.0 specs are completely stable. I suspect there will never be more than five or six XSLT 2.0 implementations, because the weaker products will drop out of the race, and because commercial vendors can't see how to make money competing against open source offerings. Five is plenty to give users an effective choice. Of course my advice to someone planning a production application about the risks of building it on XQuery 1.0 apply equally to XSLT 2.0. The stable risk-free platform that's available today is XSLT 1.0. Michael Kay From mhk@mhk.me.uk Mon Oct 20 09:54:32 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9KGsVZK011745 for ; Mon, 20 Oct 2003 09:54:32 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (VisNetic.MailServer.v6.2.2.0) with SMTP id LTN37901; Mon, 20 Oct 2003 17:59:10 +0100 From: "Michael Kay" To: , Subject: RE: [xquery-talk] XQuery Platform Support Date: Mon, 20 Oct 2003 17:58:09 +0100 Message-ID: <000101c3972b$576d13a0$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 16:54:32 -0000 > I do not need to do any transformations. I am only > interested in querying XML to determine if a condition(s) > exists. I've only done one project with XSLT and I did not > like the syntax. With this project I am currently working on > I need the ability to generate XQuery expressions on the fly > from a relational database that I have designed. The > database contains conditions entered by a business user. The > database is built on a hierarchy of rules, conditions and > expressions. A rule can contain multiple conditions, a > condition can contain multiple expressions. From the > research I have done it seemed quite a bit simpler to generate XQuery. That might be true for you, though there are plenty of people using XSLT meta-stylesheets to generate XSLT, and it's often quoted as being one of the (few?) advantages of the XML-based syntax of XSLT that it makes it easy to generate a stylesheet as the output of a stylesheet. The fact that XQuery isn't XML does make it quite tricky to generate an XQuery as the output of another XQuery. Michael Kay From jhunter@xquery.com Mon Oct 20 14:28:40 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9KLSeZK016102 for ; Mon, 20 Oct 2003 14:28:40 -0700 Received: from xquery.com ([192.168.1.45]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9KLYPig010545 for ; Mon, 20 Oct 2003 14:34:25 -0700 (PDT) Message-ID: <3F94543D.8090909@xquery.com> Date: Mon, 20 Oct 2003 14:31:41 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xquery-talk] BumbleBee 1.0.2 X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 21:28:40 -0000 Hi everyone, I'm happy to announce BumbleBee 1.0.2. This new release includes the following improvements: * Updated the NIST tests to improve the accuracy of the results. * Added XhiveAdapter to support the X-Hive XQuery engine (developed by Sander Bos at X-Hive). * Expanded the GettingStarted guide to provide instructions on configuring BumbleBee to communicate with each XQuery engine. * Fixed a bug in QizxAdapter to properly identify empty result content. * Incorporated the new Qizx 0.2_01 release containing bug fixes found as a result of running BumbleBee. http://xquery.com/bumblebee -jh- From jhunter@xquery.com Mon Oct 20 15:42:13 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9KMgDZK017109 for ; Mon, 20 Oct 2003 15:42:13 -0700 Received: from xquery.com ([192.168.1.45]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9KMmSig011057 for ; Mon, 20 Oct 2003 15:48:28 -0700 (PDT) Message-ID: <3F946598.3010000@xquery.com> Date: Mon, 20 Oct 2003 15:45:44 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: talk@xquery.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xquery-talk] XQuery Wiki X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 22:42:14 -0000 Hi everyone, A second announcement today (we've been busy). We've set up an XQuery Wiki on xquery.com. For those who aren't familiar, a Wiki is a set of web pages that are collaboratively edited by visitors to the site. Only because the visitors can easily edit the pages, they're not just "visitors" anymore and the site begins to contain a collective set of knowledge. The Wiki pages are easily edited online from the comfort of your own browser. You don't need to know HTML or use an editor, just click the "Edit" link and modify the contents online. There are simple little conventions used instead like "lines starting with an asterisk are bullets" and "words with TwoCapitals are Wiki words". Every WikiWord has its own page and is automatically linked to from any other page when mentioning the WikiWord. We're hoping you all contribute your unique XQuery experiences to the Wiki. We've sketched out a few pages into the Wiki and have recruited some friends like Darin McBeath to start us off with a Best Practices section. But history shows Wikis work best without too much initial structure, so we've left it intentionally raw around the edges. We're hoping you can help soften it up. http://xquery.com/wiki/ Don't be afraid to make changes. Everything's in RCS so if you goof, we can easily go back in time. You do have to register, but that's just so RCS can say who did what. Ideas: * Brain teasers * Vendor listings and comments * Article list * Spec bugs to watch out for * BumbleBee test issues * Whatever makes sense to you Other Wikis to look toward as samples: * http://www.intellij.org/twiki/bin/view/Main/WebHome * http://nagoya.apache.org/wiki/apachewiki.cgi * http://c2.com/cgi/wiki (the original, with history) -jh- From uday.s@Sun.COM Mon Oct 20 22:10:23 2003 Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9L5ANZK021135 for ; Mon, 20 Oct 2003 22:10:23 -0700 Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id h9L5Fu5u025337 for ; Mon, 20 Oct 2003 23:15:57 -0600 (MDT) Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91]) by sfbaymail1sca.SFBay.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id h9L5FuoV018621 for ; Mon, 20 Oct 2003 22:15:56 -0700 (PDT) Received: from sun.com (vpn-129-150-16-199.SFBay.Sun.COM [129.150.16.199]) by ha13sca-mail1.sfbay.sun.com (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct 1 2002)) with ESMTP id <0HN3000WQDAK4S@ha13sca-mail1.sfbay.sun.com> for talk@xquery.com; Mon, 20 Oct 2003 22:15:56 -0700 (PDT) Date: Mon, 20 Oct 2003 22:18:52 -0700 From: Uday Subbarayan To: talk@xquery.com Message-id: <3F94C1BC.2090207@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 Subject: [xquery-talk] Xquery engine to use w/ J2EE servers. X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 05:10:23 -0000 Hi XQuery'ers, Can you pl suggest an XQuery engine(opensource /closed source, prefer opensource) to use in Tomcat/J2EE server environments? I am just starting to learn XQuery and would like to write my first helloworld with XQuery for the server-side & JSP/Servlet model for the front end... Thanks, -Uday. From per@bothner.com Mon Oct 20 22:33:29 2003 Received: from mtaw6.prodigy.net (mtaw6.prodigy.net [64.164.98.56]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9L5XTZK021357 for ; Mon, 20 Oct 2003 22:33:29 -0700 Received: from bothner.com (adsl-216-102-199-253.dsl.snfc21.pacbell.net [216.102.199.253]) by mtaw6.prodigy.net (8.12.9/8.12.3) with ESMTP id h9L5ck7Q000857; Mon, 20 Oct 2003 22:38:47 -0700 (PDT) Message-ID: <3F94C67B.1020707@bothner.com> Date: Mon, 20 Oct 2003 22:39:07 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Uday Subbarayan Subject: Re: [xquery-talk] Xquery engine to use w/ J2EE servers. References: <3F94C1BC.2090207@sun.com> In-Reply-To: <3F94C1BC.2090207@sun.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 05:33:29 -0000 Uday Subbarayan wrote: > Can you pl suggest an XQuery engine(opensource /closed source, > prefer opensource) to use in Tomcat/J2EE server environments? I am just > starting to learn XQuery and would like to write my first helloworld > with XQuery for the server-side & JSP/Servlet model for the front end... This article provides a simple "how-to" for writing, installing, and running a "hello world"-type XQuery "form-based application" using Qexo under Tomcat: http://www.gnu.org/software/qexo/simple-xquery-webapp.html The XQuery module is compiled on-the-fly to s servlet, not interpreted. -- --Per Bothner per@bothner.com http://per.bothner.com/ From mhk@mhk.me.uk Tue Oct 21 01:06:18 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9L86GZK022548 for ; Tue, 21 Oct 2003 01:06:17 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (VisNetic.MailServer.v6.2.2.0) with ESMTP id LTN37901; Tue, 21 Oct 2003 09:15:34 +0100 From: "Michael Kay" To: "'Uday Subbarayan'" , Subject: RE: [xquery-talk] Xquery engine to use w/ J2EE servers. Date: Tue, 21 Oct 2003 09:14:35 +0100 Message-ID: <004001c397ab$5d69ea50$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <3F94C1BC.2090207@sun.com> Importance: Normal Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 08:06:18 -0000 > Hi XQuery'ers, > Can you pl suggest an XQuery engine(opensource /closed source, > prefer opensource) to use in Tomcat/J2EE server environments? > I am just > starting to learn XQuery and would like to write my first helloworld > with XQuery for the server-side & JSP/Servlet model for the > front end... > Well, Saxon is certainly one you should try. It's 100% Java so there should be no installation hassles. The only problem with this kind of environment is that unlike XSLT, there is no standard XQuery API yet, so if you want to try out different processors you will have to write a custom driver for each one. http://saxon.sf.net/ Michael Kay From john.zink@prudential.com Tue Oct 21 05:09:07 2003 Received: from pa-mailgate2.prudential.com (ny-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LC96ZK024080 for ; Tue, 21 Oct 2003 05:09:07 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h9LC9DdY010749 for ; Tue, 21 Oct 2003 08:09:13 -0400 (EDT) Subject: RE: [xquery-talk] XQuery Platform Support To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: john.zink@prudential.com Date: Tue, 21 Oct 2003 08:09:11 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/21/2003 08:09:11 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 12:09:07 -0000 Getting back to the XQuery on the mainframe discussion, here is what I am envisioning I need to do: The current mainframe batch process sequentially reads thru a QSAM file and cuts a feed to a COBOL program that runs the rules. I want to replace the COBOL program with a program that can execute XQuery expressions. I will need something that takes the feed and converts it to XML. The XML will then be passed to a program that can execute XQuery and pass back the result. The result will then be converted back to a COBOL copybook type layout and returned to the original program. Does this sound possible ??? It's been quite a few years since I've worked on the "big iron". "James Governor" To: , cc: Thursday October 16, 2003 09:48 AM Subject: RE: [xquery-talk] XQuery Platform Support I am not sure from your question exactly what scenario you're talking to. However it is worth noting that IBM this week acquired a mainframe data integration firm called CrossAccess, which was pitched as filling out its DB2 Information Integrator (II) strategy http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. From uday.s@Sun.COM Tue Oct 21 06:12:53 2003 Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LDCrZK024598 for ; Tue, 21 Oct 2003 06:12:53 -0700 Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9LDD5Ph005676; Tue, 21 Oct 2003 07:13:05 -0600 (MDT) Received: from phys-ha13sca-1 (phys-ha13sca-1.SFBay.Sun.COM [129.145.155.91]) by sfbaymail1sca.SFBay.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id h9LDD5oV020025; Tue, 21 Oct 2003 06:13:05 -0700 (PDT) Received: from sun.com (vpn-129-150-17-73.SFBay.Sun.COM [129.150.17.73]) by ha13sca-mail1.sfbay.sun.com (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct 1 2002)) with ESMTP id <0HN3000ZGZDS4S@ha13sca-mail1.sfbay.sun.com>; Tue, 21 Oct 2003 06:13:05 -0700 (PDT) Date: Tue, 21 Oct 2003 06:16:01 -0700 From: Uday Subbarayan Subject: Re: [xquery-talk] Xquery engine to use w/ J2EE servers. To: Michael Kay , per@bothner.com Message-id: <3F953191.9050007@sun.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_NxxQkd0YzzkCbjTOHs6Axw)" X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 References: <004001c397ab$5d69ea50$6401a8c0@pcukmka> Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 13:12:54 -0000 --Boundary_(ID_NxxQkd0YzzkCbjTOHs6Axw) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Thanks Michael & Per for your quick responses...Let me try both and I will share my experience here... yes,i know, let's wait for JSR225! -Uday. Michael Kay wrote: >>Hi XQuery'ers, >> Can you pl suggest an XQuery engine(opensource /closed source, >>prefer opensource) to use in Tomcat/J2EE server environments? >>I am just >>starting to learn XQuery and would like to write my first helloworld >>with XQuery for the server-side & JSP/Servlet model for the >>front end... >> >> >> > >Well, Saxon is certainly one you should try. It's 100% Java so there >should be no installation hassles. The only problem with this kind of >environment is that unlike XSLT, there is no standard XQuery API yet, so >if you want to try out different processors you will have to write a >custom driver for each one. > >http://saxon.sf.net/ > >Michael Kay > > > --Boundary_(ID_NxxQkd0YzzkCbjTOHs6Axw) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT Thanks Michael & Per for your quick responses...Let me try both and I will share my experience here...
<there is no standard XQuery API yet>
yes,i know, let's wait for JSR225!

-Uday.

Michael Kay wrote:
Hi XQuery'ers,
      Can you pl suggest an XQuery engine(opensource /closed source, 
prefer opensource) to use in Tomcat/J2EE server environments? 
I am just 
starting to learn XQuery and would like to write my first helloworld 
with XQuery for the server-side & JSP/Servlet model for the 
front end...

    

Well, Saxon is certainly one you should try. It's 100% Java so there
should be no installation hassles. The only problem with this kind of
environment is that unlike XSLT, there is no standard XQuery API yet, so
if you want to try out different processors you will have to write a
custom driver for each one.

http://saxon.sf.net/

Michael Kay

--Boundary_(ID_NxxQkd0YzzkCbjTOHs6Axw)-- From john.zink@prudential.com Tue Oct 21 07:39:46 2003 Received: from pa-mailgate2.prudential.com (pa-mailgate2.prudential.com [12.42.50.49]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LEdjZK025668 for ; Tue, 21 Oct 2003 07:39:46 -0700 Received: from paerscngw01.prudential.com (paerscngw01.metro.prudential.com [48.13.71.121]) by pa-mailgate2.prudential.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h9LEeZda001064 for ; Tue, 21 Oct 2003 10:40:37 -0400 (EDT) Subject: RE: [xquery-talk] XQuery Platform Support To: talk@xquery.com X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: john.zink@prudential.com Date: Tue, 21 Oct 2003 10:40:34 -0400 X-MIMETrack: Serialize by Router on PAERSCNGW01/SERVER/Prudential(Release 5.0.11 |July 24, 2002) at 10/21/2003 10:40:36 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 14:39:46 -0000 What would be my options on the mainframe side for 1) converting a COBOL copybook type feed to a XML feed 2) what type of program could execute an XQuery expression on the mainframe ... Java ? Can a COBOL program invoke a Java program ? "kent tegels" To: , Tuesday October 21, 2003 08:21 AM cc: Subject: RE: [xquery-talk] XQuery Platform Support Yes, it sounds possible. -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Tuesday, October 21, 2003 7:09 AM To: talk@xquery.com Subject: RE: [xquery-talk] XQuery Platform Support Getting back to the XQuery on the mainframe discussion, here is what I am envisioning I need to do: The current mainframe batch process sequentially reads thru a QSAM file and cuts a feed to a COBOL program that runs the rules. I want to replace the COBOL program with a program that can execute XQuery expressions. I will need something that takes the feed and converts it to XML. The XML will then be passed to a program that can execute XQuery and pass back the result. The result will then be converted back to a COBOL copybook type layout and returned to the original program. Does this sound possible ??? It's been quite a few years since I've worked on the "big iron". "James Governor" To: , cc: Thursday October 16, 2003 09:48 AM Subject: RE: [xquery-talk] XQuery Platform Support I am not sure from your question exactly what scenario you're talking to. However it is worth noting that IBM this week acquired a mainframe data integration firm called CrossAccess, which was pitched as filling out its DB2 Information Integrator (II) strategy http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From per@bothner.com Tue Oct 21 09:32:55 2003 Received: from mtaw6.prodigy.net (mtaw6.prodigy.net [64.164.98.56]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LGWtZK027420 for ; Tue, 21 Oct 2003 09:32:55 -0700 Received: from bothner.com (adsl-216-102-199-253.dsl.snfc21.pacbell.net [216.102.199.253]) by mtaw6.prodigy.net (8.12.9/8.12.3) with ESMTP id h9LGXl7Q014769; Tue, 21 Oct 2003 09:33:47 -0700 (PDT) Message-ID: <3F956001.5010807@bothner.com> Date: Tue, 21 Oct 2003 09:34:09 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Uday Subbarayan Subject: Re: [xquery-talk] Xquery engine to use w/ J2EE servers. References: <004001c397ab$5d69ea50$6401a8c0@pcukmka> <3F953191.9050007@sun.com> In-Reply-To: <3F953191.9050007@sun.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 16:32:56 -0000 Uday Subbarayan wrote: > Thanks Michael & Per for your quick responses...Let me try both and I > will share my experience here... You might try the Qexo version from CVS, rather than the "released" version 1.7, as there have been many improvements since the 1.7 release. On the hand for just getting a feel for what Qexo can do, Qexo 1.7 will be fine. -- --Per Bothner per@bothner.com http://per.bothner.com/ From mhk@mhk.me.uk Tue Oct 21 09:52:00 2003 Received: from mail.domainnamesgb.com (195-97-223-131.onyx.net [195.97.223.131] (may be forged)) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LGpxZK027770 for ; Tue, 21 Oct 2003 09:52:00 -0700 Received: from pcukmka ([81.98.109.162]) by mail.domainnamesgb.com (VisNetic.MailServer.v6.2.2.0) with ESMTP id LTN37901; Tue, 21 Oct 2003 17:56:17 +0100 From: "Michael Kay" To: , Subject: RE: [xquery-talk] XQuery Platform Support Date: Tue, 21 Oct 2003 17:55:18 +0100 Message-ID: <001801c397f4$1b85e500$6401a8c0@pcukmka> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 16:52:01 -0000 > What would be my options on the mainframe side for > 1) converting a COBOL copybook type feed to a XML feed Well, you need to parse the COBOL. This means you need a language that's reasonably good at regular expression handling. Perl and Python are common choices; XSLT 2.0 has good capabilities in this area, but XSLT 1.0 and XQuery 1.0 aren't really suitable. I've no idea what's available on IBM mainframes. > 2) what type of program could execute an XQuery expression on > the mainframe ... Java ? Can a COBOL program invoke a Java program ? Many XQuery processors that run on the mainframe are likely to be Java programs. Java does offer cross-language support, but the question of how to call Java from COBOL on an IBM mainframe is just a little bit off-centre for this list! Michael Kay From RelDev@aol.com Tue Oct 21 10:03:03 2003 Received: from imo-r03.mx.aol.com (imo-r03.mx.aol.com [152.163.225.99]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LH32ZK027941 for ; Tue, 21 Oct 2003 10:03:03 -0700 Received: from RelDev@aol.com by imo-r03.mx.aol.com (mail_out_dev1.2.) id 8.17e.21d6e5b2 (16111); Tue, 21 Oct 2003 13:01:04 -0400 (EDT) Received: from STEVENSMITH (ip67.tonic.com [216.54.231.67]) by air-id12.mx.aol.com (v96.8) with ESMTP id MAILINID123-3eef3f95664f1a1; Tue, 21 Oct 2003 13:01:04 -0400 Date: Tue, 21 Oct 2003 11:59:21 -0500 From: "Steven Smith" Subject: RE: [xquery-talk] XQuery Platform Support To: "Michael Kay" In-Reply-To: <001801c397f4$1b85e500$6401a8c0@pcukmka> Message-ID: <3F9565E9.9020507@aol.com> References: <001801c397f4$1b85e500$6401a8c0@pcukmka> X-Mailer: AOL Communicator (20030919.3 Win) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii X-AOL-IP: 216.54.231.67 Cc: john.zink@prudential.com, talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 17:03:03 -0000 Minimally, you could call a Java program from COBOL by going through an intermediate layer written in C that leverages JNI to talk to Java. Michael Kay wrote on 10/21/2003, 11:55 AM: > > What would be my options on the mainframe side for > > 1) converting a COBOL copybook type feed to a XML feed > > Well, you need to parse the COBOL. This means you need a language that's > reasonably good at regular expression handling. Perl and Python are > common choices; XSLT 2.0 has good capabilities in this area, but XSLT > 1.0 and XQuery 1.0 aren't really suitable. I've no idea what's available > on IBM mainframes. > > > 2) what type of program could execute an XQuery expression on > > the mainframe ... Java ? Can a COBOL program invoke a Java program ? > > Many XQuery processors that run on the mainframe are likely to be Java > programs. Java does offer cross-language support, but the question of > how to call Java from COBOL on an IBM mainframe is just a little bit > off-centre for this list! > > Michael Kay > > _______________________________________________ > talk@xquery.com > http://www.x-query.com/mailman/listinfo/talk > From ktegels@msn.com Tue Oct 21 05:21:44 2003 Received: from hotmail.com (bay5-dav139.bay5.hotmail.com [65.54.173.169]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LCLiZK024165 for ; Tue, 21 Oct 2003 05:21:44 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 21 Oct 2003 05:21:55 -0700 Received: from 63.165.129.137 by bay5-dav139.bay5.hotmail.com with DAV; Tue, 21 Oct 2003 12:21:55 +0000 X-Originating-IP: [63.165.129.137] X-Originating-Email: [ktegels@msn.com] From: "kent tegels" To: , Subject: RE: [xquery-talk] XQuery Platform Support Date: Tue, 21 Oct 2003 07:21:54 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcOXzDhJtb7kpgTnRwul6gpj8FUPhAAAaXEQ In-Reply-To: X-OriginalArrivalTime: 21 Oct 2003 12:21:55.0135 (UTC) FILETIME=[EA4A8CF0:01C397CD] X-Mailman-Approved-At: Tue, 21 Oct 2003 10:40:19 -0700 Cc: X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 12:21:44 -0000 Yes, it sounds possible. -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Tuesday, October 21, 2003 7:09 AM To: talk@xquery.com Subject: RE: [xquery-talk] XQuery Platform Support Getting back to the XQuery on the mainframe discussion, here is what I am envisioning I need to do: The current mainframe batch process sequentially reads thru a QSAM file and cuts a feed to a COBOL program that runs the rules. I want to replace the COBOL program with a program that can execute XQuery expressions. I will need something that takes the feed and converts it to XML. The XML will then be passed to a program that can execute XQuery and pass back the result. The result will then be converted back to a COBOL copybook type layout and returned to the original program. Does this sound possible ??? It's been quite a few years since I've worked on the "big iron". "James Governor" To: , cc: Thursday October 16, 2003 09:48 AM Subject: RE: [xquery-talk] XQuery Platform Support I am not sure from your question exactly what scenario you're talking to. However it is worth noting that IBM this week acquired a mainframe data integration firm called CrossAccess, which was pitched as filling out its DB2 Information Integrator (II) strategy http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From ktegels@msn.com Tue Oct 21 08:01:03 2003 Received: from hotmail.com (bay5-dav64.bay5.hotmail.com [65.54.173.94]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LF13ZK026005 for ; Tue, 21 Oct 2003 08:01:03 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 21 Oct 2003 08:01:59 -0700 Received: from 63.165.129.137 by bay5-dav64.bay5.hotmail.com with DAV; Tue, 21 Oct 2003 15:01:59 +0000 X-Originating-IP: [63.165.129.137] X-Originating-Email: [ktegels@msn.com] From: "kent tegels" To: Subject: RE: [xquery-talk] XQuery Platform Support Date: Tue, 21 Oct 2003 10:02:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcOX4Vz8EKkdNjOeQ3GOH1hf9tFChAAAFIDQ Message-ID: X-OriginalArrivalTime: 21 Oct 2003 15:01:59.0874 (UTC) FILETIME=[47296A20:01C397E4] X-Mailman-Approved-At: Tue, 21 Oct 2003 10:40:19 -0700 Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 15:01:03 -0000 1.) At a 30,000 foot-view, that's probably going to be a fair amount of code to be written there. Not aware of any off-the-self offerings that would do that. I sure the heck wouldn't want to write COBOL to generate XML, I'm assuming that you've got something else. If not, I might be able to point you at an BAL programmer or two that's looking for work (sad little grin) 2.) Depends on the COBOL implementation, Operating System and so on. I'm wondering if the complexity imparted by the elegance of this solution exceeds its over overhead, though. kt -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Tuesday, October 21, 2003 9:41 AM To: talk@xquery.com Subject: RE: [xquery-talk] XQuery Platform Support What would be my options on the mainframe side for 1) converting a COBOL copybook type feed to a XML feed 2) what type of program could execute an XQuery expression on the mainframe ... Java ? Can a COBOL program invoke a Java program ? "kent tegels" To: , Tuesday October 21, 2003 08:21 AM cc: Subject: RE: [xquery-talk] XQuery Platform Support Yes, it sounds possible. -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Tuesday, October 21, 2003 7:09 AM To: talk@xquery.com Subject: RE: [xquery-talk] XQuery Platform Support Getting back to the XQuery on the mainframe discussion, here is what I am envisioning I need to do: The current mainframe batch process sequentially reads thru a QSAM file and cuts a feed to a COBOL program that runs the rules. I want to replace the COBOL program with a program that can execute XQuery expressions. I will need something that takes the feed and converts it to XML. The XML will then be passed to a program that can execute XQuery and pass back the result. The result will then be converted back to a COBOL copybook type layout and returned to the original program. Does this sound possible ??? It's been quite a few years since I've worked on the "big iron". "James Governor" To: , cc: Thursday October 16, 2003 09:48 AM Subject: RE: [xquery-talk] XQuery Platform Support I am not sure from your question exactly what scenario you're talking to. However it is worth noting that IBM this week acquired a mainframe data integration firm called CrossAccess, which was pitched as filling out its DB2 Information Integrator (II) strategy http://www.ibm.com/news/us/2003/10/142.html DB2 II is where IBM plans to instantiate xQuery, and as such it looks as if IBM is potentially moving in a helpful direction. Assuming xquery is mapped to mainframe data sources accessed natively using CrossAccess connector technology. Until IBM delivers a native XML store for DB2 however, some of the xQuery productization is on hold. IBM was partnering with Nimble Technologies for xQuery support, but Actuate acquired Nimble, so I am not sure of the status of that deal. Hope that helps a little but I am not sure we understood your problem. As SoftwareAG points out, Tamino already offers xQuery support on the mainframe. Are you running 390 or ZOS, or VM/VSE or whatever? Which IBM mainframe OS? -----Original Message----- From: talk-bounces@xquery.com [mailto:talk-bounces@xquery.com] On Behalf Of john.zink@prudential.com Sent: Thursday, October 16, 2003 2:07 PM To: talk@xquery.com Cc: ktegels@msn.com Subject: RE: [xquery-talk] XQuery Platform Support Not in the Yukon beta, but I am in the Whidbey alpha program. The mainframe OS is IBM. _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk _______________________________________________ talk@xquery.com http://www.x-query.com/mailman/listinfo/talk From hip@cs.okstate.edu Tue Oct 21 10:35:28 2003 Received: from csa.cs.okstate.edu (a.cs.okstate.edu [139.78.113.1]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LHZSZK028432 for ; Tue, 21 Oct 2003 10:35:28 -0700 Received: from cs.okstate.edu (localhost [127.0.0.1]) by csa.cs.okstate.edu (Postfix) with ESMTP id F3305A0685; Tue, 21 Oct 2003 12:36:55 -0500 (CDT) To: john.zink@prudential.com Subject: Re: [xquery-talk] XQuery Platform Support In-Reply-To: Your message of "Tue, 21 Oct 2003 08:09:11 EDT." Date: Tue, 21 Oct 2003 12:36:55 -0500 From: "Bradley S. Huffman" Message-Id: <20031021173656.F3305A0685@csa.cs.okstate.edu> X-Mailman-Approved-At: Tue, 21 Oct 2003 10:40:19 -0700 Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 17:35:29 -0000 john.zink@prudential.com writes: > Getting back to the XQuery on the mainframe discussion, here is what I am > envisioning I need to do: > The current mainframe batch process sequentially reads thru a QSAM file and > cuts a feed to a COBOL program that runs the rules. I want to replace the > COBOL program with a program that can execute XQuery expressions. I will > need something that takes the feed and converts it to XML. The XML will > then be passed to a program that can execute XQuery and pass back the > result. The result will then be converted back to a COBOL copybook type > layout and returned to the original program. Does this sound possible ??? > It's been quite a few years since I've worked on the "big iron". There's a company www.hostbridge.com that sells a product which is suppose to be able to take a "CICS transaction and present it as XML". I never used it so I cann't comment on how it good it is, but it might be something to look at. Brad From dhruba_borthakur@hotmail.com Tue Oct 21 11:50:01 2003 Received: from hotmail.com (bay2-f99.bay2.hotmail.com [65.54.247.99]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LIo1ZK029393 for ; Tue, 21 Oct 2003 11:50:01 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 21 Oct 2003 11:51:58 -0700 Received: from 143.127.3.10 by by2fd.bay2.hotmail.msn.com with HTTP; Tue, 21 Oct 2003 18:51:57 GMT X-Originating-IP: [143.127.3.10] X-Originating-Email: [dhruba_borthakur@hotmail.com] From: "Dhruba Borthakur" To: talk@xquery.com Date: Tue, 21 Oct 2003 11:51:57 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 21 Oct 2003 18:51:58.0677 (UTC) FILETIME=[67E3A850:01C39804] X-Mailman-Approved-At: Tue, 21 Oct 2003 12:33:54 -0700 Subject: [xquery-talk] questions about security and dynamically constructed queries X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 18:50:01 -0000 Hi XQuery gurus, I would appreciate it a lot if someone can throw some light into a few elementary questions about XQuery that I have. Thanks in advance. dhruba 1. Most of the XQuery implementations that I am familiar with supports security at the database level. An user connects to the repository using a loginname/password. Once authenticated, the user can run queries against all the data in the repository. Is there any implementation that associates security per document (or collection)? 2. One XQuery implementation (that I am familiar with) has implemented vendor extensions that allow constructing and executing a query dynamically. Do other implementations support a similar functionality? 3. In my XQuery code, I want to discover if a particular library is available. Only if it is available, I want to execute a function in the library. If the library does not exist, that I want to proceed ahead and do other things. Can I do achieve this functionality using only XQuery? (I know I can do this from a Java wrapper that looks at a specified pathname and constructs a dynamic query (prefix an import statement) if the library module at the specified path exists.) _________________________________________________________________ Never get a busy signal because you are always connected with high-speed Internet access. Click here to comparison-shop providers. https://broadband.msn.com From carmelo@nist.gov Tue Oct 21 12:38:19 2003 Received: from postmark.nist.gov (pushme.nist.gov [129.6.16.92]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LJcJZK029933 for ; Tue, 21 Oct 2003 12:38:19 -0700 Received: from Vanquisher1.nist.gov (mrblues.ncsl.nist.gov [129.6.59.165]) by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id h9LJeCe8023673 for ; Tue, 21 Oct 2003 15:40:12 -0400 (EDT) Message-Id: <5.1.0.14.2.20031021153812.029e0e88@mailserver.nist.gov> X-Sender: carmelo@mailserver.nist.gov X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 21 Oct 2003 15:40:11 -0400 To: talk@xquery.com From: Carmelo Montanez Subject: [xquery-talk] BumbleBee XQuery Test Harness Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 19:38:20 -0000 Hi: Regarding the boundary values for the data types in the NIST tests. Those values are as described in the Schema Specs. I will appreciate hearing from anyone on any specific data type that is outside the required range. We will change any test that is so required. Greetings, Carmelo From per@bothner.com Tue Oct 21 12:47:42 2003 Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LJlgZK030068 for ; Tue, 21 Oct 2003 12:47:42 -0700 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id h9LJnuTi002867 for ; Tue, 21 Oct 2003 12:49:56 -0700 (PDT) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Tue, 21 Oct 2003 12:49:25 -0700 Received: from bothner.com (vpn-scv-x1-7.apple.com [17.219.193.7]) by scv1.apple.com (8.12.9/8.12.9) with ESMTP id h9LJnTww002875; Tue, 21 Oct 2003 12:49:29 -0700 (PDT) Message-ID: <3F958DE3.5050900@bothner.com> Date: Tue, 21 Oct 2003 12:49:55 -0700 From: Per Bothner User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dhruba Borthakur Subject: Re: [xquery-talk] questions about security and dynamically constructed queries References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 19:47:42 -0000 Dhruba Borthakur wrote: > 2. One XQuery implementation (that I am familiar with) has implemented > vendor extensions that allow constructing and executing a query > dynamically. Do other implementations support a similar functionality? I would expect most implementations would support this, possibly exception those those that only support "stored queries". After all most databases allow you to create SQL dynamically, so you there is no reason not to do the same for XQuery. And implementation that are not tied to a database will probably also mostly allow dynamic query construction. This certainly includes Qexo. Perhaps I'm misunderstanding your question. -- --Per Bothner per@bothner.com http://per.bothner.com/ From jhunter@servlets.com Tue Oct 21 13:05:37 2003 Received: from snowball.huntershots.com ([65.122.201.44]) by jhunter.x-query.com (8.12.8/8.12.9) with ESMTP id h9LK5bZK030296 for ; Tue, 21 Oct 2003 13:05:37 -0700 Received: from servlets.com ([192.168.1.45]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id h9LKAXig019704; Tue, 21 Oct 2003 13:10:33 -0700 (PDT) Message-ID: <3F95921B.3090702@servlets.com> Date: Tue, 21 Oct 2003 13:07:55 -0700 From: Jason Hunter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Carmelo Montanez Subject: Re: [xquery-talk] BumbleBee XQuery Test Harness References: <5.1.0.14.2.20031021153812.029e0e88@mailserver.nist.gov> In-Reply-To: <5.1.0.14.2.20031021153812.029e0e88@mailserver.nist.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: talk@xquery.com X-BeenThere: talk@xquery.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: XQuery discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 20:05:38 -0000 Per http://www.w3.org/TR/xmlschema-2/#decimal "All ˇminimally conformingˇ processors ˇmustˇ support decimal numbers with a minimum of 18 decimal digits (i.e., with a ˇtotalDigitsˇ of 18). However, ˇminimally conformingˇ processors ˇmayˇ set an application-defined limit on the maximum number of decimal digits they