[XQuery Talk Mailing List Archive Home] [By Date] [By Thread] [By Subject] [By Author] [Recent Entries] [Reply To This Message]

What is XQuery doing wrong and why does it get ignored !?

Daniela Florescu dflorescu at mac.com
Thu Jul 22 00:51:55 PDT 2010


  What is XQuery doing wrong and why does it get
	ignored !?
>
> On the other hand, when you look at something like C# 3+ and LINQ, or
> Python with its list comprehensions, or Ruby, or any "mainstreamized"
> FP language (F#, Clojure), or some of the rising stars (Scala) - when
> querying over the corresponding native object models (i.e. ADT trees
> or OO graphs, respectively), their syntax is not all that verbose. VB
> and Scala even have XML literals out of the box - not on par with
> XQuery, mind you, but good enough for 90% of cases.

Beg to differ about the 90%.  That's the 90% XML users who don't  
understand XML,
and just put angle brackets all over.

What about the complex enterprise schemas ?

What if I have to process HL7 ? Or XBRL ? Or NIEM ? ACORD ? NavyXML ?
CIDX ? GML ? MISMO ? US_GAAP? SVG ?

Good luck to whoever tries to process those with C#, Python, or  
whatever else,
closures, or not closures.

>
> Performance behavior is predictable

Yes, imperative languages's performance is predictable, and  
predictably bound to be low :-)

Sorry, could not resist...

>
>
> In XQuery, I have to jump through hoops with
> closures to return two sequences from a function (and then pray that
> the optimizer of my implementation can special-case that trick!), and
> that's for the draft 1.1

OK. You identified problem #1. Lack of structures.


I can't describe types in XQuery
> itself,

OK. Problem #2.

but the lack of type polymorphism is also limiting for a
> language with explicit type declarations.

Ok. Problem #3.

>
> Still, I guess, ultimately it boils down to this: if you want XQuery
> to be more popular, you have to convince people that XML (XDM, really)
> is _the_ way to represent data

I think it is. And I'll tell you why. It's NOT because it's a great  
data model,
far from that. Not in my worst database nightmare I wouldn't have  
designed
something like  XDM.

But it's "good enough"  to generalize all the other ones (relational,  
RDF, JSON,
documents).

And it's there, and unavoidable, and  that's the main advantage.


> . Everything else is secondary.

I agree. Everything else is secondary.


Best regards
Dana
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://x-query.com/pipermail/talk/attachments/20100721/4bdac3de/attachment-0001.htm


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.