You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In some cases, consent may need to be captured well before actual processing is required. For example, in preparation for a trip, consent for processing may be gathered days ahead of an actual trip, however processing is not needed prior to the day of the trip itself. Such staged consent support is not currently possible, as the timestamp on the receipt acts as an implicit start date for processing. Processors are increasingly wary of such open-ended windows (rather they choose to limit exposure).
Describe the solution you'd like
In $.services[].purposes[] we have a termination property. I propose adding an optional commencement (or in SAML parlance, notBefore) property to the purpose object.
Describe alternatives you've considered
Today, to increase interop chances, we store this value outside the consent receipt, which requires us to move the signature on level above our consentReceipt object.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In some cases, consent may need to be captured well before actual processing is required. For example, in preparation for a trip, consent for processing may be gathered days ahead of an actual trip, however processing is not needed prior to the day of the trip itself. Such
staged
consent support is not currently possible, as the timestamp on the receipt acts as an implicit start date for processing. Processors are increasingly wary of such open-ended windows (rather they choose to limit exposure).Describe the solution you'd like
In
$.services[].purposes[]
we have atermination
property. I propose adding an optionalcommencement
(or in SAML parlance,notBefore
) property to the purpose object.Describe alternatives you've considered
Today, to increase interop chances, we store this value outside the consent receipt, which requires us to move the signature on level above our consentReceipt object.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: