Jason Desrosiers

I don't see why the vocabulary URI couldn't serve both human readable docs and a machine readable description. That's what content negotiation is for. `Accept: text/html` could provide human readable...

I opened an issue with them to ask some questions: https://github.com/jshttp/mime-db/issues/247. Summary: I think they'll accept it if we add the extension to the spec, but that doesn't necessarily mean...

It's a shame that many applications will likely choke on `*.schema.json`. With a pattern like this, applications that understand `schema.json` can treat a file like a schema, while applications that...

There is a way to do this with OpenAPI 3.1 because it supports dynamic references from JSON Schema 2020-12. Imagine we have a pretty standard CRUD API. Each resource also...

> Because the top level `paths` is defined as `#/$defs/paths` which is an object of path-items, not path-items-or-references. I think we could resolve all issues by letting `/paths/` be an...

> I think perhaps for 3.1.1 we can say that if the mapping string is a fragment-only uri-reference, then it's resolved against the containing document (e.g. for '#/components/schemas/Dog'), but otherwise...

I could do a revision, but it's not clear to me which parts you'd like to keep and which to revert. If someone wants to submit a review pointing out...

Thanks @handrews. That looks like what I need to do a revision. It'll be a couple more days still until I can get to it, but I wanted to acknowledge...

It could work either way, but I would include it in every node. I feel like if I was writing code to process this output, it would be annoying if...

I think the identification stuff needs a lot of attention. Probably after the initial release, I'd like to look into completely reworking this area. > Schema document roots SHOULD have...