- From: <bugzilla@jessica.w3.org>
- Date: Sun, 07 Feb 2016 03:24:53 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29425 Bug ID: 29425 Summary: [XSLT30] Some AVT's in xsl:result-document seem not defined as such Product: XPath / XQuery / XSLT Version: Candidate Recommendation Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: abel.braaksma@xs4all.nl QA Contact: public-qt-comments@w3.org Target Milestone: --- We say under 25.1 Secondary Results: <quote> With the exception of use-character-maps, these attributes are all defined as attribute value templates,..... </quote> However, @validation, @type, @method and @json-node-output-method are not defined as such. I'm not sure it makes much sense to have @type and @validation as AVT, but for the other two I think it has always been intended to be an AVT. Also, I'm not quite sure what the rationale is for *not* making @use-character-maps an AVT, as I can see trivial use-cases that make having it as AVT a benefit (but being in CR I'm not sure it can be changed). And the fine lines: the standard attributes aren't AVT's either (the only standard attribute that has some meaning as an AVT for xsl:result-document could be [xsl:]exclude-result-prefixes). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 7 February 2016 03:24:55 UTC