4 ms·
Underscore prefixes like C. Dedicated property to act as kitchen sinks, e.g. "custom", that says "anything in here is implementation specific". Simply not all
by junon 4y ago
Underscore prefixes like C.
Dedicated property to act as kitchen sinks, e.g. "custom", that says "anything in here is implementation specific".
Simply not allowing custom keywords at all, also a good option. Have users write higher level schemas that compile down to jsonschema.
All viable options.
- Karellen 4y agoThe thing that confuses me is: > A keyword is "known" if it is defined by a vocabulary listed in the schema's meta-schema (identified by the value in $schema). { "$schema": "https://json-schema.org/draft/2020-12/schema", So, if a schema identifies as conforming to the 2020-12 meta-schema, why would a new "database-field-id" keyword in the 2025 upgrade be an issue? The 2025 parsers should know that it's not a keyword in the 2020-12 meta-schema, and treat it the same as they always did, shouldn't they? But also - as an alternate to underscore prefixes, could new keywords just reuse the "$" prefix as in "$schema"?
- mst 4y agoI've always been fond of _x_ as a prefix for such things.