29795 2016-08-26 19:03:43 +0000 [XSLT30] (editorial) Option parameter conventions (section 22.2 Options) 2016-10-06 18:42:27 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Member-only Editors Drafts PC Windows NT CLOSED FIXED P2 editorial --- 1 abel.braaksma mike public-qt-comments oldest_to_newest 127242 0 abel.braaksma 2016-08-26 19:03:43 +0000 As a resolution of bug 29602 a new section was added (22.2 Options) that mimics section 1.5 Options from the F&O 3.1 specification. I find it oddly placed, in between extra XSLT functions on handling JSON. While it is true that currently only one function requires "option parameter conventions", its intended meaning is wider, and could be adopted in extension functions (i.e., think EXPath or vendor extensions). I'd like to do the same as in F&O (where it is placed near the top) and place it somewhere near the introduction material, for instance as a subsection under "2 Concepts", which has more such information that applies generally to the whole specification. Marked editorial, as I don't think there's anything wrong per se. 127243 1 abel.braaksma 2016-08-26 19:05:27 +0000 In addition, both for F&O and XSLT, I find the section title "Options" rather generic and its intent is not clear from the title. I.e., calling it "Option parameters" or "Option parameter conventions" seems more substantive and to the point. 127253 2 mike 2016-08-28 11:29:17 +0000 I have changed the title of the section to "Option Parameter Conventions". I'm going to leave it where it is in the document; if the option parameter conventions are ever used for more than one XSLT-defined function, I think it is almost certain that we will be able to drop this section and refer to the F+O 3.1 version. So long as it's only used for one function, I think it makes sense to put it near that function.