[Json] JSON Content Rules

[Daniel P <[e-mail]>]

Hello everyone,

I would like to solicit feedback from members of this forum on one feature
of the JSON Content Rules specification, draft 09
<https://datatracker.ietf.org/doc/draft-newton-json-content-rules/?include_text=1>,
as I'm considering to build an implementation.

The specification states: "There are two forms of rule name assignments:
assignments of  primitive types and assignments of all other types.  Rule
name assignments to primitive type specifications [e.g. string] separate
the rule name from the type specification with the character sequence '=:',
whereas  rule name assignments for all other type specifications [e.g.
array] only require the separation using the '=' character ... This syntax
is necessary so  that JCR parsers may readily distinguish between rule name
assignments involving string and regular expressions primitive types and
member names of member specifications."

An example (I hope I have this right):

{ $bar-name : $bar-val, "foo" : $foo-val }

; member name specification
$bar-name = /^bar[0-9]$/

; primitive type specification
$foo-val =: "foo"

; non primitive type specification
$bar-val = [ integer, integer, integer ]

In what otherwise appears to me to be a fairly clean specification, I'm
having some difficulty digesting this syntax, with "=" if such and such,
and "=:" if so and so. I would be interested if anyone else on this list
has any thoughts about this.

Thanks,
Daniel Parker
https://github.com/danielaparker/jsoncons