Idea: Consider relaxing dict key charset restriction, rely on "name" instead of "altnames.json"

[Fannon]

Just a suggestion / feedback on something that could be done differently, but the current proposal also works.

Instead of applying the restricted charset (Identifier Rules) to the dictionary keys AND to the name, we could make it more similar to how JSON Schema works today:

• There are no limitation on dictionary key charset and it represents the JSON encoding name (altnames.json). If this contains restricted chars, it's mandatory to add name for codegen / tools.
• The altnames.json can be removed, and it's not necessary to use a spec extension just to describe existing JSON / JS structures as they are.
• Tools / codegens will always use name and fall back to the dictionary key.

Advantages from my view:

• Closer to how JSON Schema works today
• One less concept and one less spec extension to understand
• I think that modeling existing JSON structures is very common, the new identifier name restrictions may only work consistently for greenfield / new models that are created in JSON Structure from start.

Disadvantages:

• Validation of correct JSON Structure document is more complicated, because the regexp validation on dictionary keys is conditional (only has to match regex if no name is provided).

[clemensv]

The restriction of the character set of names is very intentional. I want to make sure that all names and namespaces can be cleanly mapped into databases and most common programming languages. Being able to define everyone's weird JSON document shapes is not a goal I am pursuing. altnames/json is a way to hack around that restriction and the pain of doing that is also intentional.

there are a few cases where "name" doesn't have a map above it and therefore this proposal would not work for those cases.

[Fannon]

@clemensv - yes, I understood that and fully agree that this is useful. The charset restriction of name would stay exactly like it is.

But if name can't be put in every place where it's needed, this approach would cause issues. Where would this be?