-
Notifications
You must be signed in to change notification settings - Fork 19
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
repairing XSD simple type definition defect #227
Merged
david-waltermire
merged 1 commit into
usnistgov:develop
from
wendellpiez:issue223-xsd-datatype-bugA
Aug 23, 2022
Merged
repairing XSD simple type definition defect #227
david-waltermire
merged 1 commit into
usnistgov:develop
from
wendellpiez:issue223-xsd-datatype-bugA
Aug 23, 2022
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
david-waltermire
approved these changes
Aug 21, 2022
…ns down their dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation.
david-waltermire
force-pushed
the
issue223-xsd-datatype-bugA
branch
from
August 21, 2022 04:39
4316dae
to
59e6543
Compare
david-waltermire
pushed a commit
that referenced
this pull request
Dec 7, 2022
…heir dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation. (#227)
aj-stein-nist
pushed a commit
to aj-stein-nist/metaschema
that referenced
this pull request
Jan 9, 2023
…ns down their dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation. (usnistgov#227)
aj-stein-nist
pushed a commit
to aj-stein-nist/metaschema
that referenced
this pull request
Jan 10, 2023
…ns down their dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation. (usnistgov#227)
aj-stein-nist
pushed a commit
to aj-stein-nist/metaschema
that referenced
this pull request
Jan 10, 2023
…ns down their dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation. (usnistgov#227)
aj-stein-nist
pushed a commit
to aj-stein-nist/metaschema
that referenced
this pull request
Jan 10, 2023
…ns down their dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation. (usnistgov#227)
aj-stein-nist
pushed a commit
to aj-stein-nist/metaschema
that referenced
this pull request
Jan 10, 2023
…ns down their dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation. (usnistgov#227)
aj-stein-nist
pushed a commit
to aj-stein-nist/metaschema
that referenced
this pull request
Jan 10, 2023
…ns down their dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation. (usnistgov#227)
david-waltermire
pushed a commit
that referenced
this pull request
Mar 9, 2023
…heir dependency graph (within a given set of definitions), preventing orphans when atomic datatypes are built on top of one another in XSD generation. (#227)
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.
In XSD generation, generated XSDs are defective when simple (atomic) types defined by OSCAL make references to other simple types -- the indirectly referenced OSCAL types (such as DateTimeWithTimeZone as a subtype of DateTime) are missing.
The XSD generation now revisits the list of types as many times as necessary to get the full list of all types referenced indirectly, from any given list (such as those referenced directly).
Committer Notes
XSD generation will be identical except when such dependent types are used.
All Submissions:
Changes to Core Features: