Learning from "competing" formats

[MikeRalphson]

• fern (new to me this day)
• Amazon smithy more documentation and code seems available for Smithy 2.0 e.g. converting to OAS
• RAML - traits and overlays already under consideration, more?

[darrelmiller]

I'll throw this https://github.com/microsoft/typespec into the mix too (formerly known as cadl).

Also, I think Steven Mizell book has some great insight here https://smizell.com/language-oriented-approach/

[JoanPuig]

I would suggest taking a look at: https://github.com/FIXTradingCommunity/fix-orchestra-spec, A lot of the design discussions around scenarios, parameter validation and workflows are very similar.

[handrews]

JSON TypeSchema (which I have not seen before) was brought up in an old spec issue as an alternative schema candidate:

• Use TypeSchema as alternative schema OpenAPI-Specification#2839

[earth2marsh]

Lexicon and its Data Model specification is another example to consider: https://atproto.com/guides/lexicon

[handrews]

CDDL is a data definition option, applying to either JSON or CBOR (CBOR support would be a nice bonus). It is not in JSON form, although we could either import them as separate documents or create a JSON representation if we really wanted to. CDDL 2 includes validation, annotation, and transformation on its road map:

• https://www.rfc-editor.org/rfc/rfc8610.html
• https://www.ietf.org/archive/id/draft-bormann-cbor-cddl-2-draft-04.html#name-processing-model-beyond-val