marketing

commit 33a4163b534d5b3df42dcc3c59c86585d920b4d9
parent e7790f040ccef3db38473bfd62d3597f4cc13a7a
Author: Christian Grothoff <christian@grothoff.org>
Date:   Wed, 16 Nov 2022 15:48:39 +0100

merge

Diffstat:
M
standards/draft-grothoff-taler.xml
 | 
18
++++++++++--------

1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/standards/draft-grothoff-taler.xml b/standards/draft-grothoff-taler.xml
@@ -116,7 +116,7 @@
   </t>
   <figure>
   <artwork type="abnf"><![CDATA[
-  taler-URI = ("taler://" / "TALER://" / "taler+http" / "TALER+HTTP" )
+  taler-URI = ("taler://" / "TALER://" / "taler+http://" / "TALER+HTTP://" )
               action path-abempty [ "?" opts ]
   action = ALPHA *( ALPHA / DIGIT / "-" / "." )
   opts = opt *( "&" opt )
@@ -259,7 +259,7 @@ 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>ct: a high-entropy order "ClaimToken"</t> 
+   <t>ct: a high-entropy order "ClaimToken"</t>
   </list>
 </t>
 <t>
@@ -276,7 +276,7 @@ also <xref target="taler-registry" />).
 <section anchor="registry-entry-refund" title="Action: refund">
   <t>
     A "refund" action instructs the wallet to download information about
-    an available refund, possibly consult the user about the refund, and
+    an available refund. Wallet SHOULD consult the user about the refund and
     then obtain the refund for an already paid order.
   </t>
   <t>
@@ -382,7 +382,7 @@ also <xref target="taler-registry" />).
    are not specified in the argument list must not be submitted.
  </t>
  <t>
-   Wallets do not have to support users entering all possible fields
+   Wallets MAY to support users entering all possible fields
    of a contract.  Keys that MUST be supported at this time are the
    "amount" and the "summary" fields.  The wallet MUST validate that
    the amount entered by the user is well-formed.  For the amount,
@@ -431,13 +431,14 @@ also <xref target="taler-registry" />).
   <list style="symbols">
     <t>exchange_host: hostname of the exchange (possibly including a port number)</t>
     <t>exchange_prefix_path: list of path components that identifies the path prefix of the exchange base URL</t>
+    <t>exchange_pub: the public key of the exchange</t>
   </list>
 </t>
 <t>
 <list style="symbols">
 <t>Name: exchange</t>
-<t>Syntax: taler://exchange/{exchange_host}{/exchange_prefix_path*}/</t>
-<t>Example: taler://exchange/exchange.example.com/</t>
+<t>Syntax: taler://exchange/{exchange_host}{/exchange_prefix_path*}/{exchange_pub}</t>
+<t>Example: taler://exchange/exchange.example.com/ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOP</t>
 <t>Contact: N/A</t>
 <t>References: [this.I-D]</t>
 </list>
@@ -454,13 +455,14 @@ also <xref target="taler-registry" />).
   <list style="symbols">
     <t>auditor_host: the hostname of the auditor (possibly including a port number)</t>
     <t>auditor_prefix_path: list of path components that identifies the path prefix of the auditor base URL</t>
+    <t>auditor_pub: the public key of the auditor</t>
   </list>
 </t>
 <t>
 <list style="symbols">
 <t>Name: auditor</t>
-<t>Syntax: taler://auditor/{auditor_host}{/auditor_prefix_path*}/</t>
-<t>Example: taler://auditor/auditor.example.com/</t>
+<t>Syntax: taler://auditor/{auditor_host}{/auditor_prefix_path*}/{auditor_pub}</t>
+<t>Example: taler://auditor/auditor.example.com/ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOP</t>
 <t>Contact: N/A</t>
 <t>References: [this.I-D]</t>
 </list>