Anywhere the JSON Schema goes, this all-important information about the JSON Schema goes too.
But we still don’t have an association between the individual JSON objects and the JSON Schema - let’s fix this next.
For example, curves that intersect themselves will not render correctly because they do not have a “inside” and “outside.” The various font file formats also expect glyphs to adhere to certain rules that simplify placing the text on screen, and fonts that break the rules can cause unexpected problems.
An example of this type of issue is that all of the points on a curve should have coordinates that are integers.
In this blog post, Fred and I will introduce another building block, which we are calling self-describing JSONs.They include a couple of updated variables (hopefully eliminating any headaches with the original ‘fields Filled’ infinite increment issue) and a reg Ex that validates the the email field, once (or if) the core validation fails.For the rest of you…read the original post [below] to gain a little background/perspective and see if this suits your current issue.But first, we’ll explain what the problem is that self-describing JSONs solves.In the rest of the post, we will cover: This is a good start: our implicit knowledge about this JSON Schema is now captured against the JSON Schema itself.