Re: ORA-SE-300-B: Implementation-defined output methods need not normalize

Steve,

     In [1], you submitted the following comment on the Last Call Working 
Draft of XSLT 2.0 and XQuery 1.0 Serialization:

<<
SECTION 3: Serialization parameters

It says "The method identifies the overall method...
If the QName is in a namespace, then it identifies an 
implementation-defined output method; the behavior in this case 
is not specified by this document."  However, you have specified
that normalization (section 2) occurs prior to invoking the 
method.  This implies that the implementation-defined method
has no control over the normalization.  It would be desirable to
reverse this, so that normalization occurs inside the method
rather than prior to the method.  In that case, normalization
would be part of the standard-defined methods but 
implementation-defined methods might have other algorithms
for dealing with values permitted by the data model that do
not correspond to well-formed XML.

To accomplish this, simply make the current section 2 into 
the first phase, prior to "Markup generation".
>>

     Thank you for this comment.

     The XSL and XML Query Working Groups discussed your comment, and 
agreed that implementation-defined output methods should be granted 
control of whether the normalization of arbitrary sequences that is 
specified by section 2 occurs.

     As a representative of Oracle was present when this decision was 
made, I will assume the response is acceptable to you.

Thanks,

Henry [On behalf of the XSL and XML Query Working Groups]
[1] 
http://lists.w3.org/Archives/Public/public-qt-comments/2004Feb/0921.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 Tuesday, 13 July 2004 13:00:37 UTC