Ben Hutton

OK, so it doesn't disable it completely. In which case, I've amended the issue title. I don't know why schema generators DO this. It's not needed. What do you see...

> responding with $id: makes it easier for the consuming clients as they don't have to concatenate/construct the $id themselves Why do you believe they WANT an $id for each...

Ha. Sure! It's valid for draft-07, which is what (hopefully) most people will be using now. Draft 2019-09 and newer don't allow `$id` to be used in a subschema*. The...

Draft 2019-09 is effectivly draft-08. We decided to change the naming convention because using `draft-NUMBER` confused people when we publish IETF drafts under different names. You could do that. Again,...

Yeah, I am familiar with several libraries which do similar... it's a pain. I don't understand WHY they do that, but hey. Yeah, I have a vested interest in this...

Thanks for this @vanrijn . That plugin provides examples and better documentation, so it's clearer that it does what I want.

There's no reason you can't add a regex for this in your schema, and then use allOf and $ref to validate.

Personally, given recent discussion and potential direction, I'm leaning towards thinking we shouldn't have IPv4 or v6 format... format is a bit of a mess =/

Hey Simon, thanks for coming and sharing your suggestion. This sounds like quite a specific use case. Is this something you believe many people would want to do? Have you...

There have been discussions about removing the ability in the future to support unknown keywords. I haven't looked into the arguments, but it feels sensible and plausible we could do...