Austin Wright

@Julian Yes, it's proposing a change to the JSON Schema Core document, the next step is to draft some specific patches/PRs; I write an issue first to try to limit...

(Did I have the wrong tab open or something? I'm quite embarrassed I didn't catch that, thank you.)

> You're very keen on using this "set" language, but I'm not sure I've encountered that from others or in the spec. I use "set" in the mathematical sense and...

> My impression is that we already have consensus that we want to make this change. The devil is in the details, and I'm continuing to pile on more details,...

Yes, YAML also has a larger value space than JSON. For example, it supports circular references ([Anchors and Aliases](https://yaml.org/spec/1.2.2/#anchors-and-aliases))—there's no way to encode this to JSON and then back to...

Well, that's the paragraph I'm proposing to remove, at least from core. (Again that wouldn't suggest you can't pass alternate serializations to a validator, just that it's out of scope...

Like I mentioned above, this issue may be a good place to consolidate "Instance Data Model" and "Instance Equality" into a single section. Each section is describing essentially the same...

If this looks reasonable, I'd like to move this through next. Then I'd like to focus mostly on resolving outstanding PRs to accommodate a conversion to Markdown, but I'd also...

Can you elaborate? I believe I addressed all of those points... specifically that the existing "format" keyword is not reliable enough for many uses. It doesn't deprecate any existing functionality,...

> The only core formats are defined over strings, but we explicitly allow extra formats to be defined outside the spec Right, I was just pointing out there are no...