public-payments-wg@w3.org from June 2016 by author

Ade Bateman

• Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Wednesday, 22 June)
• Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Monday, 20 June)

Adrian Hope-Bailie

• Re: Updated Web Payments Architecture Summary (Wednesday, 29 June)
• Re: Updated Web Payments Architecture Summary (Monday, 27 June)
• Re: [w3c/webpayments] Api shape and payment options (#148) (Thursday, 23 June)
• Re: [w3c/webpayments] Api shape and payment options (#148) (Thursday, 23 June)
• Re: AGENDA (Thursday, 23 June)
• Re: [w3c/webpayments] Update conformance (#147) (Thursday, 23 June)
• Re: [w3c/webpayments] Update conformance (#147) (Thursday, 23 June)
• AGENDA (Thursday, 23 June)
• Re: [w3c/webpayments] Registration: How is registration information updated? (#111) (Wednesday, 22 June)
• Re: [w3c/webpayments] Registration: How is registration information updated? (#111) (Wednesday, 22 June)
• [w3c/webpayments] Api shape and payment options (#148) (Wednesday, 22 June)
• Re: [w3c/webpayments] Update conformance (#147) (Wednesday, 22 June)
• Re: [w3c/webpayments] Update conformance (#147) (Wednesday, 22 June)
• Re: [w3c/webpayments] Update conformance (#147) (Wednesday, 22 June)
• [w3c/webpayments] Update conformance (#147) (Wednesday, 22 June)
• Re: [w3c/webpayments] Adding issues to payment app specification (#146) (Wednesday, 22 June)
• Re: [w3c/webpayments] Adding issues to payment app specification (#146) (Wednesday, 22 June)
• [w3c/webpayments] Moved notes and issues into markers to distinguish from spec text (#145) (Tuesday, 21 June)
• Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) (Tuesday, 21 June)
• Re: [w3c/webpayments] Use notes and issues more consistently (#144) (Tuesday, 21 June)
• Re: [w3c/webpayments] Use notes and issues more consistently (#144) (Tuesday, 21 June)
• Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) (Tuesday, 21 June)
• Re: [w3c/webpayments] Registration: Should payment instrument details be included? (#142) (Tuesday, 21 June)
• Help Required on Issues (Tuesday, 21 June)
• Reminder - Interledger Workshop - 6 July - London (Tuesday, 21 June)
• Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140) (Monday, 20 June)
• Re: [w3c/webpayments] Choosing between javascript and http communication. (#131) (Monday, 20 June)
• Re: [w3c/webpayments] Choosing between javascript and http communication. (#131) (Monday, 20 June)
• Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140) (Monday, 20 June)
• Agenda (Wednesday, 15 June)
• [w3c/webpayments] Should the browser pass user data it has collected (email etc) to the payment app? (#137) (Wednesday, 15 June)
• [w3c/webpayments] Some edits on @ianbjacobs refactoring (#136) (Wednesday, 15 June)
• Re: WPWG meeting minutes for 2016-06-09 (Friday, 10 June)
• Agenda for WG call tomorrow (Wednesday, 8 June)
• AGENDA - 2 June (Wednesday, 1 June)

Anders Rundgren

• Review: Apple Pay on the Web (Tuesday, 14 June)

Edward O'Connor

• Re: Apple Pay on the Web (Monday, 13 June)
• Apple Pay on the Web (Monday, 13 June)

Ian Jacobs

• FTF meeting attendance is full (Wednesday, 29 June)
• [Minutes] Web Payments WG meeting 2016-06-23 (Thursday, 23 June)
• Re: New Web Payments Architecture document proposal (Wednesday, 22 June)
• [Minutes] 16 June WPWG teleconference (Thursday, 16 June)
• [Minutes] 2 June 2016 WPWG teleconference (Monday, 6 June)

ianbjacobs

• Re: [w3c/webpayments] Include the IG terminology document (#149) (Friday, 24 June)
• Re: [w3c/webpayments] Api shape and payment options (#148) (Thursday, 23 June)
• Re: [w3c/webpayments] Registration: How is registration information updated? (#111) (Wednesday, 22 June)
• Re: [w3c/webpayments] Update conformance (#147) (Wednesday, 22 June)
• Re: [w3c/webpayments] Moved notes and issues into markers to distinguish from spec text (#145) (Wednesday, 22 June)
• [w3c/webpayments] Use notes and issues more consistently (#144) (Tuesday, 21 June)
• [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) (Tuesday, 21 June)
• [w3c/webpayments] Registration: Should payment instrument details be included? (#142) (Tuesday, 21 June)
• Re: [w3c/webpayments] Registration: How is registration information updated? (#111) (Tuesday, 21 June)
• Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140) (Monday, 20 June)
• Re: [w3c/webpayments] More info about UX around app recommendation and selection (#140) (Monday, 20 June)
• [w3c/webpayments] More info about UX around app recommendation and selection (#140) (Monday, 20 June)
• Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Monday, 20 June)
• [WICG/web-payments-browser-api] Status update (#8) (Monday, 20 June)
• Re: [w3c/webpayments] Editorial changes for more context (#139) (Thursday, 16 June)
• [w3c/webpayments] Editorial changes for more context (#139) (Thursday, 16 June)
• Re: [w3c/webpayments] Editorial changes for more context (#139) (Thursday, 16 June)
• Re: [w3c/webpayments] Gh pages (#138) (Wednesday, 15 June)
• [w3c/webpayments] Gh pages (#138) (Wednesday, 15 June)
• Re: [w3c/webpayments] Some edits on @ianbjacobs refactoring (#136) (Wednesday, 15 June)

Laurent Castillo

• [w3c/webpayments] Fix payment options references + proposal on recommended apps (#150) (Thursday, 30 June)
• [w3c/webpayments] Adding issues to payment app specification (#146) (Wednesday, 22 June)

Mahesh Kulkarni

• [w3c/webpayments] What happens if there’s a failure before the payment response promise resolves? (#141) (Monday, 20 June)

Manu Sporny

• Review ready Core Messages and HTTP API specs (Wednesday, 29 June)
• Re: Updated Web Payments Architecture Summary (Wednesday, 29 June)
• Updated Web Payments Architecture Summary (Monday, 27 June)
• Re: New Web Payments Architecture document proposal (Saturday, 25 June)
• Re: AGENDA (Thursday, 23 June)
• Re: New Web Payments Architecture document proposal (Wednesday, 22 June)
• Re: [WICG/web-payments-browser-api] Web Payments WG relation to this repo (#7) (Monday, 20 June)
• Re: Call for reviews of HTTP API and Core Messages proposals (Monday, 20 June)
• Re: comments on web payment HTTP API and core message components (Monday, 20 June)
• Re: comments on web payment HTTP API and core message components (Monday, 20 June)
• Re: comments on web payment HTTP API and core message components (Saturday, 18 June)
• Re: comments on web payment HTTP API and core message components (Saturday, 18 June)
• New Web Payments Architecture document proposal (Friday, 17 June)
• Re: [w3c/webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112) (Thursday, 16 June)
• Re: [w3c/webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112) (Thursday, 16 June)
• WPWG meeting minutes for 2016-06-09 (Thursday, 9 June)
• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Wednesday, 1 June)
• Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134) (Wednesday, 1 June)
• Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134) (Wednesday, 1 June)

Marcos Cáceres

• Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Wednesday, 22 June)
• Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Wednesday, 22 June)
• Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Wednesday, 22 June)
• Re: [WICG/historical-web-payments-browser-api] Status update (#8) (Wednesday, 22 June)
• Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Wednesday, 22 June)
• [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Monday, 20 June)
• [WICG/web-payments-browser-api] Web Payments WG relation to this repo (#7) (Monday, 20 June)

Michael[tm] Smith

• Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) (Monday, 20 June)

Nick Shearer

• Re: [w3c/webpayments] What happens if there’s a failure before the payment response promise resolves? (#141) (Tuesday, 21 June)

Rouslan Solomakhin

• Re: [w3c/webpayments] Registration: How is registration information updated? (#111) (Wednesday, 22 June)
• Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) (Tuesday, 21 June)
• Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) (Tuesday, 21 June)
• Re: New Web Payments Architecture document proposal (Saturday, 18 June)

Telford-Reed, Nick

• RE: Review ready Core Messages and HTTP API specs (Wednesday, 29 June)
• PROPOSED: No meeting this week (Tuesday, 28 June)

Tommy Thorsen

• [w3c/webpayments] Include the IG terminology document (#149) (Friday, 24 June)
• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Thursday, 2 June)
• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Thursday, 2 June)
• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Wednesday, 1 June)
• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Wednesday, 1 June)
• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Wednesday, 1 June)

Tri Nguyen

• Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) (Tuesday, 21 June)

Zach Koch

• Re: Apple Pay on the Web (Monday, 13 June)

Last message date: Thursday, 30 June 2016 16:22:51 UTC