Alignment between 5S-TES messages and TES messages

[anwarfg]

In TES, there are several fields that are optional - some that I've come across are:

Inputs

• URl
• Name
• Path
• Content
• Description

Outputs

• URL
• Name
• Description

There are several more in the API spec. However, 5S-TES requires them to exist, as they are checked for validation when the message is received even if they aren't used. This creates a misalignment between the TES API spec and 5S-TES.

Similarly, as the output URL is overwritten in 5S-TES, it should be optional (even though it's required in TES). It currently has to be provided, but any string will work to pass the validation check (even an empty string).