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

document-uri() problem in XSLT1 schema when generated by XSLT2 engine #4

Open
GoogleCodeExporter opened this issue Mar 17, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Lars Hutter has reported the old problem of stylesheet versions caused some 
problem. See discussion at 
http://www.eccnet.com/pipermail/schematron/2010-July/000295.html   

There are two problems:

1) Should @queryBinding="xslt2" cause a stylesheet with @version="2.0". 

According the draft ISO standard binding for XSLT2, backward compatibility 
should be false. See Annex L, http://www.itscj.ipsj.or.jp/sc34/open/1419.pdf So 
that suggests that certainly 2.0 should be generated. (Need to check it is.)

2) The svrl for saxon script generates  document-uri() function even for 
@queryLanguage="XSLT1" schemas. This is good for people then running the XSLT1 
script on SAXON: it allows better reporting, but will fail on XSLT1 systems.  
Sometimes people cross-compile, for example when the compiled stylesheet will 
run on IE attached to an XHTML document. 

At the moment there is some source code comment to delete document-uri(), but 
this requires hacking which we need to get beyond, even if it is an edge-case. 

Need to figure out better system: a command-line switch is one more thing to 
think about?, some use of xsl:fallback maybe?, or what?

Original issue reported on code.google.com by [email protected] on 10 Jul 2010 at 5:01

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

No branches or pull requests

1 participant