- From: Jonathan Robie <jonathan.robie@datadirect.com>
- Date: Tue, 14 Sep 2004 07:45:19 -0400
- To: Martin Duerst <duerst@w3.org>
- CC: "Public >> XML Query Comments" <public-qt-comments@w3.org>, w3c-i18n-ig@w3.org
Thanks, Martin! Jonathan Martin Duerst wrote: > Hello Jonathan, > > The I18N WG (Core TF) has decided that we are okay with your > disposition on this issue. > > Regards, Martin. > > At 17:58 04/08/24 -0400, Jonathan Robie wrote: > >> Hi Martin, >> >> This is a response from the XML Query Working Group, which has >> considered the following comment: >> >> http://lists.w3.org/Archives/Public/public-qt-comments/2004Feb/0415.html >> >>> [19] There should be a way to character normalize nodes (not only >>> strings). This could easily be achieved by overloading >>> fn:normalize-unicode. This will help in cases where >>> otherwise fn:normalize-unicode would have to be used all over >>> the place. >> >> >> First off, we would like to remark that in a side-effect free >> functional language like XQuery, it is not possible to change an >> existing node, though it is possible to make a modified copy of an >> existing node. We currently have no functions that make a copy of an >> entire sub-tree, modified or unmodified, though users certainly write >> functions that modify subtrees in various ways. The functionality you >> propose might be achieved by writing such a function and placing it in >> a function library. >> >> On the other hand, we are not completely certain of your usage >> scenario, and it is also likely that much of what you need might >> better be acccomplished by specifying serialization parameters for >> serializing the results of a query. >> >> Please let me know if you feel this resolution is unacceptable. >> >> Thanks! >> >> Jonathan >> >> On behalf of the XML Query Working Group > >
Received on Tuesday, 14 September 2004 11:45:54 UTC