autobuild dependency graph of submodules

[lzehl]

essentials: core, controlledTerms
extensions: all other modules
TRUE DEP: bold links
SOFT DEP: thin links

ESSENTIAL -> EXTENSION scenarios:

1. schemaA -> schemaB (one or multiple object, required)

• schemaA in essentials
• schemaB in extension
  -> THIS IS WHAT WE NEED TO AVOID (TRUE DEPENDENCY between essential to extension)

2. schemaA -> [schemaB | schemaC] (one or multiple object, required)

• schemaA in essentials
• schemaB in extension
• schemaC in essentials
  -> OKAYISH (SOFT DEPENDENCY between essential to extension)

3. schemaA -> schemaB (one or multiple object, optional)

• schemaA in essentials
• schemaB in extension
  -> THIS IS WHAT WE WANT TO AVOID, less critical than 1 (SOFT DEPENDENCY between essential to extension)

4. schemaA -> [schemaB | schemaC] (one or multiple object, optional)

• schemaA in essentials
• schemaB in extension
• schemaC in essentials
  -> OKAYISH (SOFT DEPENDENCY between essential to extension)

Extensions to essentials can of course have TRUE DEPENDENCIES

For auto-generating this figure: