You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
furthermore, I believe https://github.com/usnistgov/metaschema-xslt has no support for sarif, so either metaschema-xslt would have to catch up to metaschema java and start producing sarif output, or metaschema java should replace metaschema xslt as the reference implementation.
Goals:
I'd like a strategy that supports the integrity and long term success of metaschema and oscal
Dependencies:
why isn't this repo considered a fork of the metaschema repo? this makes providing upstream updates more challenging.
Acceptance Criteria
this repo is converted to be a fork of the usnist metaschema
a strategy for reference implementation
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 text was updated successfully, but these errors were encountered:
There are also 10 dependabot PRs that are open and unresolved. By all indications, there is not much maintenance going on in the usnistgov/metaschema repository.
This repository was stood up to be a place where the specification, schemas, unit tests, and examples can be actively maintained. The PRs mentioned earlier have been merged here. At the moment this repo is 19 commits ahead of the usnistgov repo. As a direct contribution fork, doing this is not really practical. This repo and related website can also be used to post related specification changes, which would not be possible otherwise without PRs getting merged in usnistgov/metaschema.
If at some point usnistgov/metaschema becomes active again, they can pull changes from this repository if there is interest. They are also welcome to contribute here. Contributions from any community members are always welcome.
User Story:
I believe we need a strategy to syncronize this repo with https://github.com/usnistgov/metaschema
namely the SARIF module isn't there.
furthermore, I believe https://github.com/usnistgov/metaschema-xslt has no support for sarif, so either metaschema-xslt would have to catch up to metaschema java and start producing sarif output, or metaschema java should replace metaschema xslt as the reference implementation.
Goals:
I'd like a strategy that supports the integrity and long term success of metaschema and oscal
Dependencies:
why isn't this repo considered a fork of the metaschema repo? this makes providing upstream updates more challenging.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: