- From: Michael Rys <mrys@microsoft.com>
- Date: Tue, 14 Oct 2003 13:21:54 -0700
- To: "Erik Bruchez" <erik@bruchez.org>, "Kay, Michael" <Michael.Kay@softwareag.com>, <public-qt-comments@w3.org>
> -----Original Message----- > From: public-qt-comments-request@w3.org [mailto:public-qt-comments- > request@w3.org] On Behalf Of Erik Bruchez > Sent: Tuesday, October 14, 2003 12:47 PM > To: Kay, Michael; public-qt-comments@w3.org > Subject: Re: Missing functions in XQuery 1.0 and XPath 2.0 Functions and O > perators > > > > Obviously there are hundreds (thousands!) of functions that we could > > have included but have not. We have consciously tried to keep the > > library as small as possible, and in fact some people complain that > > it is already much too large compared with XPath 1.0. > > I guess the approach I would have chosen would have been to look at > existing libraries, for example the Java String and Pattern/Matcher > classes, and try to match the functionality available there (which is > there most of the time for a reason). > So let's all just implement the functions of XPath 1.0 (since we need them for backwards-compatibility). Then, should we use the Perl functions, or the Java functions, or the C/C++/C# functions, or the SQL-functions or the EXSLT functions and/or... The point is that we attempt to design a function library that provides the minimal support necessary to provide interoperability among implementation. If you add too many functions, you will not get achieve that and you will add to the delay of the spec... Note that there is nothing that forbids us to add more functions later or encourages implementers to provide additional functions in their implementation which then can be used to gather information about their usefulness. This then can be used to determine future extensions of the function library... Best regards Michael
Received on Tuesday, 14 October 2003 16:21:58 UTC