Issue #5 raised some relevant considerations that are currently being analysed.
One aspect under analysis is that some mandates can be used only once.
After the consumption of the service the status of the power must be changed so it cannot be used again.
This change should be performed by the eMandate Registry. But how does it get aware about the consumption of the Service?
Several solutions, each one with pros and cons, have been put on the table, each one with pros and cons. But possibly the one that appears to us as the most "natural" one (please react on this if you do not agree) is to phase the exchange of information between SP and eMR into three stages: 1) Mandate Request; 2) Mandate Response; and 3) Service Report, to be used in those cases where it is necessary to inform back the eMR about how the delivery of the service went (e.g. when the empowerment is a one-single-use one). The figure below sums up this exchange document protocol:
Reactions on this proposal would be appreciated, please.
Issue #5 raised some relevant considerations that are currently being analysed.
One aspect under analysis is that some mandates can be used only once.
After the consumption of the service the status of the power must be changed so it cannot be used again.
This change should be performed by the eMandate Registry. But how does it get aware about the consumption of the Service?
Several solutions, each one with pros and cons, have been put on the table, each one with pros and cons. But possibly the one that appears to us as the most "natural" one (please react on this if you do not agree) is to phase the exchange of information between SP and eMR into three stages: 1) Mandate Request; 2) Mandate Response; and 3) Service Report, to be used in those cases where it is necessary to inform back the eMR about how the delivery of the service went (e.g. when the empowerment is a one-single-use one). The figure below sums up this exchange document protocol:
Reactions on this proposal would be appreciated, please.