-
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
XSD datatype glitch in XSLT M4 schema generator #223
Comments
Current plan:
Then we have a start at #224 (exposing the regex issues). |
…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.
Actually - the bug found and repaired for #227 may not be this one, at least as described in this Issue (which was transcribed from a note). TBD. |
…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.
@wendellpiez The specific error can be verified by validating the OSCAL catalog XML schema. |
The schema generated from adjusted XSD comes up without errors, and the diff shows new structures (only). Thanks @david-waltermire-nist for the reference point. |
…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)
…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)
…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)
…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)
…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)
…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)
…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)
…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)
…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)
Describe the bug
For whatever reason, derived datatypes are not capturing their base types in the generated XSDs (XSLT M4 implementation,
develop
branch). For example,dateTime-with-timezone
should be defined as a restriction ondateTime
, but is coming through as a restriction onstring
.Who is the bug affecting?
Downstream users of the XSD who do not have correct data type bindings.
What is affected by this bug?
Difficult to determine, but this has potential impacts on XSD-based applications.
When does this occur?
Reliably on certain datatypes in OSCAL (that are derived by restriction).
How do we replicate the issue?
Examine any generated schema.
Expected behavior (i.e. solution)
Schemas should reflect the derivation of the type, not erase it.
The text was updated successfully, but these errors were encountered: