JADN

Within the OpenC2 community (OASIS) , there is a yearning for a schema language for JSON users. They are writing JSON Abstract Data Notation (JADN).

JADN is an information modeling language based on the CBOR data model. It has several purposes, including definition of data structures, validation of data instances, providing hints for user interfaces working with structured data, and facilitating protocol internationalization. JADN specifications consist of two parts: abstract type definitions that are independent of data format, and serialization rules that define how to represent type instances using specific data formats. A JADN schema is itself a structured information object that can be serialized and transferred between applications, documented in multiple formats such as property tables and text-based data definition languages, and translated into concrete schemas used to validate specific data formats.

In particular, JADN is data that can: 1) be displayed as tables in documents like the OpenC2 language spec, 2) be validated for correctness, ensuring that the tables are correct, and 3) validate data instances, ensuring that data examples correspond to the tables.

https://github.com/oasis-tcs/openc2-jadn/blob/working/jadn-v1.0-wd01.md

The standard has some interesting and influential backers, who hope that someday JADN will see use outside OpenC2, and that it will be understood by software tools.

I post this here because of the many fine arguments over XML vs JSON over the years, which have taught me a lot, and because that Subcommittee would be improved by the participation of some on this list.

tc