public-webpayments-specs@w3.org from October 2016 by subject

[w3c/browser-payment-api] Add Guidance Text for User Consent (#229)

• Jeff Burdges (Friday, 21 October)
• ianbjacobs (Wednesday, 19 October)
• ianbjacobs (Wednesday, 19 October)
• Lukasz Olejnik (Friday, 7 October)
• ianbjacobs (Thursday, 6 October)

[w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291)

• Adrian Hope-Bailie (Monday, 17 October)
• Manu Sporny (Friday, 14 October)
• Manu Sporny (Friday, 14 October)
• Manu Sporny (Friday, 14 October)
• Adrian Hope-Bailie (Thursday, 13 October)
• Manu Sporny (Wednesday, 12 October)
• Dave Longley (Wednesday, 12 October)
• ianbjacobs (Wednesday, 12 October)
• Manu Sporny (Wednesday, 12 October)
• Manu Sporny (Wednesday, 12 October)
• ianbjacobs (Wednesday, 12 October)
• Manu Sporny (Wednesday, 12 October)
• Manu Sporny (Wednesday, 12 October)

[w3c/browser-payment-api] Introduce transaction_id and server callback (#292)

• Zach Koch (Friday, 28 October)
• Zach Koch (Tuesday, 25 October)
• Adrian Hope-Bailie (Tuesday, 25 October)
• Dave Longley (Thursday, 20 October)
• ianbjacobs (Thursday, 20 October)
• Dave Longley (Thursday, 20 October)
• ianbjacobs (Wednesday, 19 October)
• rvm4 (Wednesday, 19 October)

[w3c/browser-payment-api] notifying the payment app when a payment is complete (#286)

• Adrian Hope-Bailie (Monday, 10 October)
• Shane McCarron (Thursday, 6 October)
• Adrian Hope-Bailie (Thursday, 6 October)
• Shane McCarron (Thursday, 6 October)

[w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287)

• mattsaxon (Wednesday, 12 October)
• Andre Lyver (Friday, 7 October)

[w3c/browser-payment-api] Supporting push payment methods (#224)

• ianbjacobs (Tuesday, 18 October)

[w3c/webpayments-methods-card] Add privacy and security section (#8)

• adamroach (Thursday, 6 October)

[w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17)

• adamroach (Thursday, 6 October)
• adamroach (Thursday, 6 October)
• adamroach (Thursday, 6 October)
• Adrian Hope-Bailie (Tuesday, 4 October)
• adamroach (Monday, 3 October)

[w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#18)

• adamroach (Thursday, 6 October)

[w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16)

• ianbjacobs (Thursday, 6 October)
• adamroach (Thursday, 6 October)
• ianbjacobs (Tuesday, 4 October)
• adamroach (Monday, 3 October)

[w3c/webpayments-payment-apps-api] Add note to design considerations about ephemeral data for unregistered apps and step in invokation procedure (#65)

• ianbjacobs (Wednesday, 19 October)
• Jason Normore (Wednesday, 19 October)

[w3c/webpayments-payment-apps-api] Cleaned up text (#52)

• ianbjacobs (Thursday, 6 October)
• ianbjacobs (Thursday, 6 October)

[w3c/webpayments-payment-apps-api] Editorial fixes and clarifications (#66)

• ianbjacobs (Wednesday, 19 October)
• ianbjacobs (Wednesday, 19 October)

[w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62)

• ianbjacobs (Thursday, 6 October)
• ianbjacobs (Thursday, 6 October)
• ianbjacobs (Tuesday, 4 October)

[w3c/webpayments-payment-apps-api] Should merchants be able to limit matching to trusted apps? (#1)

• ianbjacobs (Friday, 14 October)

[w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63)

• adamroach (Wednesday, 19 October)
• ianbjacobs (Wednesday, 19 October)
• ianbjacobs (Friday, 14 October)

[w3c/webpayments-payment-apps-api] Update (#64)

• ianbjacobs (Wednesday, 19 October)
• ianbjacobs (Wednesday, 19 October)

Last message date: Friday, 28 October 2016 01:32:35 UTC