On Thu, Aug 31, 2023 at 1:05 PM Mario Loffredo <mario.loffr...@iit.cnr.it> wrote: > > AFAIU, the definition of a standard JSON data description language has been a > controversial matter for long. To my knowledge, the only DDL published as > RFC that could work is CDDL [RFC8610]. It was primarily created for CBOR but > it works for JSON too. >
Mario basically summed up the issue. I was involved in trying to get the IETF to do something here but there was no movement. There were many reasons: 1. JSON Schema seemed to be a moving target. 2. Something something about Yang. 3. At the time (and it may still be true), RDAP was by far the most complex example of JSON in the IETF. Everything else was much, much simpler and did not need a schema language. 4. Schema languages give a false sense of conformance. Conformance tools are far more important. Therefore the default position became "use CDDL". My experience with RDAP mirrors #4. Most conformance issues aren't about the JSON unless we're talking about jCard, for which schema languages are basically useless anyway. I would recommend using a conformance tool such as this one: https://github.com/icann/rdap-conformance-tool Also, ARIN's NicInfo had an RFC 7483 checker for JCR, which is superior to JSON Schema (or at least was). -andy _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
