Suggest specifying mapping between registry and validation scripts in package.json

[palemieux]

Currently the mapping is through file names:

registries/src/main/scripts/validate.js

Line 41 in e1795fb

const schemaFile = DATA_SCHEMA_PATH.replace("%s", name)

[radford-for-smpte]

@palemieux , what are you thoughts on the fact that the data file names must currently match both the JSON schema files and the validation files:

const DATA_SCHEMA_PATH = "src/main/schemas/%s.schema.json";
const DATA_VALIDATE_PATH = "src/main/scripts/%s.validate.js";

Additionally, the data file names implicitly dictate the path values at https://registry.isdcf.com/.

Is the thought to make all 3 of those mappings explicit in package.json?

[palemieux]

Further thoughts:

• hard-coding the location of the schemas and registry files in validate.js is probably better than hard-coding them in package.json since (a) it is closer to the actual code and (b) clients are supposed to use validate.js to retrieve the registries and other exposed functions/structures.

• validate.js should be renamed registries.js (or index.js or something more general) since it exposes more than validation methods.