Sanjiva,
We are completely open to using any other schema model from any other
project. So we could try the module from the WS project, if your
experience shows that it is better.
You are right in that all we need is a schema model.
Thanks for offering to mentor.
Vinayak
Sanjiva Weerawarana wrote:
Yes it does- but for schema support, we actually have a more useful project
called XMLSchema in the WS project. That's a clean model for XMLSchema
that's used by a bunch of ASF projects and others. We tried (hard) to use
the Xerces schema stuff when doing Axis2 (who wants to write a schema
parser!) but it was not possible because it was innately tied to parsing XML
and validation and not for general use as an XML parser. For XQuery, what is
needed is a proper schema model and XMLSchema gives that.
Anyway, I'm glad to see the StAX answer :).
Sanjiva.
On Fri, Jul 3, 2009 at 9:01 AM, Vinayak Borkar <vbo...@yahoo.com> wrote:
Sanjiva,
The way the system is built, the data source (the place from where XML is
brought into the system), is fully pluggable.
In fact, currently the parser has been implemented using StAX (JSR 173).
The XML snippets one sees in XQuery is not parsed using an XML parser.
Instead we use JavaCC to do that.
The mention of Xerces was specifically to implement schema support in
VXQuery as per the typing requirements of the XQuery spec.
Does that answer your question?
Thanks,
Vinayak
Sanjiva Weerawarana wrote:
Vinayak, in some other mail you indicated that there's little code around
yet. So ...
Can we build this on top of StAX instead of Xerces (presumably SAX)? That
allows a high performant impl on top of Axiom, which would be very useful
for all projects that use Axiom (Axis2 & family, Synapse, Abdera, Tuscany
(I
think) etc.). The StAX impl will allow CXF also to make good use of this
and
should not affect the ability to build a DOM or DTM or any other model.
I would also love to see the Axiom binding done as part of this project
but
that's not a requirement as that can be done externally.
Hmm thinking a bit more I guess the use of Xerces is just for parsing the
XQuery XML syntax bits right? You've obviously had to write a parser for
the
non-XML syntax bits (which is a lot)? So then this is really an easy
request!
Sanjiva.
On Wed, May 13, 2009 at 9:49 PM, Vinayak Borkar <vbo...@yahoo.com> wrote:
Paul,
Thank you for willing to be a mentor.
I have added you as a mentor to the proposal at
http://wiki.apache.org/incubator/VXQueryProposal.
What would be the best way to get more
1. mentors
2. feedback
so we can move the proposal to a vote?
Thanks,
Vinayak
Paul Fremantle wrote:
Yes I am willing to be a mentor.
Paul
On Tue, May 12, 2009 at 7:57 PM, Vinayak Borkar <vbo...@yahoo.com>
wrote:
Paul,
Thank you for your interest in the VXQuery engine. We are looking for
mentors for the project. Would you be willing to be a mentor?
Thanks,
Vinayak
Paul Fremantle wrote:
Synapse would also be interested in using the XQuery implementation!
Thanks
Paul
On Mon, May 11, 2009 at 7:22 PM, Vinayak Borkar <vbo...@yahoo.com>
wrote:
Hello,
We wish to present a proposal to create a new project in the
incubator
called VXQuery. Please find below, the plain-text version of the
proposal.
Any feedback would be greatly appreciated.
Thanks,
Vinayak
VXQueryProposal
Abstract
Apache VXQuery is a language processor that implements the XML Query
Language v1.0 standardized by the W3C.
Proposal
VXQuery (Versatile XQuery) will be a standards compliant XML Query
processor
implemented in Java. We believe that there exists a strong (and
growing)
need to process semi-structured data in many applications. The W3C
standardized v1.0 of the XML Query Language in early 2007. Since
then,
a
few
processors have surfaced (both commercial and open source). VXQuery
will
implement this standard.
VXQuery plans to be the glue that brings together imperative
programming
in
Java and declarative programming in XQuery. The project would enable
developers to use XQuery to navigate and transform application
objects
declaratively in Java applications with minimal overhead.
In the VXQuery project we plan to build an implementation that allows
users
to run declarative XQueries on arbitrary object models. Existing
XQuery
engines execute queries by translating the user data into some form
of
XML
Object model. With VXQuery, we take the opposing view - Translate the
query
to work natively on the user's object model.
In addition, VXQuery works on top of different XML representations
including
DOM, Stax, and a space optimized model motivated by Xalan's DTM
(Document
Table Model).
VXQuery will also provide a library that allows application
developers
to
express declarative queries without the need to learn a new syntax.
We
believe that this will speed up the adoption process.
Current Status
This is a new project.
Meritocracy
The initial developers are very familiar with meritocratic open
source
development at Apache. Apache was chosen specifically because the
initial
developers want to encourage this style of development for the
project.
Community
VXQuery seeks to develop developer and user communities during
incubation.
Core Developers
The core members of the project are diverse. Vinayak Borkar is an
independent consultant. Till Westmann works for a company that would
be
a
potential consumer of VXQuery. During incubation the developers base
will
be
broadened.
Alignment
XQuery is gaining more traction as a XML management technology and
there
already are several Apache projects ([WWW] XMLBeans, [WWW] Camel,
[WWW]
Tuscany) that use or need a XQuery implementation. As no such
implementation
is available as an Apache project these projects have to rely on
external
engines. VXQuery can fill this gap and complement the XML support of
the
Apache Software Foundation.
Known Risks
Orphaned products
VXQuery is new development.
Inexperience with Open Source
The initial developers include long-time open source developers.
Vinayak
Borkar is an active contributor to the Zorba project at the FLWOR
foundation.
Relationships with Other Apache Products
XMLBeans is a representation of XML that would be natively supported
in
VXQuery. Therefore VXQuery can be used as an efficient and
Apache-licensed
implementation for the [WWW] selectPath and execQuery methods found
in
XMLBeans.
Similarly, [WWW] Tuscany's SDO implementation can be natively
supported
and
VXQuery can be used to provide an [WWW] XQuery implementation for
Tuscany.
VXQuery can also be used as an XQuery implementation for [WWW] Camel.
Further, VXQuery uses the Xerces XML parser and schema validator.
A Excessive Fascination with the Apache Brand
We believe in the processes, systems, and framework Apache has put in
place.
Apache is also known to foster a great community around their
projects
and
provide exposure. While these points are important, they are not the
main
motivation for choosing Apache to host VXQuery.
Documentation
Not publicly available
Initial Source
Not publicly available
External Dependencies
[WWW] JavaCC (BSD license), [WWW] Davos SDO implementation (Apache
2.0
license), [WWW] Woodstox XML parser (Apache 2.0 license), [WWW]
XStream
project (BSD license)
Required Resources
Developer and user mailing lists
[MAILTO] vxquery-...@incubator.apache.org [MAILTO]
vxquery-us...@incubator.apache.org [MAILTO]
vxquery-comm...@incubator.apache.org
A subversion repository
[WWW] https://svn.apache.org/repos/asf/incubator/vxquery
A JIRA issue tracker
VXQuery (VXQUERY)
Initial Committers
*
Vinayak Borkar <vborky at yahoo dot com>
*
Till Westmann <till at westmann dot org>
*
Cezar Andrei <cezar at apache dot org> [Have CLA]
*
Michael Carey <mjcarey at ics dot uci dot edu>
Sponsors
*
XMLBeans PMC
Champion
*
Cezar Andrei
Nominated Mentors
*
Looking for mentors
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
