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

Update Schematron composition check to formally deprecate old datatypes #107

Open
10 tasks
aj-stein-nist opened this issue Mar 1, 2024 · 0 comments
Open
10 tasks

Comments

@aj-stein-nist
Copy link
Contributor

User Story:

As a Metaschema module developer, to be sure I am using best practices recommended by the core Metaschema project specification maintainers when using these XSLT tools, I want a Schematron composition to report an error if I use the soon-to-be deprecated camelCase data types.

NOTE: This is an upcoming change in usnistgov/metaschema#558 that maintainer and community feedback indicates that this change with final deprecation of camelCase types will land in one of the milestone releases before 1.0.0 and complete it with 1.0.0.

Goals:

  • Report Schematron errors for any usage of as-type and datatype of the deprecated datatypes listed below:
    • base64Binary
    • dateTime
    • dateTime-with-timezone
    • email
    • nonNegativeInteger
    • positiveInteger

Dependencies:

{Describe any previous issues or related work that must be completed to start or complete this issue.}

Acceptance Criteria

  • All website and readme documentation affected by the changes in this issue have been updated. Changes to the website can be made in the docs/content directory of your branch.
  • A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
  • The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant