public-webpayments-specs@w3.org from April 2016 by thread

[w3c/browser-payment-api] API flow (#177) mattsaxon (Friday, 29 April)

[w3c/browser-payment-api] Required fields (#176) mattsaxon (Friday, 29 April)

[w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Ade Bateman (Friday, 29 April)

[w3c/browser-payment-api] Adding support for phone and email (#174) Ade Bateman (Friday, 29 April)

Re: [w3c/browser-payment-api] Add section on internationalization (#53) Ade Bateman (Friday, 29 April)

Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Adrian Hope-Bailie (Friday, 29 April)

[w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) Adrian Hope-Bailie (Friday, 29 April)

[w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172) Ade Bateman (Friday, 29 April)

[w3c/browser-payment-api] Add explicit note that shippingOptions is only required if requesting… (#171) Ade Bateman (Friday, 29 April)

[w3c/browser-payment-api] Update security and privacy considerations sections (#170) Ade Bateman (Friday, 29 April)

[w3c/browser-payment-api] Fix old reference to items and use total/displayItems (#169) Ade Bateman (Thursday, 28 April)

[w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Ade Bateman (Thursday, 28 April)

[w3c/browser-payment-api] Add previous publication metadata. (#167) Ade Bateman (Thursday, 28 April)

[w3c/browser-payment-api] Updated examples to reflect changes in recent PRs (#166) Ade Bateman (Thursday, 28 April)

[w3c/browser-payment-api] Remove issue #48 label. (#165) Ade Bateman (Thursday, 28 April)

[w3c/browser-payment-api] Examples need updating with recent PRs (#164) Ade Bateman (Thursday, 28 April)

[w3c/browser-payment-api] Should PaymentItems have a type? (#163) rvm4 (Thursday, 28 April)

[w3c/browser-payment-api] Refactor the supportedMethods and payment specific data (#162) Ade Bateman (Wednesday, 27 April)

[w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Ade Bateman (Wednesday, 27 April)

[w3c/browser-payment-api] Remove id attribute from PaymentItem (#160) Ade Bateman (Wednesday, 27 April)

[w3c/browser-payment-api] Remove issue #14 note (#159) Ade Bateman (Wednesday, 27 April)

[w3c/browser-payment-api] Separate total from line items. (#158) Ade Bateman (Wednesday, 27 April)

[w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) Adrian Hope-Bailie (Monday, 25 April)

[w3c/browser-payment-api] De-duplicate markup for “user agents” def (#156) HubleGiter (Monday, 25 April)

Re: [w3c/browser-payment-api] Adding baseline CONTRIBUTING.md (c5b89a3) HubleGiter (Sunday, 24 April)

Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) ianbjacobs (Sunday, 24 April)

[w3c/browser-payment-api] Payment app discovery (#155) Andrew Paliga (Friday, 22 April)

[w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Adrian Hope-Bailie (Friday, 22 April)

Re: [w3c/browser-payment-api] Adding baseline README.md (c68b812) HubleGiter (Friday, 22 April)

[w3c/browser-payment-api] Fix #129 (#153) Adrian Hope-Bailie (Friday, 22 April)

Re: [w3c/browser-payment-api] Handling non-decimal currencies (#14) Adrian Hope-Bailie (Friday, 22 April)

Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) ianbjacobs (Thursday, 21 April)

[w3c/browser-payment-api] fixing typo (#152) Erik Wilde (Thursday, 21 April)

[w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) Erik Wilde (Thursday, 21 April)

[w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde (Thursday, 21 April)

[w3c/browser-payment-api] Identifier Aliases (#149) Erik Wilde (Thursday, 21 April)

[w3c/browser-payment-api] General Comment on Registry Design (#148) Erik Wilde (Thursday, 21 April)

[w3c/browser-payment-api] Specify shipping address fields based on OASIS xAL. (#147) Rouslan Solomakhin (Thursday, 21 April)

Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Adrian Hope-Bailie (Thursday, 21 April)

Re: [w3c/browser-payment-api] Change the way we request user data (#65) David Jackson (Wednesday, 20 April)

Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Manu Sporny (Wednesday, 20 April)

Re: [w3c/browser-payment-api] Issue Prioritisation Explainer (#105) Adrian Hope-Bailie (Wednesday, 20 April)

Re: [w3c/browser-payment-api] Payment instrument installation is platform-dependent (#8) Adrian Hope-Bailie (Wednesday, 20 April)

Re: [w3c/browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie (Wednesday, 20 April)

Re: [w3c/browser-payment-api] Write-up initial proposal for payment app registration spec (#12) Adrian Hope-Bailie (Wednesday, 20 April)

Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Adrian Hope-Bailie (Wednesday, 20 April)

Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Adrian Hope-Bailie (Wednesday, 20 April)

[w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Adrian Hope-Bailie (Wednesday, 20 April)

[w3c/browser-payment-api] Support for gift cards and discount codes (#145) Andrew Paliga (Tuesday, 19 April)

[w3c/browser-payment-api] Removing references to closed issues #47 and #56. (#144) Ade Bateman (Tuesday, 19 April)

[w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs (Tuesday, 19 April)

[w3c/browser-payment-api] Remove issue 55 note and add security considerations section. (#142) Ade Bateman (Tuesday, 19 April)

Re: [w3c/browser-payment-api] Should a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) Adrian Hope-Bailie (Tuesday, 19 April)

Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) Adrian Hope-Bailie (Tuesday, 19 April)

[w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) Adrian Hope-Bailie (Tuesday, 19 April)

Re: [w3c/browser-payment-api] Add reference to issue #49. (#83) Ade Bateman (Monday, 18 April)

Re: [w3c/browser-payment-api] Should the payment API be more conversational or less conversational? (#51) Ade Bateman (Monday, 18 April)

[w3c/browser-payment-api] Proposed text for issue 23. (#140) Ade Bateman (Monday, 18 April)

[w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) rvm4 (Monday, 18 April)

Re: [w3c/browser-payment-api] Should a payment request be just data, or a programmable object? (#47) Ade Bateman (Monday, 18 April)

Re: [w3c/browser-payment-api] [architecture] Reference names should have hyphens (#63) Zach Koch (Monday, 18 April)

Re: [w3c/browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) Ade Bateman (Monday, 18 April)

Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) Ade Bateman (Monday, 18 April)

Re: [w3c/browser-payment-api] Should the payee be able to inspect the status of a payment? (#28) Ade Bateman (Monday, 18 April)

[w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie (Tuesday, 12 April)

Re: [w3c/browser-payment-api] [api] Change e.g. to e.g., (#66) rvm4 (Sunday, 10 April)

[w3c/browser-payment-api] codemod user agent to payment mediator in payment request (#137) rvm4 (Sunday, 10 April)

[w3c/browser-payment-api] provide partial shipping address in PaymentRequest and full shipping … (#136) rvm4 (Sunday, 10 April)

[w3c/browser-payment-api] provide partial shipping address in PaymentRequest and full shipping … (#135) rvm4 (Sunday, 10 April)

Re: [w3c/browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) rvm4 (Sunday, 10 April)

[w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) Gregory Estrade (Sunday, 10 April)

Re: [w3c/browser-payment-api] Should the messages support field-level encryption? (#55) Adrian Hope-Bailie (Sunday, 10 April)

Re: [w3c/browser-payment-api] Should list of accepted payment methods be strings or objects? (#48) Adrian Hope-Bailie (Sunday, 10 April)

Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Adrian Hope-Bailie (Sunday, 10 April)

[w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Adrian Hope-Bailie (Sunday, 10 April)

[w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Adrian Hope-Bailie (Sunday, 10 April)

Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Wayne Carr (Sunday, 10 April)

Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) djackso3 (Friday, 8 April)

Re: [w3c/browser-payment-api] Specification to include Flow Diagram (#32) mattsaxon (Friday, 8 April)

[w3c/browser-payment-api] Flows issue 32 (#131) mattsaxon (Friday, 8 April)

[w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Axel Nennker (Friday, 8 April)

[w3c/browser-payment-api] complete does not talk to the Payment App (#129) Axel Nennker (Friday, 8 April)

Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Adrian Hope-Bailie (Thursday, 7 April)

Re: [w3c/browser-payment-api] Should the web page be able to provide status information before calling complete() (#5) Adrian Hope-Bailie (Thursday, 7 April)

Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1) Adrian Hope-Bailie (Thursday, 7 April)

[w3c/browser-payment-api] Add explicit note that shippingOptions is only required if requesting shipping (#128) Adrian Hope-Bailie (Thursday, 7 April)

Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) Adrian Hope-Bailie (Thursday, 7 April)

Re: [w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23) Adrian Hope-Bailie (Thursday, 7 April)

Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) Adrian Hope-Bailie (Thursday, 7 April)

[w3c/browser-payment-api] Should show() be renamed? (#127) Adrian Hope-Bailie (Thursday, 7 April)

Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16) Adrian Hope-Bailie (Thursday, 7 April)

[w3c/browser-payment-api] Change e.g. to e.g., (#126) Ade Bateman (Thursday, 7 April)

[w3c/browser-payment-api] Reference names should have hyphens (#125) Ade Bateman (Thursday, 7 April)

Re: [w3c/browser-payment-api] Basic Card Payment Spec will become a Note not a Rec (#100) Ade Bateman (Thursday, 7 April)

Re: [w3c/browser-payment-api] [architecture] SotD should indicate it is intended to be a Note (#58) Ade Bateman (Thursday, 7 April)

[w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) rvm4 (Thursday, 7 April)

[w3c/browser-payment-api] How can short payment method identifiers be successful (#123) rvm4 (Thursday, 7 April)

Re: [w3c/browser-payment-api] Change the way we request user data (#65) kirkalx (Wednesday, 6 April)

Re: [w3c/browser-payment-api] API Data Integrity (#31) ianbjacobs (Monday, 4 April)

Re: [w3c/browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Adrian Hope-Bailie (Monday, 4 April)

[w3c/browser-payment-api] Consider revising the design of complete() (#122) Adrian Hope-Bailie (Monday, 4 April)

Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Adrian Hope-Bailie (Monday, 4 April)

[w3c/browser-payment-api] Update Introduction to describe actors better (#121) Adrian Hope-Bailie (Monday, 4 April)

[w3c/browser-payment-api] Proposal to add negative value support (#120) Adrian Hope-Bailie (Monday, 4 April)

[w3c/browser-payment-api] Support for negative amounts (#119) Adrian Hope-Bailie (Monday, 4 April)

[w3c/browser-payment-api] Review and respond to Andrew Betts’ TAG review of the spec (#118) Michael[tm] Smith (Sunday, 3 April)

[w3c/browser-payment-api] Replace non-RFC-2219 “may”s in normative text (#117) Michael[tm] Smith (Sunday, 3 April)

[w3c/browser-payment-api] De-duplicate markup for “user agents” def (#116) Michael[tm] Smith (Sunday, 3 April)

[w3c/browser-payment-api] Make other Payments-drafts refs be absolute URLs (#115) Michael[tm] Smith (Saturday, 2 April)

[w3c/browser-payment-api] Gh pages (#114) mattsaxon (Saturday, 2 April)

Re: [w3c/browser-payment-api] Add reference to issue #45. (#79) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) Manu Sporny (Friday, 1 April)

Re: [w3c/browser-payment-api] Add option 1b to payment method identifier spec. (#108) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Resubmitting because the document moved (#106) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Issue marker requesting security considerations section (#98) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Alternative issue marker for issue#38 (#96) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Add a reference to issue #55. (#87) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Add a reference to issue #51. (#85) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Add a reference to issue #50. (#84) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Add reference to issue #48. (#82) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Add reference to issue #47. (#81) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Add a reference to issue #39 (#77) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Some friendly editorial changes (#64) Ade Bateman (Friday, 1 April)

Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) mattsaxon (Friday, 1 April)

[w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Adrian Hope-Bailie (Friday, 1 April)

[w3c/browser-payment-api] Should the list of transaction types be extensible? (#112) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] Should a payment app identifier (URL) or a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] Should the payment request contain line item details? (#49) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) Adrian Hope-Bailie (Friday, 1 April)

Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Jason Normore (Friday, 1 April)

Last message date: Saturday, 30 April 2016 21:07:34 UTC