%% You should probably cite draft-ucarion-json-type-definition instead of this I-D.
@techreport{ucarion-jddf-05,
    number =    {draft-ucarion-jddf-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ucarion-jddf/05/},
    author =    {Ulysse Carion},
    title =     {{JSON Data Definition Format (JDDF)}},
    pagetotal = 44,
    year =      2020,
    month =     jan,
    day =       23,
    abstract =  {This document proposes a format, called JSON Data Definition Format (JDDF), for describing the shape of JavaScript Object Notation (JSON) messages. Its main goals are to enable code generation from schemas as well as portable validation with standardized error indicators. To this end, JDDF is strategically limited to be no more expressive than the type systems of mainstream programming languages. This strategic limitation, as well as the decision to make JDDF schemas be JSON documents, also makes tooling atop of JDDF easier to build. This document does not have IETF consensus and is presented here to facilitate experimentation with the concept of JDDF.},
}