Re: [Json] The parts of JSON (a possible aid to discussion)

[John Cowan <[e-mail]>]

Jacob Davies scripsit:

> I should have made the point regarding Unicode separately - speaking
> of separating things - but that was that it is unnecessary to mention
> Unicode anywhere except when discussing the interpretation of \u
> escapes and in the discussion of the application/json media-type, and
> that doing so in other places is a little confusing. (If I write a
> JSON text on a whiteboard, am I using "Unicode characters"? This seems
> like a map/territory issue - Unicode is a way of representing
> characters as integers, but characters are the things under discussion
> in the abstract model and textual language, not a particular mapping
> of integers to characters.)

+1

Note that Unicode actually provides two things:  it maps every character
to an integer v, called a Unicode scalar value, such that 0 <= v < 56320
or 56575 < v <= 1114111; and it provides a variety of mappings between
Unicode scalar values and sequences of 8-bit, 16-bit, or 32-bit unsigned
integers, called code units.  This is the law; all else is commentary.

-- 
John Cowan   [e-mail]    http://ccil.org/~cowan
[R]eversing the apostolic precept to be all things to all men, I usually [before
Darwin] defended the tenability of the received doctrines, when I had to do
with the [evolution]ists; and stood up for the possibility of [evolution] among
the orthodox --thereby, no doubt, increasing an already current, but quite
undeserved, reputation for needless combativeness.  --T. H. Huxley