Definition of the configuration data model

Configuration data model:
 
In order to parse Science SBs into Configuration SBs, we’re going to need to have a definition of the configuration data model to work with.

This data model will not complete, but should be designed to be able to evolve with minimal system-level disruption, so I would suggest a distinction should be made between shared, stable parts and parts specific to a particular element, that can be evolved with the element. There is already a lot of information in the TM Architecture documentation, for example the Observation Configuration Data Model and the various Software Interfaces, but this task is to encode this information into an extensible JSON schema.