Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XTSE0090: Attribute @format is not allowed on element <xsl:result-document> #7

Open
mrft opened this issue Jul 28, 2015 · 1 comment

Comments

@mrft
Copy link

mrft commented Jul 28, 2015

When adding an xsl:result-document element to my stylesheet that contains a format attribute (for selecting the output method), this is the error returned:

SaxonCE.StandardErrorListener 17:08:16.652
SEVERE: Error at /xsl:stylesheet/xsl:template[2]/xsl:choose/xsl:when[1]/xsl:result-document in 
  XTSE0090: Attribute @format is not allowed on element 

but if I am reading the xslt 2.0 spec correctly about xsl:output and xsl:result-document this should be possible.

Is this a bug or a mistake on my part?

@michaelhkay
Copy link
Member

There’s no serializer in Saxon-CE, so the format attribute doesn’t make much sense (nor do the serialization attributes like indent and the like). For conformance I suspect the format attribute should be accepted and ignored (or validated and then ignored) but it looks like there’s an oversight in the code and it doesn’t do this.

Michael Kay
Saxonica

On 28 Jul 2015, at 16:16, mrft notifications@github.com wrote:

When adding an xsl:result-document element to my stylesheet that contains a format attribute (for selecting the output method), this is the error returned:

SaxonCE.StandardErrorListener 17:08:16.652
SEVERE: Error at /xsl:stylesheet/xsl:template[2]/xsl:choose/xsl:when[1]/xsl:result-document in
XTSE0090: Attribute @Format is not allowed on element
but if I am reading the xslt 2.0 spec correctly about xsl:output http://www.w3.org/TR/xslt20/#element-output and xsl:result-document http://www.w3.org/TR/xslt20/#element-result-document this should be possible.

Is this a bug or a mistake on my part?


Reply to this email directly or view it on GitHub #7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants