D2.7 OETCS API Requirements Version 1.2: Review: Chapt. 4.1 - 4.3

[UweSteinkeFromSiemens]

• 4.1.1: "After treatment, the input stack is supposed to be empty.": what is the impact of an empty input stack? Where in the architecture resides the input stack?
• 4.1.1: Who is responsible to maintain the connection states of the peripherals: the basic SW or the application SW?
• 4.2.1: "The control interface allows the Basic SW to initialise and activate the application ..": Where in the architecture (see 3.2) it the control interface located?
• 4.2.4.4: How can the application SW generate a non-arbitrary sequence of outputs?
• 4.3.1: The functional data flows related to the configuration interface are not identifiable in "OETCS_API Requirements_appendix_functional_data_dictionary_v1.0.pdf". The search for "CONFIGURATION INTERFACE" in this document has no results.
• 4.3.2: PLUG_BIT_STREAM_T is not traceable to "OETCS_API Requirements_appendix_functional_data_dictionary_v1.0.pdf".
• 4.3.2.4: "The parameters data will be provided in the form of a bit stream": The parameter data must be provided in a structured symbolic manner instead of a bit stream. Otherwise, the application software will become hardware and platform dependant.
• 4.3.3.2: ETCS_ID_T is not traceable to "OETCS_API Requirements_appendix_functional_data_dictionary_v1.0.pdf".

[UweSteinkeFromSiemens]

This issue is part of the review in #47 .