Jason Desrosiers

I didn't think you made it up. I recognized it as the example is from the documentation. Yes, I believe the example from the documentation has a bug. I don't...

I agree with your conclusion. This is what I missed, > Relative references are resolved using the URLs defined in the Server Object as a Base URI. That is very...

I was wrong that "schema names" are not allowed in `mapping`. The spec says `mapping` is "an object to hold mappings between payload values and _schema names or references_". (The...

I'm quite sure there isn't a way to bundle non-schema object easily. You'd have to re-write `$ref`s and deal with naming conflicts in `components`. However, if OpenAPI adopts the `$id`...

@karenetheridge > This is getting so complicated It's really not. I expected that people who are not familiar with JSON Schema's `$id` keyword might find this confusing at first, but...

> "domain specific" is redundant (we say it's only for JSON, that's it's "domain") The domain is JSON validation and annotation, but I agree that "domain specific" is not useful...

Generally I'm not too concerned about default configuration. As long as it can be easily configured to be compatible. Although, lately ajv's strict mode is making me think twice about...

It's pretty bold to argue that the primary maintainer of the JSON Specification (@handrews) misunderstands "what JSON Schema really is and what it is used for". But, I've been known...

I agree "tuple" isn't a perfect description, but I think it's more helpful than misleading. `prefixItems` (or previously array-form-`items`) is primarily useful for describing a tuple. I think the way...

The schema is correct as it is. If the country is not set, USA is assumed and therefore the postal code (if present) needs to be a USA postal code....