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

XSLT profile resolver does not work with Saxon version 11 #1629

Closed
galtm opened this issue Jan 28, 2023 · 3 comments
Closed

XSLT profile resolver does not work with Saxon version 11 #1629

galtm opened this issue Jan 28, 2023 · 3 comments
Assignees
Labels

Comments

@galtm
Copy link
Contributor

galtm commented Jan 28, 2023

Describe the bug

The XSLT profile resolver errors out with Saxon version 11. See the comments in #1596 .

Who is the bug affecting

Users of the XSLT profile resolver who want to use version 11 or later of the Saxon XSLT engine.

What is affected by this bug

Tooling & API

How do we replicate this issue

java -cp path-to-saxon/saxon-he-12.0.jar net.sf.saxon.Transform -xsl:oscal-profile-RESOLVE.xsl -s:path-to-profile.xml -o:resolved-catalog.xml

Error message:

Type error at char 50 in expression in xsl:variable/@select on line 49 column 89 of oscal-profile-resolve-metadata.xsl:
  XTTE0570  An empty sequence is not allowed as the value of variable $source-profile
at variable source-profile on line 49 column 89 of oscal-profile-resolve-metadata.xsl

Expected behavior (i.e. solution)

Command should produce a catalog file, resolved-catalog.xml

Other comments

Works with Saxon 10 but not 11 or 12. See https://saxonica.plan.io/issues/5339 for information about changes in document-uri function in Saxon 11.

@galtm
Copy link
Contributor Author

galtm commented Jan 28, 2023

@wendellpiez / @aj-stein-nist : Please assign this issue to me.

@nikitawootten-nist
Copy link
Contributor

Update: #1685 has been merged, need to get an update from @aj-stein-nist about this issue being closable.

@aj-stein-nist
Copy link
Contributor

Update: #1685 has been merged, need to get an update from @aj-stein-nist about this issue being closable.

Closable to me, marked it done.

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

No branches or pull requests

3 participants