This section tries to create a middle ground between what is agreed out-of-band between client and service and what is communicated using discovery (and can change dynamically?).
The result is a section that holds a little bit of both without a clear vision on what drives data to be part in the discovery mechanism and what is out-of-band.
The discovery mechanism should cover those aspects that may change depending on the service or require the client to act-upon based on data received.

Key examples include configuration (see other ticket on this topic) and discovery of services that are defined on a CDS-algorithm development environment (the list and data requirements are dynamic).

In the latter, the data requirements are dynamic and might very well change.
Each serice will have specific data requirements. Some services might do a basic calculation based on prefetch and retrieve additional data when required. This requires the services to depend on the presence of certain data-delivery mechanisms. Something that they should indicate in the discovery mechanism and that the client may ignore.
This should be clarified.