Add glossary entries for schema and instance.

[Julian]

No description provided.

[netlify]

✅ Deploy Preview for condescending-hopper-c3ed30 ready!

Name	Link
🔨 Latest commit	9783f12
🔍 Latest deploy log	https://app.netlify.com/sites/condescending-hopper-c3ed30/deploys/62f62ea27769940008a6a5e4
😎 Deploy Preview	https://deploy-preview-462--condescending-hopper-c3ed30.netlify.app/learn/glossary
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[Julian]

Thanks!

[notEthan]

This seems to focus on validation to the point of not considering any other application of JSON schema. Validation is by far the most common thing to do with schemas and instances, for sure, but not the only thing. I'd say that an instance is JSON data described by a schema (or multiple schemas), and a schema describes a set of instances, which are expected to be valid against it.

This is a thought I have had more broadly in the language used with JSON schema. My own implementation is focused on the descriptive aspect of the schema/instance relationship, with validation being a requisite feature to support that.

[notEthan]

I always feel like using the term "valid" in describing schemas that don't break any rules of the specification is asking for confusing with "valid" as a result of validating an instance against a schema. Especially since a schema can be valid against the specification, or valid against its metaschema, with pretty different (though strongly related) meanings. In that suite I'm working on of schemas that violate their spec, I landed on "conformant" to the spec to differentiate that from validation.

[Julian]

This seems to focus on validation to the point of not considering any other application of JSON schema. Validation is by far the most common thing to do with schemas and instances, for sure, but not the only thing. I'd say that an instance is JSON data described by a schema (or multiple schemas), and a schema describes a set of instances, which are expected to be valid against it.

I'm happy to reword, but don't we use the verbiage "validation" / "validate" even for the cases you're referring to? That was the feedback given here.

[Julian]

There's #469 with some cleanup so we can discuss on an open PR.

[handrews]

I'm happy to reword, but don't we use the verbiage "validation" / "validate" even for the cases you're referring to? That was the feedback given here.

Which was immediately followed by:

I'd go with "evaluation." I think "apply" is also fine whether the application is because of an applicator or because of a top-level invocation, but to avoid confusion, "evaluate" is probably best (and I think we settled on evaluationPath in the revised output format?)

"evaluation" is used fairly consistently in the spec such as in section 7 among others.