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

Contradiction between core specs and step core regarding errors #955

Open
xml-project opened this issue Feb 19, 2020 · 3 comments
Open

Contradiction between core specs and step core regarding errors #955

xml-project opened this issue Feb 19, 2020 · 3 comments

Comments

@xml-project
Copy link
Contributor

@xml-project xml-project commented Feb 19, 2020

As @gimsieke obsevered in one of his comments to issue xproc/3.0-steps#355 the example for xslt error in the core specs has no error code, but the specs for p:xslt in the step library clearly states:

  • It is a dynamic error (err:XC0095) if an error occurred during the transformation.

  • It is a dynamic error (err:XC0096) if the transformation is terminated by XSLT message termination.

So the c:error element in the core spec example clearly needs an error code.

@ndw

This comment has been minimized.

Copy link
Contributor

@ndw ndw commented Feb 19, 2020

My expectation, for better or worse, is that the underlying error code generated in the stylesheet will percolate up to the c:error element. So maybe err:XC0095 can never occur since there must have been an underlying error?

@xml-project

This comment has been minimized.

Copy link
Contributor Author

@xml-project xml-project commented Mar 18, 2020

The problem in two paragraph: On value templates we say:

It is a static error if the string contained between matching curly brackets in a value template, when interpreted as an XPath expression, contains errors. The error is signaled using the appropriate XPath error code.
It is a dynamic error (err:XD0050) if the XPath expression in a value template can not be evaluated.

So: @gimsieke and @ndw are right concerning a static error in the XPath expression (its an error code in the XPath error namespace), but I am right an any dynamic error because it is in the XProc error namespace.
We have to clean this up and remove all XProc errors covering underlying errors.

@ndw

This comment has been minimized.

Copy link
Contributor

@ndw ndw commented Mar 25, 2020

We're going to change value templates so that we return an XProc error.
We're going to add a new attribute to c:error so that an underlying error code can be returned.

@ndw ndw transferred this issue from xproc/3.0-steps Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.