I have heard in the latest roundtable meeting that some EIDs with REST interface require dynamic query parameters, for example in dynamic tariff EIDs.
These parameters are specified via placeholders, similar to interface configuration parameters, and are replaced on every request.
While the configuration placeholders are specified in the <configurationList> structure, there is no equivalent for those dynamic REST query parameters.
Inquiry
Do we need a placeholder list inside the REST data point specification for such cases?
It might be helpful for testing and also parameter validation.
The schema would be very similar to the <configurationListElement>, therefore implementation would not be too difficult.
Situation
I have heard in the latest roundtable meeting that some EIDs with REST interface require dynamic query parameters, for example in dynamic tariff EIDs.
These parameters are specified via placeholders, similar to interface configuration parameters, and are replaced on every request. While the configuration placeholders are specified in the
<configurationList>
structure, there is no equivalent for those dynamic REST query parameters.Inquiry
Do we need a placeholder list inside the REST data point specification for such cases?
It might be helpful for testing and also parameter validation.
The schema would be very similar to the
<configurationListElement>
, therefore implementation would not be too difficult.