W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2003

RE: SAG-FO-04: fn:trace()

From: Ashok Malhotra <ashokma@microsoft.com>
Date: Mon, 21 Jul 2003 08:16:08 -0700
Message-ID: <E5B814702B65CB4DA51644580E4853FB09840E9C@red-msg-12.redmond.corp.microsoft.com>
To: "Kay, Michael" <Michael.Kay@softwareag.com>, <public-qt-comments@w3.org>

The F&O taskforce discussed this at the meeting on 7/18/2003 and
declined to make the change you suggested.

All the best, Ashok

> -----Original Message-----
> From: public-qt-comments-request@w3.org [mailto:public-qt-comments-
> request@w3.org] On Behalf Of Kay, Michael
> Sent: Tuesday, June 10, 2003 8:50 AM
> To: public-qt-comments@w3.org
> Subject: SAG-FO-04: fn:trace()
> 
> 
> Software AG does not believe that there is any good reason to include
> fn:trace() in the core function library.
> 
> We already have diagnostic features in our product that are much more
> sophisticated and usable than the proposed fn:trace() function. We do
not
> have a sensible way of implementing fn:trace() in our product
> architecture,
> and we believe that as a result of query optimization, the output is
> likely
> to be unintelligible to most users.
> 
> We see no need for diagnostic capabilities to be standardised. This
should
> be an area that is left entirely to implementors to add value.
> 
> We recommend that the fn:trace() function should be dropped, or at
least
> marked as optional.
> 
> Michael Kay
> Software AG
> 
Received on Monday, 21 July 2003 11:16:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:13 UTC