- From: Henry Zongaro <zongaro@ca.ibm.com>
- Date: Fri, 15 Oct 2004 16:11:49 -0400
- To: Stephen.Buxton@oracle.com
- Cc: public-qt-comments@w3.org
Steve, In [1], you submitted the following comment on the Last Call Working Draft of XSLT 2.0 and XQuery 1.0 Serialization. << SECTION 4: XML output method Last sentence concludes with "...if nodes in the model contain characters that are invalid in XML (introduced, perhaps, by calling a user-written extension function: this is an error but the processor is not required to signal it)." It is not clear what is meant by "processor". Does this refer to the XQuery engine that invoked the user-written extension and thereby obtained a corrupt value, or does it refer to the XML output method? Probably the former, since there does not appear to be any provision for calling user-written functions from the output method. This could be fixed by changing "processor" to "XQuery processor". >> Thank you for your comment, which I am handling editorially. In response to your comment, and at the suggestion of Michael Kay, I've introduced a new term: serializer. That term is now used throughout the specification. The only two remaining instances of "processor" are qualified and refer to XML processors and XSLT processors. I would appreciate if you could check the next draft of the specification when it becomes available, and verify that this new term and its definition satisfactorily address your comment. Thanks, Henry [1] http://lists.w3.org/Archives/Public/public-qt-comments/2004Feb/0935.html ------------------------------------------------------------------ Henry Zongaro Xalan development IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044 mailto:zongaro@ca.ibm.com
Received on Friday, 15 October 2004 20:12:25 UTC