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.

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

[Editorial] Adjustments to definitions of payment method and payment method provider #848

Merged
merged 6 commits into from
Mar 14, 2019

Conversation

ianbjacobs
Copy link
Collaborator

@ianbjacobs ianbjacobs commented Mar 11, 2019

@snyderp,

In response to your observations [1] about the definitions of payment method and payment method owner, I have endeavored to make (editorial) clarifications. I welcome your feedback.

Ian

The following tasks have been completed:

  • [*] Confirmed there are no ReSpec errors/warnings.

[1] #843 (comment)


Preview | Diff

 https://www.w3.org/2019/02/28-privacy-minutes

Specifically:

 * Merged the "Security and Privacy" and "Privacy" considerations sections
  into a single "Security and Privacy Considerations"

 * Added a forward pointer from 3.5 to the canMakePayment() protections section (in security and privacy considerations). Removed the Note in the algorithm of 3.5, and merged it with the (rewritten) protections section.

 * Expanded the canMakePayment protections section based on PING conversation.
- Removed "alert the user" as an idea; deemed impractical
and payment method provider based on:
 #843 (comment)

Ian
@pes10k
Copy link

pes10k commented Mar 11, 2019

@ianbjacobs this is much clearer to me. Thanks much for the tweaks!

@marcoscaceres marcoscaceres self-requested a review March 11, 2019 20:45
@marcoscaceres marcoscaceres merged commit 768128f into gh-pages Mar 14, 2019
@marcoscaceres marcoscaceres deleted the pm-dfn-201903 branch March 14, 2019 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants