[Bug 24234] Unclear resolution of default attributes for named modes and error XTSE0545

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24234

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
On the first point, I agree. For named modes we should add the statement that
the effective value is the default value if no value is specified.

One the second point, I think that conflicts should only be reported between
explicit attribute values. That's what the spec currently says (it talks about
the "values" of the attributes, not the "effective values"), and I think it's
the right thing to say. It's consistent with other declarations that allow the
attributes to be spread across multiple declarations (such as xsl:output and
xsl:decimal-format). There's no point in allowing multiple declarations of a
mode at the same import precedence if we require all information on one of the
declarations to be exactly replicated in the others.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 13 January 2014 20:52:58 UTC