[Cbor] An Information-based CBOR schema language?

[David Kemp <[e-mail]>]

CBOR-bis describes the need to specify document content without needing the
specification to parse the document:

  "Of course, in real-world implementations, the encoder and the decoder
   will have a shared view of what should be in a CBOR data item.  For
   example, an agreed-to format might be "the item is an array whose
   first value is a UTF-8 string, second value is an integer, and
   subsequent values are zero or more floating-point numbers" or "the
   item is a map that has byte strings for keys and contains at least
   one pair whose key is 0xab01".

CDDL is a schema language for CBOR.   JADN (JSON Abstract Data Notation) is
another.  JADN differs from CDDL in that it:
  1) Specifies an Information Model rather than a Data Model (RFC 3444), and
  2) Is itself structured data (JSON or CBOR) rather than text that
requires parsing

JADN was created as the schema language for the OpenC2 security automation
protocol (
https://www.csoonline.com/article/3386161/openc2-can-accelerate-security-operations-automation-and-orchestration.html),
but there is now a need to separate the schema language from any particular
application protocol.   There is currently a draft in OASIS format (
https://github.com/oasis-tcs/openc2-jadn/blob/working/jadn-v1.0-wd01.md),
but it seems possible that the IETF is a more appropriate venue to develop
an Information Model standard.

This message is to gauge interest in creating a JADN Internet Draft and to
either initiate a BOF or adopt the draft as a work product of an existing
WG.  If you are interested in working on such a spec, or have suggestions
for where it should be worked, please let me know.