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

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

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

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

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

[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 explicit note that shippingOptions is only required if requesting shipping (#128)

[w3c/browser-payment-api] Add explicit note that shippingOptions is only required if requesting… (#171)

[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 previous publication metadata. (#167)

[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 reference to issue #49. (#83)

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

[w3c/browser-payment-api] Adding baseline CONTRIBUTING.md (c5b89a3)

[w3c/browser-payment-api] Adding baseline README.md (c68b812)

[w3c/browser-payment-api] Adding support for phone and email (#174)

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

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

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

[w3c/browser-payment-api] API flow (#177)

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

[w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134)

[w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23)

[w3c/browser-payment-api] Change e.g. to e.g., (#126)

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

[w3c/browser-payment-api] codemod user agent to payment mediator in payment request (#137)

[w3c/browser-payment-api] Combine API parameters into a single request object + options (#15)

[w3c/browser-payment-api] complete does not talk to the Payment App (#129)

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

[w3c/browser-payment-api] Consider revising the design of complete() (#122)

[w3c/browser-payment-api] Constructor should not include "total" in list of items (#18)

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

[w3c/browser-payment-api] De-duplicate markup for “user agents” def (#116)

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

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

[w3c/browser-payment-api] Do we need payment method identifier aliases? (#149)

[w3c/browser-payment-api] Examples need updating with recent PRs (#164)

[w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130)

[w3c/browser-payment-api] Fix #129 (#153)

[w3c/browser-payment-api] Fix old reference to items and use total/displayItems (#169)

[w3c/browser-payment-api] fixing typo (#152)

[w3c/browser-payment-api] Flows issue 32 (#131)

[w3c/browser-payment-api] General Comment on Registry Design (#148)

[w3c/browser-payment-api] Gh pages (#114)

[w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124)

[w3c/browser-payment-api] Handling non-decimal currencies (#14)

[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] How can short payment method identifiers be successful (#123)

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

[w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113)

[w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33)

[w3c/browser-payment-api] Identifier Aliases (#149)

[w3c/browser-payment-api] Identifiers or Locators (#150)

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

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

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

[w3c/browser-payment-api] Make other Payments-drafts refs be absolute URLs (#115)

[w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133)

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

[w3c/browser-payment-api] Payment app discovery (#155)

[w3c/browser-payment-api] Payment instrument installation is platform-dependent (#8)

[w3c/browser-payment-api] Proposal to add negative value support (#120)

[w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138)

[w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141)

[w3c/browser-payment-api] Proposed text for issue 23. (#140)

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

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

[w3c/browser-payment-api] provide shipping address in PaymentResponse (#139)

[w3c/browser-payment-api] Refactor the supportedMethods and payment specific data (#162)

[w3c/browser-payment-api] Reference names should have hyphens (#125)

[w3c/browser-payment-api] Registry Access/Handling Registry Change (#151)

[w3c/browser-payment-api] Remove id attribute from PaymentItem (#160)

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

[w3c/browser-payment-api] Remove issue #14 note (#159)

[w3c/browser-payment-api] Remove issue #48 label. (#165)

[w3c/browser-payment-api] Remove issue 55 note and add security considerations section. (#142)

[w3c/browser-payment-api] Removing references to closed issues #47 and #56. (#144)

[w3c/browser-payment-api] Replace non-RFC-2119 “may”s in normative text (#117)

[w3c/browser-payment-api] Replace non-RFC-2219 “may”s in normative text (#117)

[w3c/browser-payment-api] Required fields (#176)

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

[w3c/browser-payment-api] Review and respond to Andrew Betts’ TAG review of the spec (#118)

[w3c/browser-payment-api] Separate total from line items. (#158)

[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 payment method identifier (URL) resolve to a machine readable resource that describes it? (#46)

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

[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 API support billing address capture (for tax computation)? (#27)

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

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

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

[w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8)

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

[w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132)

[w3c/browser-payment-api] Should PaymentItems have a type? (#163)

[w3c/browser-payment-api] Should show() be renamed? (#127)

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

[w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154)

[w3c/browser-payment-api] Should the list of transaction types be extensible? (#112)

[w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1)

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

[w3c/browser-payment-api] Should the payee be able to inspect the status of a payment? (#28)

[w3c/browser-payment-api] Should the payment API be more conversational or less conversational? (#51)

[w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157)

[w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2)

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

[w3c/browser-payment-api] Should the web page be able to provide status information before calling complete() (#5)

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

[w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10)

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

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

[w3c/browser-payment-api] Specification of required fields (#114)

[w3c/browser-payment-api] Specification to include Flow Diagram (#32)

[w3c/browser-payment-api] Specify shipping address fields based on OASIS xAL. (#147)

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

[w3c/browser-payment-api] Support for gift cards and discount codes (#145)

[w3c/browser-payment-api] Support for negative amounts (#119)

[w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161)

[w3c/browser-payment-api] Update Introduction to describe actors better (#121)

[w3c/browser-payment-api] Update security and privacy considerations sections (#170)

[w3c/browser-payment-api] Updated examples to reflect changes in recent PRs (#166)

[w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172)

[w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16)

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

[w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146)

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

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

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

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

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