Improve names of definitions in JSON Schema

[wendellpiez]

Describe the bug

See usnistgov/metaschema#112

This is both to improve the (JSON) schemas in general, and make them more robust across conformant processors.

Who is the bug affecting?

Anyone depending on validation in JSON Schema or who wishes to use the published schemas as bases for extension etc.

What is affected by this bug?

Usability and extensibility of the generated schemas.

When does this occur?

Always (any time a JSON Schema is produced from a metaschema).

How do we replicate the issue?

Inspect the schemas.

Expected behavior (i.e. solution)

The ideal syntax would both disambiguate all the definitions, and be legible for devs and robust.

We may wish to keyword both top-level module, and interim module, into a definition name, in order to help.

Other Comments

Run this by the community we have participants who can help review the work.