Lists Home |
Date Index |
Jonathan Robie wrote:
> I am all ears on this. Personally, I would think it would be particularly
> interesting to hear feelings about:
> 1. An XQuery 1.0 CR this summer, with a separate CR for updates six months
> 2. An XQuery 1.0 CR a year from now including updates.
> This is really the crucial question. Personally, I do not think that
> waiting a year or two for updates would be a good option.
I would much rather see XQuery without updates sooner than XQuery with
updates later. I can't see how it's a bad thing. It gives people
something to start implementing and using now, so by the time updates
come along, people are ready.
Furthermore, there is a nice logical separation between reading data and
manipulating data, so updates are a good feature to put in a separate
release. There is some risk they will require changes to basic
syntax/underlying formalisms, but the fact that people are already
working on update languages will (hopefully) minimize this risk.
I would also say that we've been down this path before. DOM shipped with
less than "complete" functionality through its various levels and hasn't
exactly had people screaming in pain. (Some discomfort, yes, but severe
pain, no.) On the other hand, XML Schemas waited until several models of
kitchen sinks were added and didn't exactly get kudos for timeliness or