- From: Janne Saarela <janne.saarela@profium.com>
- Date: Sat, 16 Apr 2005 10:27:02 +0300
- To: public-rdf-dawg@w3.org
let me do some mathematics, too: > I suggest that the primary role of the protocol is to transport query > requests to a server and transfer the results back. It is the role of > the query processor (and hence the QL) to generate and manipulate the > results, result sets included. This is why I don't think DISTINCT, > LIMIT and SORT have a place in the protocol - they happen before > serilization. +1 > Allowing XSLT to be applied is useful for the creation of presentation > but using that as the means to manipulate results breaks the separation, > so will lead to complex interactions (e.g. sorting twice, sorting after > limit applied) now or later. > > > So "OK" to have having an XSLT parameter but "no" to saying that meets > the sorting requirement. +1 Just to give the chair a message that there's strong support of this position. Janne -- Janne Saarela <janne.saarela at profium.com> Profium, Lars Sonckin kaari 12, 02600 Espoo, Finland Internet: http://www.profium.com
Received on Saturday, 16 April 2005 07:27:06 UTC