W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2014

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Jan 2014 18:37:00 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24234-523-SOl4y0lb3H@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24234

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
If I compare the text with the related one from xsl:output (error XTSE1560),
then that error is clearer in its description: it says "if two xsl:output
declarations within an output definition specify explicit values for the same
attribute ".

It is this difference that is confusing. When for XTSE0545 we say "values",
without specifying whether that's implicit or explicit, I checked comparable
errors, where in the case of XTSE1560 the term "explicit values" is mentioned.
This led me to deduct that xsl:mode behaved different than xsl:output in
conflict resolution.

I suggest we simply change "values" into "explicit values" (for XTSE1560) to
make this ambiguity go away.

Note: our current implementation mistook the meaning of the error, failing some
tests, which ultimately led to this bug-report.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 14 January 2014 18:37:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:45 UTC