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

[Pete Cordell <[e-mail]>]

On 04/05/2021 11:11, Pete Cordell wrote:
> 2.
> Although possibly not formally released, we were considering a way of 
> declaring that a string had to adhere to an arbitrary format.  This was 
> a way of adding additional string based types (as there is no other 
> option in JSON for extended types!) without adding new base types (like 
> int32, date-http etc).  So, in a ruleset you could specify something like:
> 
>    #ruleset-id org.ietf.extended-types
> 
>    $rfc2822-date-time =
>          @{format org.ietf.extended-types.rfc2822.date-time} string
> 
> Then use it as:
> 
>    #import org.ietf.extended-types as iet
> 
>    {
>       "start-time" : $iet.rfc2822-date-time,
>       "end-time" : $iet.rfc2822-date-time
>    }
> 
> The spec for the "org.ietf.extended-types.rfc2822.date-time" format 
> might read something like:
> 
>    Formatted according to the RFC2822 date-time ABNF but omitting
>    the trailing [CFWS] term.
> 

Actually, @{format} doesn't have to be limited to strings.  You could 
also format other base types.  For example, @{format} on an int might 
look something like:

   #ruleset-id org.example.my-types

   $int-div-3 =
         @{format org.example.my-types.int-div-3} int

Where the definition for "org.example.my-types.int-div-3" is "positive 
integers that are multiples of 3".

Cheers,

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