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
As the work in JSMDO has shown, a schema's traverse phase is very similar to the act of evaluating the schema against its metaschema -- the work we do at traverse time to identify embedded identifiers etc can be replaced by similar code that is triggered by evaluation callbacks on the properties keyword.
One interesting counter-example is if a document changes its dialect (embedded $schema keyword) midway -- at that point we cannot keep evaluating the schema against the same metaschema, as now the metaschema has changed. (!)
The text was updated successfully, but these errors were encountered:
As the work in JSMDO has shown, a schema's traverse phase is very similar to the act of evaluating the schema against its metaschema -- the work we do at traverse time to identify embedded identifiers etc can be replaced by similar code that is triggered by evaluation callbacks on the
properties
keyword.One interesting counter-example is if a document changes its dialect (embedded
$schema
keyword) midway -- at that point we cannot keep evaluating the schema against the same metaschema, as now the metaschema has changed. (!)The text was updated successfully, but these errors were encountered: