Allow optional requiredFilename in ContentType schema? #550
Description
Based on this discussion:
openMetadataInitiative/openMINDS_instances#271 (comment)_
Should we introduce an optional requiredFilename property in the ContentType schema, thus allowing instances to declare a fixed basename when truly needed (e.g., config.json, settings.json, package.json...)?
However, this property is unlikely to be broadly adopted, since most tools support customizable file names.