Make the default XPath version implementation defined #1092
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gimsieke
requested changes
Apr 14, 2024
xproc/src/main/xml/specification.xml
Outdated
| pipelines or libraries declare different XPath versions, it is | ||
| <glossterm>implementation-defined</glossterm> how those conflicts are resolved.</impl> | ||
| An implementation might use different versions for different pipelines, or it might | ||
| use the same version for all pipelines. <impl>If an implementation elects to us the |
|
I think this is a good solution for the inheritance problem. But I am not sure how it covers the problem when the pipeline is asking for an XPath version not supported by the processor. Does this PR suggest the reaction as implementation-defined? |
|
Fixed the typo. Extended |
gimsieke
approved these changes
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes issue 39 in the vnext repository.