Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Some friendly editorial changes #64

Closed
wants to merge 3 commits into from
Closed

Some friendly editorial changes #64

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a944bf3
Some friendly editorial changes
halindrome Mar 15, 2016
c573044
Updated definition to make it more precise.
halindrome Mar 17, 2016
417f86b
Update architecture.html
halindrome Mar 24, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions specs/architecture.html
View file
Open in desktop
Expand Up @@ -223,7 +223,7 @@ <h2>Specifications</h2>

<p>The Payment Request Architecture organizes the above concepts into several component specifications
so that they can be discussed and moved forward independently. The
<a href="#payment-method-identifiers">Payment Method Identifiers</a> specification the only
<a href="#payment-method-identifiers">Payment Method Identifiers</a> specification is the only
common dependency. The following diagram shows the references between different specifications that describe
the Payment Request Architecture. The arrows show normative references pointing from the referring
document to the referenced document.
Expand Down Expand Up @@ -327,7 +327,7 @@ <h2>Relationship to Previous Concepts</h2>
<ul>
<li>
In the physical world it is not practical for users to have multiple wallets. On the Web this is
possible and for there to be a copies of the same payment method data in more than one wallet.</li>
possible and for there to be copies of the same payment method data in more than one wallet.</li>
<li> In the physical world the process of deciding how to pay is not done by the wallet, it is done by
the user. On the Web the process of selection can be facilitated by digital algorithms that are capable
of processing complex data and relationships to assist the user in deciding how to pay.</li>
Expand All @@ -348,7 +348,7 @@ <h2>Relationship to Previous Concepts</h2>
<tr>
<td>Payment App</td>
<td>Digital Wallet, Payment Instrument </td>
<td>A piece of software to pay</td>
<td>A piece of software to manage payment methods and coordinate the issuance of payments.</td>
</tr>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A payment app does not manage payment methods. It supports a specific set of payment methods of which only a subset may be enabled because the user may have only configured the app with the necessary information (like payment instrument credentials) for certain methods.

I also don't like the wording "issuance of payments".

Proposed change:

<td>An application, registered by the payer, that supports 
processing payment requests and returning payment responses 
for one or more payment methods.</td>

<tr>
<td>Payment Method</td>
Expand All @@ -358,7 +358,7 @@ <h2>Relationship to Previous Concepts</h2>
<tr>
<td>Payment Mediator</td>
<td>Digital Wallet, Payment Instrument</td>
<td>A piece of software that coordinates messages between Web apps and Payment apps</td>
<td>A piece of software that coordinates messages between sellers and Payment apps</td>
</tr>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't agree with this change. The messages are exchanged between the website and the payment app via the mediator.

</table>
</section>
Expand Down