This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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).
(1) validation and type are not included in the list in the previous paragraph, this rule does not apply to them. (2) method was allowed as an AVT in 2.0, it appears to be an editorial mistake that this is not the case in 3.0 and we need to fix this (3) json-node-output-method was copy-and-pasted from the method attribute and inherited this error; this should also be fixed. RESOLVED that method and json-node-output-method should be AVTs.
The changes have been applied.