taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit de939ff8e91bb2cd5b4227a42a365c4cb928d201
parent d407e3ed76fb75fcbb3e9bd7020070b43ca3e847
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu, 16 May 2024 16:48:13 +0200

clarifications to spec

Diffstat:
Mdesign-documents/023-taler-kyc.rst | 12+++++-------
1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/design-documents/023-taler-kyc.rst b/design-documents/023-taler-kyc.rst @@ -204,8 +204,8 @@ The main state of an account is represented by a set of `KYC rules <KycRule>` (t `LegitimizationRuleSet`) which specify the current *rules* to apply to transactions involving the account. Rules can *exposed* to the account owner, or can be secret. Each *rule* specifies certain *conditions* which, if met, -*trigger* a single specific *measure*. After a *rule* was *triggered* and -before the *outcome* of the respective *measure* has been produced (say +*trigger* a set of *measures*. After a *rule* was *triggered* and +before the *outcome* of a respective *measure* has been produced (say because the user did not yet enter their data or the AML officer is still reviewing the case), the existing rules remain in force. Rules have a display priority, and if a second rule with a higher display priority is also @@ -1255,7 +1255,7 @@ on GET ``/deposits/`` with the respective legitimization requirement row. ,access_token BYTEA NOT NULL UNIQUE CHECK (LENGTH(access_token)=32) REFERENCES wire_targets (access_token) ,start_time INT8 NOT NULL - ,jmeasures TEXT NOT NULL -- FIXME: rename to jrule? + ,jmeasures TEXT NOT NULL ,display_priority INT4 NOT NULL ,is_finished BOOL NOT NULL DEFAULT(FALSE) ) @@ -1267,8 +1267,6 @@ on GET ``/deposits/`` with the respective legitimization requirement row. IS 'Used to uniquely identify the account and as a symmetric access control mechanism for the SPA'; COMMENT ON COLUMN legitimization_measures.start_time IS 'Time when the measure was triggered (by decision or rule)'; - -- FIXME: LegitimizationMeasures is *bad* here, as we only have the KycRule; the specific measure may - -- not yet have been selected at the time of the trigger! COMMENT ON COLUMN legitimization_measures.jmeasures IS 'JSON object of type LegitimizationMeasures with KYC/AML measures for the account encoded'; COMMENT ON COLUMN legitimization_measures.display_priority @@ -1412,13 +1410,13 @@ on GET ``/deposits/`` with the respective legitimization requirement row. The ``jmeasures`` JSON in the ``legitimization_measures`` -table is of type `LegitimizationMeasures`: +table is of type `LegitimizationMeasures`. The ``jnew_rules`` JSON in the ``legitimization_outcomes`` table is of type `LegitimizationRuleSet`. The ``jproperties`` JSON in the ``legitimization_outcomes`` table is of -type `AccountProperties`. +type `AccountProperties`. KYC forms