Support tagging top-level metaschema definitions as 'local' to exclude them when imported #76
Assignees
Labels
enhancement
New feature or request
Comments
|
Work progresses on this. Unit testing is helping to show the steps in sequence. As of today we also have a breaking test we can use to demo this functionality. |
wendellpiez
added a commit
to wendellpiez/metaschema
that referenced
this issue
Oct 16, 2020
… declared to be 'local' at top level (usnistgov#76); now with unit testing
This was referenced Oct 16, 2020
david-waltermire
pushed a commit
that referenced
this issue
Oct 19, 2020
… declared to be 'local' at top level (#76); now with unit testing
3 tasks
wendellpiez
added a commit
to wendellpiez/metaschema
that referenced
this issue
Nov 10, 2020
… declared to be 'local' at top level (usnistgov#76); now with unit testing
david-waltermire
pushed a commit
that referenced
this issue
Nov 13, 2020
… declared to be 'local' at top level (#76); now with unit testing
david-waltermire
pushed a commit
that referenced
this issue
Dec 21, 2020
… declared to be 'local' at top level (#76); now with unit testing
david-waltermire
pushed a commit
that referenced
this issue
May 27, 2021
* Many adjustments toward correct converter generation, though still broken - start with unit test toolchains/xslt-M4/metapath/metapath-jsonizing.xspec - this is a fail-safe commit * Now appears to pass testing scenarios (but more testing is coming) * Committing a version that handles test data correctly (so far) from rebuilt metaschema composition addressing #51 #53 #76
david-waltermire
added a commit
that referenced
this issue
Jun 6, 2021
* Rework of docs focusing on JSON docs and model pipeline * Improvements to composition toolchain * Fixed a few small bugs in the metaschema-check. Improved performance of the compose pruning using an accumulator. * Moved edge-case samples into testing directory * Made shadowing warning a warning * Initial commit of an Oxygen Metaschema framework. * Creation of new compose schematron unit tests. * Cross-linking XML and JSON syntax pages and other improvements to links * Now building XML and JSON indexes to reference pages, with links to steps * Reconfigured docs pipeline (XSLT entry points); adding new files including pipeline steps * Migrating schema generation tools to new/improved composition pipeline * Addressing usnistgov/OSCAL#902 thanks for finding this bug * Enhancements to JSON Schema definition (with better performance too) * Adding support for json-base-uri as a metaschema property * Updated JSON schema $id; factoring out common docs XSLT * Fixing IDs in JSON schema per issue usnistgov/OSCAL#933. * Addressing datatype validation issues: whitespace collapsing; non-empty values; ncname-workalike in JSON Schema - see usnistgov/OSCAL#911 usnistgov/OSCAL#805 also #33 #67 #68 * Improvements to XSD production; fully aligning 'token' datatype across XSD and JSON Schema implementations. * Updating bidirectional XML/JSON converter generators (#143) * Committing a version that handles test data correctly (so far) from rebuilt metaschema composition addressing #51 #53 #76 * Now displaying constraints in documentation at point of definition; * Docs generation revamp Reworked reference and other pages to sketch - #128 and others Co-authored-by: Wendell Piez <wendell.piez@nist.gov>
|
Work done previously, closable. This was implemented in previous work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story:
In WIP (branch
metaschema-m4-integration) the Metaschema XSD now supports a new attribute on top-level (global) definitions,scope, which can be set to "local" or "global"."global" represents the current semantics. A definition at the top level is available for reference from any assembly model, whether in the current metaschema or in an importing metaschema (unless it is overwritten by the import).
The new value "local" should exclude a definition from the set of global declarations in importing metaschemas. Effectively, this is a local definition (that is, local to the module) that can be referenced within the same module, instead of given by value in the model that uses it.
Goals:
Implement this feature to filter out definitions marked as 'local' from composed metaschemas, when they are imported. For the module in which they are used to be complete, they must be kept for its use, possibly by replicating them as local definitions in place.
A PR should be made against the
metaschema-m4-integrationbranch, notmaster.Dependencies:
A working version of the oscal metadata metaschema (in the
metaschema-m4-integrationbranch) contains examples for testing.Acceptance Criteria
The text was updated successfully, but these errors were encountered: