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

Writing XSDs in US-ASCII #165

Merged

Conversation

wendellpiez
Copy link
Collaborator

@wendellpiez wendellpiez commented Jun 11, 2021

Committer Notes

This (re)configures serialization in the main make-metaschema-xsd.xsl XSLT (and in the debug XProc for reference). Setting encoding to emit US-ASCII provides for expressing all out-of-ASCII Unicode as (escaped) Unicode character references.

The PR addresses usnistgov/OSCAL#956.

All Submissions:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Have you squashed any non-relevant commits and commit messages? [instructions]
  • Do all automated CI/CD checks pass?

Changes to Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you included examples of how to use your new feature(s)?
  • Have you updated all website](https://pages.nist.gov/metaschema) and readme documentation affected by the changes you made? Changes to the website can be made in the website/content directory of your branch.

Copy link
Collaborator

@david-waltermire david-waltermire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@david-waltermire david-waltermire merged commit 72cd8c5 into usnistgov:master Jun 14, 2021
wendellpiez added a commit to wendellpiez/metaschema that referenced this pull request Feb 23, 2022
…e no upper-Unicode characters in the schema to be concerned about.
wendellpiez added a commit to wendellpiez/metaschema that referenced this pull request Mar 22, 2022
…e no upper-Unicode characters in the schema to be concerned about.
david-waltermire pushed a commit that referenced this pull request Apr 15, 2022
* Redefined lexical constraint on 'token' datatype - #181 - removing references to upper-Unicode characters that break at least one processor - this is not actually relaxed, since the exclusion tests out as inoperative (the offending characters are not in the sets from which they are being excluded)
* Rolling back #165 addressing usnistgov/OSCAL#956. We now have no upper-Unicode characters in the schema to be concerned about.
* Adding schema-generation unit tests for 'token' datatype
* Adjusted JSON Schema generation to capture latest datatype definitions #195
* Debugging path in datatype integration
* Adding XSD datatype production logic - reads and rewrites JSON definitions in XSD syntax.
* Adjustment to JSON -> XSD rough casting
* XSD datatypes adjusted to align with JSON #195
* Adding new datatypes as aliases for old names #1186
* Touchups to inline documentation (for propagation to tools)
* Replaced with updated mapping plus adjustments to XSD production
* Now doing a better job excluding unneeded datatype (simpleType) definitions
* Reconciled datatype merge to emit functional JSON schemas
* Removing safety backups; small correction to Metaschema Schematron to avoid a runtime error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants