[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Why *is* XQuery taking so long?

• To: 'Jonathan Robie' <jonathan.robie@d...>
• Subject: RE: Why *is* XQuery taking so long?
• From: "Bullard, Claude L (Len)" <len.bullard@i...>
• Date: Fri, 15 Oct 2004 12:00:30 -0500
• Cc: 'Michael Champion' <michaelc.champion@g...>, "'xml-dev@l...'" <xml-dev@l...>

It's still worth it if the learning curve is retained.

A small team can put a small craft into 
sub-orbital flight at lower costs.  But 
the composites and display systems came of 
having a big team do it first at very high costs.  

That's progress.  "It don't come easy" or cheap 
the first time, and if the progress isn't replicable, 
the second time either.  It will be interesting 
to see what the W3C does to learn, remember, and 
reapply.   We're in that same mode at the W3DC.

len


From: Jonathan Robie [mailto:jonathan.robie@d...]

Bullard, Claude L (Len) wrote:

> But understand the audience and don't play Bach if they came 
> to boogie. Could XQuery have come out in successive versions 
> with simpler accompaniment? 

We now know that we could have done most of the type work later, 
releasing a dynamically typed language and adding the static typing in a 
subsequent release. The awful fact is, we couldn't know that for sure 
until after the static typing was done.

And I think we could have been done 1 to 2 years earlier if we had 
learned the lessons we now know about process on a complex spec with 
lots of players and lots of industry interest. The awful fact is, we had 
to flounder a while to figure some of this out.

Jonathan

• Prev by Date: Re: Why *is* XQuery taking so long?
• Next by Date: [ANN] <oXygen/> XML Editor version 5.0
• Previous by thread: Re: Why *is* XQuery taking so long?
• Next by thread: RE: Why *is* XQuery taking so long?
• Index(es):
  • Date
  • Thread