-
Notifications
You must be signed in to change notification settings - Fork 19
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
Permit let
variable declarations without require sibling constraint
#548
Comments
@david-waltermire per conversation I will leave it in 1.0.0-m3 milestone for now, we can revisit if the work gets completed and review finalized ahead of that milestone target. |
… solution to #548 is completed.
Due to limited attendance at today's community meeting from Wendell and other adopters, we decided to park discussion for today and paired on other issues instead. A collection of relevant models and sample documents for further discussion will be kept in this GitHub Gist until further notice or updated to this comment. https://gist.github.com/aj-stein-nist/3c89090184bc446b4759a41b52cf3ae3 |
@david-waltermire, my memory is hazy on this. Have we not discussed this yet? Either way, should we be bringing it up tomorrow? |
Per discussion today during the community call, several on the call agreed that interleaving of |
User Story:
As a Metaschema developer, in order to share variable declarations for reuse in descendant child constraints without duplicate the same variable in every scope, I would like the Metaschema core syntax model to permit binding variable values with
let
but without needing to define a siblingallowed-values
/expect
/index
/is-unique
/etc. constraint beside it.For an example as to why see PR review, specifically discussion in #542 (comment).
Goals:
schema/metaschema/metaschema-module-metaschema.xml
to allowlet
bindings without a sibling constraint.schema/xml/metaschema.xsd
to allowlet
bindings without a sibling constraint.Dependencies:
{Describe any previous issues or related work that must be completed to start or complete this issue.}
Acceptance Criteria
{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.}
The text was updated successfully, but these errors were encountered: