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

Thursday, 30 June 2016

[w3c/webpayments] Fix payment options references + proposal on recommended apps (#150) Laurent Castillo

Wednesday, 29 June 2016

FTF meeting attendance is full Ian Jacobs
Re: Updated Web Payments Architecture Summary Adrian Hope-Bailie
RE: Review ready Core Messages and HTTP API specs Telford-Reed, Nick
Review ready Core Messages and HTTP API specs Manu Sporny
Re: Updated Web Payments Architecture Summary Manu Sporny

Tuesday, 28 June 2016

PROPOSED: No meeting this week Telford-Reed, Nick

Monday, 27 June 2016

Re: Updated Web Payments Architecture Summary Adrian Hope-Bailie
Updated Web Payments Architecture Summary Manu Sporny

Saturday, 25 June 2016

Re: New Web Payments Architecture document proposal Manu Sporny

Friday, 24 June 2016

Re: [w3c/webpayments] Include the IG terminology document (#149) ianbjacobs
[w3c/webpayments] Include the IG terminology document (#149) Tommy Thorsen

Thursday, 23 June 2016

Re: [w3c/webpayments] Api shape and payment options (#148) ianbjacobs
[Minutes] Web Payments WG meeting 2016-06-23 Ian Jacobs
Re: [w3c/webpayments] Api shape and payment options (#148) Adrian Hope-Bailie
Re: [w3c/webpayments] Api shape and payment options (#148) Adrian Hope-Bailie
Re: AGENDA Adrian Hope-Bailie
Re: AGENDA Manu Sporny
Re: [w3c/webpayments] Update conformance (#147) Adrian Hope-Bailie
Re: [w3c/webpayments] Update conformance (#147) Adrian Hope-Bailie
AGENDA Adrian Hope-Bailie

Wednesday, 22 June 2016

Re: [w3c/webpayments] Registration: How is registration information updated? (#111) Adrian Hope-Bailie
Re: [w3c/webpayments] Registration: How is registration information updated? (#111) ianbjacobs
Re: [w3c/webpayments] Registration: How is registration information updated? (#111) Adrian Hope-Bailie
[w3c/webpayments] Api shape and payment options (#148) Adrian Hope-Bailie
Re: [w3c/webpayments] Update conformance (#147) Adrian Hope-Bailie
Re: [w3c/webpayments] Update conformance (#147) Adrian Hope-Bailie
Re: [w3c/webpayments] Update conformance (#147) Adrian Hope-Bailie
Re: [w3c/webpayments] Update conformance (#147) ianbjacobs
[w3c/webpayments] Update conformance (#147) Adrian Hope-Bailie
Re: [w3c/webpayments] Adding issues to payment app specification (#146) Adrian Hope-Bailie
Re: [w3c/webpayments] Adding issues to payment app specification (#146) Adrian Hope-Bailie
[w3c/webpayments] Adding issues to payment app specification (#146) Laurent Castillo
Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) Marcos Cáceres
Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) Marcos Cáceres
Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) Marcos Cáceres
Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) Ade Bateman
Re: [WICG/historical-web-payments-browser-api] Status update (#8) Marcos Cáceres
Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) Marcos Cáceres
Re: New Web Payments Architecture document proposal Ian Jacobs
Re: [w3c/webpayments] Registration: How is registration information updated? (#111) Rouslan Solomakhin
Re: [w3c/webpayments] Moved notes and issues into markers to distinguish from spec text (#145) ianbjacobs
Re: New Web Payments Architecture document proposal Manu Sporny

Tuesday, 21 June 2016

[w3c/webpayments] Moved notes and issues into markers to distinguish from spec text (#145) Adrian Hope-Bailie
Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) Adrian Hope-Bailie
Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) Rouslan Solomakhin
Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) Tri Nguyen
Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) Rouslan Solomakhin
Re: [w3c/webpayments] Use notes and issues more consistently (#144) Adrian Hope-Bailie
Re: [w3c/webpayments] Use notes and issues more consistently (#144) Adrian Hope-Bailie
Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) Adrian Hope-Bailie
Re: [w3c/webpayments] Registration: Should payment instrument details be included? (#142) Adrian Hope-Bailie
[w3c/webpayments] Use notes and issues more consistently (#144) ianbjacobs
[w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143) ianbjacobs
[w3c/webpayments] Registration: Should payment instrument details be included? (#142) ianbjacobs
Re: [w3c/webpayments] Registration: How is registration information updated? (#111) ianbjacobs
Help Required on Issues Adrian Hope-Bailie
Reminder - Interledger Workshop - 6 July - London Adrian Hope-Bailie
Re: [w3c/webpayments] What happens if there’s a failure before the payment response promise resolves? (#141) Nick Shearer

Monday, 20 June 2016

Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140) Adrian Hope-Bailie
Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140) ianbjacobs
Re: [w3c/webpayments] Choosing between javascript and http communication. (#131) Adrian Hope-Bailie
Re: [w3c/webpayments] Choosing between javascript and http communication. (#131) Adrian Hope-Bailie
Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140) Adrian Hope-Bailie
[w3c/webpayments] What happens if there’s a failure before the payment response promise resolves? (#141) Mahesh Kulkarni
Re: [w3c/webpayments] More info about UX around app recommendation and selection (#140) ianbjacobs
[w3c/webpayments] More info about UX around app recommendation and selection (#140) ianbjacobs
Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) ianbjacobs
[WICG/web-payments-browser-api] Status update (#8) ianbjacobs
Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) Ade Bateman
Re: [WICG/web-payments-browser-api] Web Payments WG relation to this repo (#7) Manu Sporny
Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71) Michael[tm] Smith
[WICG/paymentrequest] Web Payments WG relation to this repo (#71) Marcos Cáceres
[WICG/web-payments-browser-api] Web Payments WG relation to this repo (#7) Marcos Cáceres
Re: Call for reviews of HTTP API and Core Messages proposals Manu Sporny
Re: comments on web payment HTTP API and core message components Manu Sporny
Re: comments on web payment HTTP API and core message components Manu Sporny

Saturday, 18 June 2016

Re: New Web Payments Architecture document proposal Rouslan Solomakhin
Re: comments on web payment HTTP API and core message components Manu Sporny
Re: comments on web payment HTTP API and core message components Manu Sporny

Friday, 17 June 2016

New Web Payments Architecture document proposal Manu Sporny

Thursday, 16 June 2016

Wednesday, 15 June 2016

Re: [w3c/webpayments] Gh pages (#138) ianbjacobs
[w3c/webpayments] Gh pages (#138) ianbjacobs
Agenda Adrian Hope-Bailie
[w3c/webpayments] Should the browser pass user data it has collected (email etc) to the payment app? (#137) Adrian Hope-Bailie
Re: [w3c/webpayments] Some edits on @ianbjacobs refactoring (#136) ianbjacobs
[w3c/webpayments] Some edits on @ianbjacobs refactoring (#136) Adrian Hope-Bailie

Tuesday, 14 June 2016

Review: Apple Pay on the Web Anders Rundgren

Monday, 13 June 2016

Re: Apple Pay on the Web Zach Koch
Re: Apple Pay on the Web Edward O'Connor
Apple Pay on the Web Edward O'Connor

Friday, 10 June 2016

Re: WPWG meeting minutes for 2016-06-09 Adrian Hope-Bailie

Thursday, 9 June 2016

WPWG meeting minutes for 2016-06-09 Manu Sporny

Wednesday, 8 June 2016

Agenda for WG call tomorrow Adrian Hope-Bailie

Monday, 6 June 2016

[Minutes] 2 June 2016 WPWG teleconference Ian Jacobs

Thursday, 2 June 2016

Wednesday, 1 June 2016

Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) Manu Sporny
AGENDA - 2 June Adrian Hope-Bailie
Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) Tommy Thorsen
Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) Tommy Thorsen
Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) Tommy Thorsen
Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134) Manu Sporny
Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134) Manu Sporny

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