commit 15ae5db2f796229ea9e9ed89811265d3cdffff62
parent 1aff7b911c1aa66fb666ee3c9ce0c5d79237cfa1
Author: priscilla <priscilla.huang@efrei.net>
Date: Fri, 11 Nov 2022 05:51:41 -0500
Merge branch 'master' of git+ssh://git.taler.net/marketing
Diffstat:
1 file changed, 17 insertions(+), 18 deletions(-)
diff --git a/standards/draft-grothoff-taler.xml b/standards/draft-grothoff-taler.xml
@@ -74,7 +74,7 @@
interact with a wallet. By having a Taler wallet handle the respective URIs,
applications can integrate Taler payments without having to support the Taler protocol
directly. Furthermore, by passing control to a Taler wallet process, the wallet's
- database with its finanical data might be better protected from application failures.
+ database with its financial data might be better protected from application failures.
</t>
</abstract>
@@ -92,7 +92,7 @@
<section title="Objective">
<t>
A 'taler' URI always instructs a GNU Taler wallet to perform a particular operation.
- A 'taler' URI consists of a action and optional parameters.
+ A 'taler' URI consists of an action and optional parameters.
</t>
<t>
The interpretation of the optional parameters depends on the action.
@@ -266,13 +266,13 @@ also <xref target="taler-registry" />).
<t>merchant_prefix_path: list of path components that identifies the path prefix of the merchant base URL</t>
<t>order_id: the order ID that the customer is asked to pay for</t>
<t>session_id: the session ID under which the payment takes place</t>
- <t>c: a high-entropy order "ClaimToken"</t>
+ <t>ct: a high-entropy order "ClaimToken"</t>
</list>
</t>
<t>
<list style="symbols">
<t>Name: pay</t>
-<t>Syntax: taler://pay/{merchant_host}{/merchant_prefix_path*}/{order_id}/{session_id}{?c}</t>
+<t>Syntax: taler://pay/{merchant_host}{/merchant_prefix_path*}/{order_id}/{session_id}{?c=ct}</t>
<t>Example: taler://pay/merchant.example.com/42/</t>
<t>Contact: N/A</t>
<t>References: [this.I-D]</t>
@@ -436,41 +436,40 @@ also <xref target="taler-registry" />).
<t>
The specific arguments of a "restore" action are:
<list style="symbols">
- <t>sync_host: the hostname of the backup service (possibly including a port number)</t>
- <t>sync_prefix_path: list of path components that identifies the path prefix of the backup service base URL</t>
- <t>symkey: symmetric key that was used to encrypt the backup</t>
+ <t>sync_rootkey: Root sync key of the wallet, used to derive the symmetric key to encrypt the backup with individual providers.</t>
+ <t>sync_provider_list: Comma-separated list of provider http or https URLs. If no scheme part is specified, https is assumed. Each URL is URI-encoded for all characters except "A-Z a-z 0-9 - _ . ! ~ * ' ( )" (matching the HTML5 encodeURIComponent).</t>
</list>
</t>
<t>
<list style="symbols">
<t>Name: restore</t>
-<t>Syntax: taler://auditor/{sync_host}{/sync_prefix_path*}/{symkey}</t>
-<t>Example: taler://restore/backup.example.com/FIXME</t>
+<t>Syntax: taler://auditor/{sync_rootkey}{sync_provider_list}</t>
+<t>Example: taler://restore/backup.example.com/GJKG23V4ZBHEH45YRK7TWQE8ZTY7JWTY5094TQJSRZN5DSDBX8E0/prov1.example.com,prov2.example.com</t>
<t>Contact: N/A</t>
<t>References: [this.I-D]</t>
</list>
</t>
</section>
-<section anchor="registry-entry-error" title="Action: error">
+<section anchor="registry-entry-dev-experiment" title="Action: dev-experiment">
<t>
- An "error" action instructs the wallet to simulate a particular
+ An "dev-experiment" action instructs the wallet to simulate a particular
error scenario. This action can be used to test the user interface.
Wallets that are not in developer mode should not run
- the specified action and instead inform the user that "error"
- action are only supported in developer mode.
+ the specified action and instead inform the user that "dev-experiment"
+ actions are only supported in developer mode.
</t>
<t>
- The specific arguments of an "error" action are:
+ The specific arguments of a "dev-experiment" action are:
<list style="symbols">
- <t>name: specifies the specific type of error to be simulated</t>
+ <t>name: specifies the specific type of dev experiment</t>
</list>
</t>
<t>
<list style="symbols">
-<t>Name: error</t>
-<t>Syntax: payto://error/{name}</t>
-<t>Example: payto://error/xxx</t>
+<t>Name: dev-experiment</t>
+<t>Syntax: payto://dev-experiment/{name}</t>
+<t>Example: payto://dev-experiment/xxx</t>
<t>Contact: N/A</t>
<t>References: [this.I-D]</t>
</list>
