Re: [Json] JSON Content Rules

[Carsten Bormann <[e-mail]>]

On Jan 24, 2018, at 13:19, Pete Cordell <[e-mail]> wrote:
> 
>   "foo" - A member name (but see caveat below)
>   'bar' - A string value (new syntax, but also see below)
>   /^baz\d+$/ - A regex value
>   `biff\d+` - A member name regex (new syntax)

Hmm.

> We wanted to still allow JCR to be a superset of JSON syntax (to facilitate easy creation of JCR from example JSON).  So we wanted to allow:
> 
>    { "name" : "Fred" }

Right.  In JSON, a string is a string…

What is the syntactical feature of JCR that makes this distinction necessary?
Maybe you can fix that feature instead?

(When we designed CDDL, we didn’t have to make a distinction between string values destined as member names and string values destined as member values — indeed strings are strings. Now the CDDL syntax is very simple and does not leave any ambiguity as to whether we are talking about a member name or a member value; I haven’t looked at JCR recently enough to answer my own question here.)

Grüße, Carsten