Re: [Json] Update Standard to support ECMA-262 BigInt

[Pete Cordell <[e-mail]>]

On 04/05/2021 14:38, Carsten Bormann wrote:
> On 2021-05-04, at 15:05, Pete Cordell <[e-mail]> wrote:
>>
>> The example wasn't intended to be about ABNF, but saying specifying formats in purely machine readable ways usually ends up being insufficient.  Having provision for human understood formats done in such a way that a machine can ask 'does this value conform to this format that you, smart human, have coded?' allows a simple way to side-step that problem.
>>
>> So in addition to the ABNF (or any other equivalent you might choose) you can also include to narratively define the constraints on say, date-mday etc.
> 
> Sure, we can add something like that, that is an interesting thought.
> 
> I’m mostly in favor of also providing a machine-executable form, which may not cover all the bases (if I say there is a “signature” of type “bstr”, I won’t be able to specify in CDDL what exactly I want from that :-).

I agree that an ABNF option is good.  In fact, if I had to choose 
between ABNF and regex, I'd go with ABNF.

But your example did make me think, did you consider HEREDOC format in 
CDDL? e.g. something like:

    rfc3339 = <<ABNFEND
       date-fullyear   = 4DIGIT
       date-month      = 2DIGIT  ; 01-12
       date-mday       = 2DIGIT  ; 01-28, 01-29, 01-30, 01-31 based on
                                 ; month/year
       time-hour       = 2DIGIT  ; 00-23
       time-minute     = 2DIGIT  ; 00-59
       time-second     = 2DIGIT  ; 00-58, 00-59, 00-60 based on leap sec
                                 ; rules
       time-secfrac    = "." 1*DIGIT
       time-numoffset  = ("+" / "-") time-hour ":" time-minute
       time-offset     = "Z" / time-numoffset

       partial-time    = time-hour ":" time-minute ":" time-second
                         [time-secfrac]
       full-date       = date-fullyear "-" date-month "-" date-mday
       full-time       = partial-time time-offset

       date-time       = full-date "T" full-time
    ABNFEND .cat rfc5234-core

    rfc5234-core = <<ABNFEND
       DIGIT          =  %x30-39 ; 0-9
       ; abbreviated here
    ABNFEND

(I think HEREDOCs would normally end when only the end token appears on 
its own line, but CDDL could say it has to be the first token on the 
line ad other tokens could follow so you can get your .cat rfc5234-core in.)

And I forgot earlier to say thanks for the links to WGs using CDDL for 
JSON.  So thanks for that.  I'll have a look at them.

Looking forward to the the ability to combine multiple CDDL files 
together being in place.

Cheers,

Pete.
-- 
---------------------------------------------------------------------
Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com
---------------------------------------------------------------------