[xquery-talk] Article: "Five Practical XQuery Applications"

[Dmitri.Colebatch at toyota.com.au]

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 <mike at clarkware.com>@x-query.com on 20/08/2003 01:16:55 AM

Sent by:    talk-bounces at x-query.com


To:    talk at 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 at 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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -