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

[browser-payment-api] "Shown" is not inclusive enough (#71)

[browser-payment-api] [api] Change e.g. to e.g., (#66)

[browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75)

[browser-payment-api] [architecture] Reference names should have hyphens (#63)

[browser-payment-api] [architecture] SotD should indicate it is intended to be a Note (#58)

[browser-payment-api] [architecture] Use "user agent", not "browser" (#59)

[browser-payment-api] [basic] Reference trademarks (#94)

[browser-payment-api] Add a reference to issue #38 (#73)

[browser-payment-api] Add a reference to issue #39 (#77)

[browser-payment-api] Add a reference to issue #40. (#72)

[browser-payment-api] Add a reference to issue #50. (#84)

[browser-payment-api] Add a reference to issue #51. (#85)

[browser-payment-api] Add a reference to issue #53. (#86)

[browser-payment-api] Add a reference to issue #55. (#87)

[browser-payment-api] Add a reference to issue #56. (#88)

[browser-payment-api] Add issue #43 to payment request spec. (#61)

[browser-payment-api] Add reference to issue #44. (#78)

[browser-payment-api] Add reference to issue #45. (#79)

[browser-payment-api] Add reference to issue #46. (#80)

[browser-payment-api] Add reference to issue #47. (#81)

[browser-payment-api] Add reference to issue #48. (#82)

[browser-payment-api] Add reference to issue #49. (#83)

[browser-payment-api] Add reference to issue #56. (#89)

[browser-payment-api] Add section on Extensibility (#44)

[browser-payment-api] Add section on internationalization (#53)

[browser-payment-api] Add UnionPay, Correct typo on Diners (#91)

[browser-payment-api] Added respec defines to improve github links (#57)

[browser-payment-api] Alternative issue marker for issue#38 (#96)

[browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35)

[browser-payment-api] API Data Integrity (#31)

[browser-payment-api] Card Sub-Brands (#95)

[browser-payment-api] Change the way we request user data (#65)

[browser-payment-api] Different card schemes have different mandatory field requirements (#9)

[browser-payment-api] Document titles were wrong (#69)

[browser-payment-api] Editorial and some clarifications (#37)

[browser-payment-api] Fix typo (#76)

[browser-payment-api] Gh pages (#36)

[browser-payment-api] Gh pages (#90)

[browser-payment-api] Gh pages (#95)

[browser-payment-api] How are payment apps shared between different browser brands? (#38)

[browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50)

[browser-payment-api] How are web-based payment apps supported? (#39)

[browser-payment-api] How do organizations layer additional information in the core payment messages? (#40)

[browser-payment-api] How do we ensure that the payment request from the merchant is not tampered with before it gets to the payment app? (#41)

[browser-payment-api] How does the API support enrollment (aka subscription, future payment) use cases? (#52)

[browser-payment-api] Issue marker requesting security considerations section (#98)

[browser-payment-api] Make activation language more permissive (#70)

[browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42)

[browser-payment-api] Minor mod to paymentrequest.html (#62)

[browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25)

[browser-payment-api] Remove duplicate conformance language (#67)

[browser-payment-api] Remove note and add description for diagram (#74)

[browser-payment-api] Remove trailing whitespace. (#60)

[browser-payment-api] Removed references to "browser" (#92)

[browser-payment-api] Rvm4 editor (#99)

[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)

[browser-payment-api] Should a payment request be just data, or a programmable object? (#47)

[browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56)

[browser-payment-api] Should it be possible to provide amounts in more than one currency (#3)

[browser-payment-api] Should it be possible to vary amounts depending on payment method (#4)

[browser-payment-api] Should list of accepted payment methods be strings or objects? (#48)

[browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45)

[browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19)

[browser-payment-api] Should the API support field-level encryption? (#55)

[browser-payment-api] Should the payment API be more conversational vs. rigid? (#51)

[browser-payment-api] Should the payment request contain line item details? (#49)

[browser-payment-api] Should the payment request support multiple pricing options? (#54)

[browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30)

[browser-payment-api] Some friendly editorial changes (#64)

[browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22)

[browser-payment-api] Specifying Mandatory Data (#97)

[browser-payment-api] Suggest two alternative payment method identifier proposals (#34)

[browser-payment-api] Terminology across all Web Payments documents should be aligned (#43)

[browser-payment-api] User Agent should not be hyphenated (#68)

[browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11)

[browser-payment-api] Write-up initial proposal for payment app registration spec (#12)

[browser-payment-api] Write-up proposal for shipping address fields (#6)

[browser-payment-api] Wrong document names and British English (#93)

[w3c/browser-payment-api] Add a reference to issue #38 (#73)

[w3c/browser-payment-api] Add a reference to issue #39 (#77)

[w3c/browser-payment-api] Add a reference to issue #50. (#84)

[w3c/browser-payment-api] Add a reference to issue #51. (#85)

[w3c/browser-payment-api] Add a reference to issue #55. (#87)

[w3c/browser-payment-api] Add option 1b to payment method identifier spec. (#108)

[w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111)

[w3c/browser-payment-api] Add reference to issue #45. (#79)

[w3c/browser-payment-api] Add reference to issue #47. (#81)

[w3c/browser-payment-api] Add reference to issue #48. (#82)

[w3c/browser-payment-api] add rvm4 as editor on the other 3 specs (#107)

[w3c/browser-payment-api] Basic Card Payment Spec will become a Note not a Rec (#100)

[w3c/browser-payment-api] Card Sub-Brands (#95)

[w3c/browser-payment-api] complete() should take a string argument not boolean (#17)

[w3c/browser-payment-api] Currency amount (#101)

[w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38)

[w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50)

[w3c/browser-payment-api] How are web-based payment apps supported? (#39)

[w3c/browser-payment-api] Issue Prioritisation Explainer (#105)

[w3c/browser-payment-api] mark rvm4 as a new editor of the spec (#102)

[w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110)

[w3c/browser-payment-api] Payment Instrument clarification (#104)

[w3c/browser-payment-api] Resubmitting because the document moved (#106)

[w3c/browser-payment-api] Rvm4 editor (#99)

[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)

[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)

[w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3)

[w3c/browser-payment-api] Should the payment request contain line item details? (#49)

[w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30)

[w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109)

[w3c/browser-payment-api] Specifying Mandatory Data (#97)

[w3c/browser-payment-api] What component does the payment method intersection? (#103)

[w3c/browser-payment-api] What happens when currency of offer differs from currency of selected payment instrument? (#29)

Test new list

Last message date: Thursday, 31 March 2016 23:55:19 UTC