[xquery-talk] set as datatype in xquery

Rob Stapper r.stapper at lijbrandt.nl
Sun Jul 19 10:47:22 PDT 2015

That’s clear. 


I’m doing my work which is based on the results of the work done by W3C, also partly funded, partly voluntary. We can’t be all working on the same subject.


I hoped that since the specifications of the array is an extension of those of the dataset, the implementation would be a quick win and not so much of a kludge.

If the choose is between another ad-hoc implementation of a collection type, which in itself isn’t  ad hoc, or the suggested workaround I also would offer the workaround.

Until the framework is ready for generic collection types and the dataset hopefully will be implemented, I’ll be using my own work-around.( no array anyway J)


One could perhaps make a start with the specifications of the dataset.


Rob Stapper


Van: talk-bounces at x-query.com [mailto:talk-bounces at x-query.com] Namens Michael Kay
Verzonden: zondag 19 juli 2015 15:36
Aan: Rob Stapper
CC: talk at x-query.com
Onderwerp: Re: [xquery-talk] set as datatype in xquery



Sure I can do that because after all an array is a glorified dataset. But I won’t J.

Question is: does the W3C as a standardization-organization, want its product to settle for a workaround like that?



The answer is yes.


If we still had 40 people taking an active part in the development process, we would probably be more ambitious. But it’s down to a handful, and you have to set your work programme so it can be achieved with the resources available. Remember the work is not done by W3C as some faceless entity, it is done by individuals whose work is in some cases funded by their companies and in some cases entirely voluntary. If you want to know why they aren’t doing this work, first ask why you aren’t doing it.


Adding arrays to the data model was in many ways a kludge. We would have much preferred to have done a generic collection capability where operations like FLWOR expressions applied to any kind of collection, rather than each kind of collection having its own functions and operators. But it was too hard and too disruptive, so we settled for doing it as a bolt-on. Without the underpinnings of a generic collections framework in the language, we certainly wouldn’t want to add more ad-hoc collection types.


Michael Kay



Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://x-query.com/pipermail/talk/attachments/20150719/0ab3dddc/attachment.html>

More information about the talk mailing list