Deal with sub-dictionaries for JSON multi-inheritance

[Lestropie]

All of the code for the first working implementation assumes that JSON key-value dictionaries are to be interpreted only as present or absent at the root level of the dictionary. As such, if one were to have two metadata files applicable to some data file, both of which have contents stored in a sub-dictionary of the same name, but there we no collisions between them with respect to the contents of those sub-dictionaries, then the initial code will treat that as an overload.

Have to either:

• Document as part of the specification that:

  • Having the same key present in two dictionaries constitutes an overload
  • This will result in a warning
    (and may be escalated to a violation of the IP in future versions)
  • The metadata to be interpreted with respect to the data file for which both metadata files are applicable should be exclusively the content of whichever metadata file is "closest" in the filesystem hierarchy / Inheritance Principle criteria, not a merge of the respective contents of the sub-dictionaries.

• Modify code such that metadata key collisions are checked recursively through any sub-dictionaries.