-
Notifications
You must be signed in to change notification settings - Fork 10
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 schema documentation production to current Metaschema model #14
Comments
Update Nov 5 2020XML docs refactoring proceeds well. Ready for closer review, then Hugo integration, while we come back to the JSON docs. |
Should have mentioned the working branch is here: https://github.com/wendellpiez/metaschema/tree/issue48-m4-schemadocs |
Update Nov 19 2020 The new production XSLTs are now integrated into Hugo to produce a running site, although I need help from @david-waltermire-nist on a couple of points (git alignment; correctly amending the CSS) before able to push a PR with this. Then much work will remain building this out. |
This should be updated based on the changes summarized in usnistgov/metaschema#195. |
Docs production to be factored out. As it stands this aspect of docs production is functional and adequate (afaik). If not, please make a new Issue. |
There is however a lot of work on how this current document generation pipeline is used in OSCAL, not here, and there are at least two issues queued up for the current OSCAL sprint, and it is complicated by the fact this work is used in the Metaschema repository for OSCAL, but not generating Metaschema docs for this project itself. So, may I respectfully requested we talk about this before it is closed? (I see the closeable tag added.) Thanks! |
@aj-stein-nist We should talk about this. Let's keep this open for now to allow for your larger questions to be addressed. |
User Story:
With usnistgov/metaschema#39 and #12, Metaschema has new features including support for constraints definition.
It has also changed somewhat in its design since the docs production pipeline was built, for example supporting local declarations and homonymy (same name for different thing in different contexts).
Both of these require extension of the Metaschema documentation pipelines to describe these features (as applied in a metaschema) in a legible way for users.
Goals:
More complete, more legible documentation of Metaschema models from the documentation-generation pipelines, both XML and JSON-oriented.
Dependencies:
The new Metaschema design should be feature-complete and stable before we take on the docs.
This will require some (front-end) design as well as work reworking the pipelines.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: