taler/wallet-core
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Activity

Minor tweaks to ui paper

Browse Source
This commit is contained in:
Jeff Burdges 2016-10-01 10:56:55 -04:00
parent 76bdfcb989
commit 9b471718e3
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
articles/ui/ui.bib
View File

@ -1,9 +1,9 @@
@Misc{pigs, @Misc{w3cpig,
author = {W3c}, author = {W3C},
title = {Web Payments Payment Flows}, title = {Web Payments Payment Flows},
howpublished = {\url{https://github.com/w3c/webpayments/tree/gh-pages/PaymentFlows}}, howpublished = {\url{https://github.com/w3c/webpayments-flows/tree/gh-pages/TargetFlows}},
month = {February}, month = {February},
year = {2016}, year = {2016},
} }

10
articles/ui/ui.tex
View File

@ -174,7 +174,7 @@ protocols.\footnote{Details of the protocol are documented at
\url{https://api.taler.net/}} The basic cryptography behind \url{https://api.taler.net/}} The basic cryptography behind
blind-signature based payment systems has been known for over 25 blind-signature based payment systems has been known for over 25
years~\cite{chaum1990untraceable}. However, it was not until 2015 that the W3C years~\cite{chaum1990untraceable}. However, it was not until 2015 that the W3C
started the payments working group~\cite{pigs} to explore requirements started the payments working group~\cite{w3cpig} to explore requirements
for deploying payment systems that are more secure and easy to use for for deploying payment systems that are more secure and easy to use for
the Web. Our work describes how a modern payment system using blind the Web. Our work describes how a modern payment system using blind
signatures could practically be integrated with the modern Web to signatures could practically be integrated with the modern Web to
@ -263,7 +263,7 @@ issued by the customer's bank.
\begin{center} \begin{center}
\includegraphics[width=0.95\textwidth]{figs/cc3ds.pdf} \includegraphics[width=0.95\textwidth]{figs/cc3ds.pdf}
\end{center} \end{center}
\caption{Card payment processing with 3-D Secure (3DS). (From: W3C Web Payments IG.)} \caption{Card payment processing with 3-D Secure (3DS). (From: W3C Web Payments WG \cite{w3cpig})}
\label{fig:cc3ds} \label{fig:cc3ds}
\end{figure*} \end{figure*}
%KG: I hope they can print this larger, because this is WAY too small to be of any use. %KG: I hope they can print this larger, because this is WAY too small to be of any use.
@ -291,7 +291,7 @@ of this, the data entry is often performed on a Web site that
is operated by a third-party payment processor and {\em not} the merchant or is operated by a third-party payment processor and {\em not} the merchant or
the customer's bank. Figure~\ref{fig:cc3ds} shows a typical card-based payment the customer's bank. Figure~\ref{fig:cc3ds} shows a typical card-based payment
process on the Web using the UML style of the W3C payment interest process on the Web using the UML style of the W3C payment interest
group~\cite{pigs}. Most of the details are not relevant to this group~\cite{w3cpig}. Most of the details are not relevant to this
paper, but the diagram nicely illustrates the complexity of the common paper, but the diagram nicely illustrates the complexity of the common
3-D secure process. 3-D secure process.
%KG: Define 3DS the FIRST time you use it. %KG: Define 3DS the FIRST time you use it.
@ -355,7 +355,7 @@ online shopping~\cite[p. 50]{ibi2014}.
\begin{figure*}[b!] \begin{figure*}[b!]
\includegraphics[width=\textwidth]{figs/bitcoin.pdf} \includegraphics[width=\textwidth]{figs/bitcoin.pdf}
\caption{Bitcoin payment processing. (From: W3C Web Payments IG.)} \caption{Bitcoin payment processing. (From: W3C Web Payments WG \cite{w3cpig})}
\label{fig:bitcoin} \label{fig:bitcoin}
\end{figure*} \end{figure*}
@ -1549,7 +1549,7 @@ at \url{https://demo.taler.net/}.
This work benefits from the financial support of the Brittany Region This work benefits from the financial support of the Brittany Region
(ARED 9178) and a grant from the Renewable Freedom Foundation. We (ARED 9178) and a grant from the Renewable Freedom Foundation. We
thank Bruno Haible for his financial support enabling us to thank Bruno Haible for his financial support enabling us to
participate with the W3c payment working group. We thank the W3C participate with the W3C payment working group. We thank the W3C
payment working group for insightful discussions about Web payments. payment working group for insightful discussions about Web payments.
We thank Krista Grothoff and Neal Walfield for comments on an earlier We thank Krista Grothoff and Neal Walfield for comments on an earlier
draft of the paper. We thank Gabor Toth for his help with the draft of the paper. We thank Gabor Toth for his help with the