Sprint22 Metaschema enhancements #450
Conversation
| @@ -85,15 +92,15 @@ Nonetheless and with this in mind, understanding the mechanism by which the Meta | |||
|
|
|||
| Terminology note: "metaschema" is a common noun and there are many metaschema technologies (indeed almost any mature XML tag set has one), with different purposes, feature sets and capabilities. "Metaschema" (capitalized) is our peculiar homegrown metaschema technology and application. | |||
|
|
|||
| ## The Overall Approach | |||
| ## The Approach | |||
|
|
|||
| A reduced, lightweight modeling language with certain specially-enforced constraints can be sketched such that multiple schemas constraining disparate formats, such as XML and JSON, can be produced from a single metaschema instance (a document written in Metaschema) deterministically, and thus designed and coordinated in parallel. | |||
There was a problem hiding this comment.
@wendellpiez should we maybe be more specific on the use of XML for crafting the metaschemas themselves rather than alluding to any sort of new language which is what the sentence "a reduced, lightweight modeling language ..." kind of does? I know we don't want to detract from the design principles we've built, which themselves are new in this domain, but don't necessarily want to confuse folks when it comes to the syntax of the metaschemas.
There was a problem hiding this comment.
@anweiss good point. We could say "A reduced, lightweight XML-based modeling language" -- would that do the trick? I am not sure this is the place to explain the rationale(s) for the XML basis of the Metaschema itself. Or is it? We could also write a couple of sentences on that.
There was a problem hiding this comment.
I think simply adding "XML-based" will do the trick here. A better place to explain the rationale behind certain decisions such as the use of XML for the metaschema, etc might be in an FAQ of sorts, no?
…ns; moving w/in the model; valid values)
…s for cardinality indicators usnistgov#441
…ulting XSD per usnistgov#448; some updates to markdown documentation
…actually works now
… xs:schema/xs:appinfo
Co-Authored-By: Andrew Weiss <anweiss@github.com>
Co-Authored-By: Andrew Weiss <anweiss@github.com>
Disabled @group-as checks in metaschema-check.sch. These need to be updated to support the new features.
… metaschema update XSLT - will break the build for now
… also small doc mod in profile metaschema
build/metaschema/json-binding.md
Outdated
| @@ -0,0 +1,352 @@ | |||
|
|
|||
There was a problem hiding this comment.
This file was used to define the work needed for this PR. I don't think this needs to be added to the repo as a standalone Markdown file. We should pull from this to build out metaschema documentation and examples instead.
There was a problem hiding this comment.
Moved the file to a safe place, no longer in the rep
| <xsl:strip-space elements="*"/> | ||
|
|
||
| <xsl:preserve-space elements="documentation"/> | ||
| <!--Converts file:/C:/Users/wap1/Documents/OSCAL/build/metaschema/xml/oscal-datatypes.xsd in JSON Schema notation--> |
There was a problem hiding this comment.
Not sure why this path is in here. This needs to be cleaned up.
There was a problem hiding this comment.
Stray comment now cleaned up.
…schema docs (for real now)
|
Closing this in favor of PR #464, where this branch is being integrated. |
Committer Notes
Testing PR. Will rewrite these committer notes to reflect Issues addressed, now (at least): #437, #442, #448, #435, with more to come.
Note: the draft SSP Metaschema, which needs to be updated to the new model, is not validated in this build against its XSD or Schematron.
All Submissions:
Changes to Core Features: