1233 2005-04-09 08:39:08 +0000 [XSLT] Parameterizing Serialization 2005-09-28 12:27:22 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 2.0 Last Call drafts PC Windows XP CLOSED FIXED http://lists.w3.org/Archives/Public/public-qt-comments/2005Apr/0034.html P2 normal --- 1 mike mike public-qt-comments oldest_to_newest 3847 0 mike 2005-04-09 08:39:08 +0000 Andre Cusson raised this directly on public-qt-comments, I am copying it here (follow the URL) for tracking purposes. 3717 1 mike 2005-04-28 18:16:14 +0000 Thankyou for the comment. The XSL WG reviewed it today and decided that we want to keep the ability for xsl:result-document to override individual serialization parameters at run-time, for example based on the values of stylesheet parameters, and that reducing this to the ability to reference a fixed bundle of parameters defined in an xsl:output declaration would be a backwards step. WG members reported that experience has shown that this facility is useful. Your comment was transferred from the public-qt-comments list to the Bugzilla database at http://www.w3.org/Bugs/Public/show_bug.cgi?id=1233 Please let us know if you agree with this resolution of your issue, by adding a comment to the issue record and changing the Status of the issue to Closed. Or, if you do not agree with this resolution, please add a comment explaining why. If you wish to appeal the WG's decision to the Director, then also change the Status of the record to Reopened. If you wish to record your dissent, but do not wish to appeal the decision to the Director, then change the status of the record to Closed. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision. 3719 2 ac 2005-04-28 19:57:37 +0000 The proposition is not meant to replace the individual override serialization parameters but to allow more efficient use of preset output formats, the two approaches being complementary. The current solution limits the use of presets and forces a recourse to many individual parameters and the corresponding application variables. The only required change is that the output format name should be a computable string instead of a literal QName. The example provided compares 3 approaches to a common problem showing some of the differences. We agree that individual override parameters are very useful but selecting what they can override and using output presets is also very useful, as well as in-line with the language spirit and constructs, and all that is required is to reduce some restrictions on the result-document format attribute, also making it similar to most other parameters. Thank you. ac. 6520 3 mike 2005-09-28 12:27:07 +0000 The XSL WG decided today to accept this comment. The format attribute of the xsl:result-document will be allowed to be an attribute value template. The individual seialization attributes of xsl:result-document will continue to be allowed, and will override anything specified on the corresponding xsl:output declaration. Since we have accepted the comment, we are closing the bug.