[Json] Doofus Parameter Labels

[Phillip Hallam-Baker <[e-mail]>]

So, I am implementing an IETF draft which is fairly widely used and
using a code generator to speed things along.

The code is breaking because the spec has decided to use 'protected'
as a tag which is of course a reserved keyword in Java, C# and much
else.

OK so there is an escape feature that I can use instead. But those
don't exist in other languages. And then I come across a tag that has
a non alphanumeric tag value.


This sort of thing is likely to be happening quite a bit now that
people are using JSON and it would be a lot better if we could avoid
it. The fact that JSON allows tags to be any valid UNICODE sequence
does not mean that all choices are equal.

In general it would be good if people writing specs could stick to the
identifier naming rules for C and avoid reserved words from Java, C#,
etc. The languages and tools I use are quite capable of using accented
characters. I have absolutely no clue how to generate them on the
keyboard though.