size of XQuery developer community

[Andrew Welch]

>>> lots of money
>>
>> Hmm, Sure. We'd love that, thanks ! :-)
>>
>> But how ?
>> ( This was the subtitle of my original question.....:-)
>
>
> Standardization of the server side containers to allow the majority of
> xqueries to run. For example, don't make the developer rewrite an xquery to
> get a simple request parameter. (perhaps better, don't use XQuery for
> webapps <duck/>)
>
> Push XQuery for what it is good at: querying XML. Integrate XSL natively in
> the XML DB and use that for mixed-content heavy transformations.
>
>  (In the past I have probably beaten this issue into the ground?)

(Yep :) but hopefully it's coming )

The project I work on at the moment takes a load of XML, parses it
into pojos, stores them in a relational db, gets them from the db,
then writes out XML etc...   It would be so much better if an XML
database was used, however because the project architect and majority
of the team have no experience with XQuery and XML databases, that's
the only solution they know.  They argue over things like how easy it
is to "traverse the schema", yet don't seem to realise/understand if
the information was still in XML how much simpler querying the data
would be.




-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/