[Bug 2420] xsl:message treats a colision of select attribute and sequence-constructor in contentare different from other elements

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Bug 2420] xsl:message treats a colision of select attribute and sequence-constructor in contentare different from other elements

bugzilla (Bugzilla)-14

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2420


[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |LATER




------- Additional Comments From [hidden email]  2005-10-31 13:14 -------
This isn't a bug in the spec: it was a conscious design decision, though one
that you are free to disagree with.

The reason it was done this way is that xsl:message is used mainly for
diagnostics, and it was thought undesirable that a diagnostic facility should
itself produce errors. Furthermore, one of the reasons that other instructions
aren't allowed to have both a select attribute and a content body is that it's
not obvious how the two should be ordered in the output; for xsl:message the
resulting order is likely to be of little consequence.

I've classified this as "LATER" so the WG will come back to it at some stage.

Michael Kay
personal response.