As discussed in the MSON README - there is this Markdown format for documenting APIs; discussing / describing API payloads and resources in JSON Schema felt complex and not suiting well the settings of a Markdown document.
Besides some payloads are not just a JSON. So there is a need to describe these data in a media-type agnostic form.
Ok sorry if my question came off as snarky, the first example in your readme shows how mson can be converted to json which doesn't seem to be very useful.
I think you should better highlight the connection to json schema.
Also json schema is new to me. Any examples of it being used in the wild?
What do you think about Teleport [0]? It is more like an actual type system (with dependent types!), with type signatures that get encoded in JSON. In Python (the only functioning implementation thus far), a real definition looks something like this [1].
Rather than providing a big fixed set of types, Teleport provides just the basics and allows you to define your own types, be it JSON-encoded primitives or fancy deeply nested structures.
Since my partner left to work on something else, work on Cosmic slowed down, but I'm successfully using Teleport at my day job and planning a new release soon, along with a complete JavaScript port.
which spec are you working off? I am really interested in hearing what you think is not powerful enough. The meta-schema unioned all the types together. I find that annoying, but its drafted to be fixed in v5
