XQuery as a general data processing language WAS: [xquery-talk]XQuery and Web 2.0

Peter Coppens pc.subscriptions at gmail.com
Sat Apr 26 02:06:51 PDT 2008

On 26 Apr 2008, at 00:37, Michael Kay wrote:

>> Anyway, XQuery was designed to 'work' on the XQuery/XPath
>> data model and I don't believe anywhere anytime soon your
>> 'typical' developer/architect/ designer will choose XDM as
>> its main representation of information to implement
>> (transactional business) logic upon.
> You may be right, but it's a shame, because XML is often a much  
> better way
> of representing business information than the two main alternatives,
> relational tables and Java objects. That's because it can handle the  
> softer,
> fuzzier, more variable information that traditional applications  
> leave out
> on the grounds that traditional technology can't cope with it.
Yes...I can certainly see your point. So would an attempt to better  
integrate the oo and xml programming and data models not be a valid  
approach? Is that not what has (or is) happening with oo and  
relational data? For a lot of use cases EJB3 seems to be working fine,  
or is the analogy flawed?

More information about the talk mailing list