What would be a use case for such a new service? Doesn't this mean that we move this logic from the middle tier to the database backend?
I think you just stated the use case :-) To many, XSLT is a less-confusing alternative to XQuery. Several NXDs are already doing internal XSLT transformations, and so such a Service would create a common way to interface with those capabilities.
For example, dbXML provides parameterized calling of pre-interpreted XSLT queries as well as being about to transform the results of both single documents and result sets from other queries. It is especially important to do this type of transformation at the database level to reduce the bandwidth requirements of processing such potentially large data sets.
What would be nice to do is audit the current offerings (X-Hive, eXcelon, Tamino, dbXML) and see how they expose their XSLT capabilities, so we can nail down common functionality. Would any of company people on the list like to share?
-- Tom Bradford - http://www.tbradford.org/ CTO - The dbXML Group - http://www.dbxml.com/ Apache Xindice - http://xml.apache.org/xindice
---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
