451: Schema compatibility - #635
Merged
Merged
Conversation
michaelhkay
force-pushed
the
Issue451-multiple-schemas
branch
from
September 28, 2023 10:19
f214500 to
b986bd4
Compare
Contributor
Author
|
I have updated the PR mainly to eliminate merge conflicts; but at the same time I have revised XDM §2.8.3 to bring it up to date; in particular the derived types |
michaelhkay
force-pushed
the
Issue451-multiple-schemas
branch
from
October 10, 2023 20:22
c83f40b to
67b06cf
Compare
michaelhkay
force-pushed
the
Issue451-multiple-schemas
branch
from
October 18, 2023 11:54
67b06cf to
15f193b
Compare
Contributor
|
The CG agreed to accept this PR at meeting 051 |
michaelhkay
force-pushed
the
Issue451-multiple-schemas
branch
from
October 24, 2023 17:36
15f193b to
2ee2cd8
Compare
Contributor
Author
|
The proposal was accepted by the CG on 24 Oct. A new version has been pushed to remove merge conflicts. |
ChristianGruen
approved these changes
Oct 26, 2023
Closed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR addresses part (not all) of issue 451.
It recognises that an application may use more than one schema; for example in a pipeline using multiple stylesheets, it must be possible for the first stylesheet to produce valid output that is valid input to the second, without requiring that the two stylesheet have absolutely identical schema imports. It recognises that there are cases (for example involving substitution groups) where two schemas X and Y may both include the same type T, but produce different results when an element is validated against T. So it defines a concept of schema compatibility and defines its limitations, especially on the semantics of item types such as
element(*,T)andschema-element(E). The rules for schema compatibility between different modules of a query and between different packages in a stylesheet are tightened up and brought into line with each other.