commit f8bff544a82a0f80eb76d9ddc4855232176258cb
parent 7f22691a4a9901d07632e16e50cef606037a0360
Author: Christian Grothoff <christian@grothoff.org>
Date: Sun, 22 Jun 2025 12:01:34 +0200
remove historic KycStructuredFormData from manual
Diffstat:
1 file changed, 4 insertions(+), 26 deletions(-)
diff --git a/taler-kyc-manual.rst b/taler-kyc-manual.rst
@@ -500,30 +500,12 @@ the context in which the form is executed.
However, this is not yet implemented, see #9187.
When forms are submitted, the exchange converts the form data into key-value
-pairs where the key is the form field name and the value is of type
-`KycStructuredFormData`. The respective AML program can then evaluate the data from the form
+pairs where the key is the form field name and the value depends on
+the key. The different keys are defined in the
+``gnu-taler-form-attributes`` GANA registry.
+The respective AML program can then evaluate the data from the form
submission from `attributes`.
- .. ts:def:: KycStructuredFormData
-
- interface KycStructuredFormData {
-
- // Content type. Missing if unknown.
- content_type?: string;
-
- // Name of the uploaded file. Missing if unknown
- // or this was not a file upload.
- filename?: string;
-
- // Base32-encoded binary form value. Only present
- // if form data was determined to be binary data.
- data?: string;
-
- // Text form value. Only present if the form data
- // was determined to be in textual format.
- text?: string;
-
- }
The LINK Type
^^^^^^^^^^^^^
@@ -712,10 +694,6 @@ administrator.
// names and the values must be strings representing
// the data. In the case of file uploads, the data
// MUST be base64-encoded.
- // In the case of KYC data provided by HTML FORMs, the
- // keys will match the HTML FORM field names and
- // the values will use the `KycStructuredFormData`
- // encoding.
// Attributes are only provided if the AML program
// specifies "attributes" for its input requirements.
attributes?: Object;
