Re: [Json] JSON or I-JSON?

[John Cowan <[e-mail]>]

On Fri, Feb 26, 2021 at 12:41 PM David Kemp <[e-mail]> wrote:

If you are designing a protocol that uses, for example, Reputons (
> https://tools.ietf.org/html/draft-ietf-repute-media-type-13#section-3.1),
> and a Reputon can contain megabytes of malware, or mpegs of cats being
> cute, or 14th century pornography (
> https://github.com/oasis-tcs/openc2-usecases/blob/master/Cybercom-Plugfest/TestData/slpf%2Bacme/commands/bad/create_poetry.json),
> that isn't necessarily a good thing for the Internet.
>

Nevertheless, there are many contexts where must-ignore is entirely
appropriate.  If I am checking your ID card against a list of authorized
visitors, all I need to know is how to find your picture and your name:
whatever other fields may be present are quite irrelevant to me.  (Not
always so easy: probably a hundred traffic tickets were written in Ireland
in 2006-09 in the name of Prawo Jazdy, which is, alas, merely the Polish
for "driver's license".)

In any case, simple limitations on the length or nesting depth of a
structured document should be enough to eliminate all the problems you
mention.



John Cowan          http://vrici.lojban.org/~cowan        [e-mail]
    "Mr. Lane, if you ever wish anything that I can do, all you will have
        to do will be to send me a telegram asking and it will be done."
    "Mr. Hearst, if you ever get a telegram from me asking you to do
        anything, you can put the telegram down as a forgery."