Re: [Json] Schemas & so on

[Anders Rundgren <[e-mail]>]

On 2016-05-01 22:55, Tim Bray wrote:
>
> I find myself tasked with specifying a JSON-based DSL and preparing it for public release, with a validator and so on.
>
> I had never really concerned myself much with options for JSON language definition, but have discovered they’re not very good.  The JSON Schema project is not terribly appealing - opaque spec, poor documentation and tools - and smells of neglect (last I-D expired in 2013).  It's been suggested that a good approach would be just to write a jq program that emits true or false.
>
> Is there good conventional wisdom about formally specifying a JSON dialect?

I had used XML Schema for 10Y+ before I became a JSON "convert".

I addressed the problem you mentioned in another and less formal way:

1. Creating a strongly typed JSON parser with access methods like getString(), getInt() etc.  This also supports some derived types that you most likely need such as dateTime, BigInteger and BigDecimal (for the financial industry).

2. The I added a method for verifying that all elements have been read.

This works quite well but of course do not address the documentation issue or the ability creating JSON from static object declaration.

https://github.com/cyberphone/saturn/blob/master/resources/common/org/webpki/saturn/common/PayerAuthorization.java

Anders

>
> -- 
> - Tim Bray (If you’d like to send me a private message, see https://keybase.io/timbray)
>
>
> _______________________________________________
> json mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/json