Henry Andrews
Henry Andrews
A use case that I just encountered is onboarding an IoT device, where some HTTP API calls are needed, but there is a BLE (bluetooth low energy) step in the...
@karenetheridge want to take a look with your schema work?
_[Note: I am not affiliated with Scalar, I'm just learning the product and am curious about this issue]_ Is this a referencing problem or an `allOf` + `oneOf` problem? It...
@fpapon There are no schema-visible differences between patch releases. That is part of the _definition_ of a patch release. The dates allow us to make bug fixes and other improvements....
@fpapon but see also #4877.
@rmannibucau the JSON Schema section that you linked to has nothing to do with using `$schema` in non-JSON Schema documents, which has _never_ been part of the JSON Schema specification.
@rmannibucau also, there is no need for such a usage of `$schema` because the `openapi` field gives you the major and minor version, which is sufficient to locate the most...
> jsonSchemaDialect is an example of this: it is now permitted to be a uri-reference, not a uri, so such a uri-reference in an OAD written with the latest schema...
@ralfhandl > We do not want to change a published schema „in place“, so a new schema iteration needs a new retrieval URI and a new $id value. Yeah this...
@rmannibucau I wrote/maintained musch of the JSON Schema specification. I am quite certain that `$schema` to reference a schema from an instance is _not_ part of the JSON Schema specification.