From fd319d66ebcdfcaded5083bc2a42c951fc7a32ce Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Sun, 15 May 2016 18:30:20 +0200
Subject: misc edits based on Neal's comments

---
 articles/ui/ui.tex | 21 +++++++++++++++------
 1 file changed, 15 insertions(+), 6 deletions(-)

(limited to 'articles/ui/ui.tex')

diff --git a/articles/ui/ui.tex b/articles/ui/ui.tex
index 745556dce..9c7884c3c 100644
--- a/articles/ui/ui.tex
+++ b/articles/ui/ui.tex
@@ -1225,12 +1225,6 @@ question for the future is thus whether this data collection will be
 done on behalf of the citizens and under their control, or on behalf
 of the Reich of big data corporations.
 
-We encourage readers to try our prototype for Taler
-at \url{https://demo.taler.net/}, and to ponder why the billion dollar
-e-commerce industry still relies mostly on TLS for security given
-that usability, security and privacy can clearly {\em all} be improved
-simultaneously using a modern payment protocol.
-
 % These APIs are all RESTful in the modern sense because that greatly
 % simplify integrating Taler with web shops and browsers.
 
@@ -1245,6 +1239,21 @@ thank Neal Walfield for comments on an earlier draft of the paper.
 
 \appendix
 
+We encourage readers to try our prototype for Taler
+at \url{https://demo.taler.net/}, and to ponder why the billion dollar
+e-commerce industry still relies mostly on TLS for security given
+that usability, security and privacy can clearly {\em all} be improved
+simultaneously using a modern payment protocol.
+
+The following pages include figures with more detailed illustrations
+of various payment protocols.  They are based on resources from the
+W3c Web Payments Interest Group.
+
+Figures~\ref{listing:presence} and~\ref{listing:contract} provide more
+detailed sample source code for how merchants might integrate their
+systems with Taler.
+
+
 \begin{figure*}
 \begin{center}
 \includegraphics[width=0.95\textwidth]{figs/cc3ds.pdf}
-- 
cgit v1.2.3

