gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-marketing] branch master updated: refund SHOULD be consulted


From: gnunet
Subject: [taler-marketing] branch master updated: refund SHOULD be consulted
Date: Sun, 13 Nov 2022 00:38:42 +0100

This is an automated email from the git hooks/post-receive script.

sebasjm pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new 684af09  refund SHOULD be consulted
684af09 is described below

commit 684af09b0508a4005fffaf4eaf49cf8ff4d9fee0
Author: Sebastian <sebasjm@gmail.com>
AuthorDate: Sat Nov 12 20:38:20 2022 -0300

    refund SHOULD be consulted
---
 standards/draft-grothoff-taler.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/standards/draft-grothoff-taler.xml 
b/standards/draft-grothoff-taler.xml
index a4166a9..c487de6 100644
--- a/standards/draft-grothoff-taler.xml
+++ b/standards/draft-grothoff-taler.xml
@@ -281,7 +281,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>
@@ -387,7 +387,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,

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]