2697 2006-01-11 18:49:42 +0000 [Ser] xml version not supported by serializer 2006-02-01 15:07:41 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Serialization 1.0 Candidate Recommendation All All CLOSED FIXED P2 normal --- 1 joannet joannet public-qt-comments oldest_to_newest 7781 0 joannet 2006-01-11 18:49:42 +0000 The fourth paragraph in section 16.1 (XML Output Method) in XSLT 1.0 specification reads: "The version attribute specifies the version of XML to be used for outputting the result tree. If the XSLT processor does not support this version of XML, it should use a version of XML that it does support. ..." The description of the version attribute in XSLT 2.0 section 20 reads: "The value of the version attribute provides the value of the version parameter to the serialization method. The set of permitted values, and the default value, are implementation-defined. A serialization error will be reported if the requested version is not supported by the implementation." The serialization specification defines no such error code when the version requested is not supported by the serializer. I can think of 3 possible solutions: 1: XML version value is silently ignored if not supported (align with XSLT 1.0) 2: add a new error code in Serialization when the XML version value is not supported (align with XSLT 2.0) 3: add a sentence in Serialization that it's up to the host language whether an error is thrown if the XML version value is not supported. original comment raised in the members mailing list: http://lists.w3.org/Archives/Member/w3c-xsl-wg/2005Oct/0048.html 7959 1 joannet 2006-01-24 16:06:28 +0000 When the serializer encounters other serialization parameters that are not supported, the specification currently says: encoding: recoverable by using UTF-8 or UTF-16 or signal err:SESU0007 method: both Serialization and XSLT 2.0 say "the behavior in this case is not specified by this document." normalization-form: serializer MUST signal err:SESU0011 8082 2 joannet 2006-02-01 15:06:05 +0000 The XSL and XQuery working group decided on Feb 1, 2006 to accept option 2 in the suggested resolution. A serialization error will be added to the specification. The rationale is to align with other parameters, where an error is thrown if the parameter value is not supported by the serializer.