Warning:
This wiki has been archived and is now read-only.

Main Page/FTF Oct2015

From Web Commerce Interest Group
Jump to: navigation, search

Meeting pages for the Web Payments Interest Group and future Web Payments Working Group, which plan to meet during TPAC 2015. Questions? Ian Jacobs <ij@w3.org> or Doug Schepers <schepers@w3.org>.

See also:

Minutes

Interest Group Agenda

Goals

  • Review and update the strategic plan of the Interest Group
  • Reach consensus on the next standardization priority and develop a plan and timeline for the creation and socialization of a new Working Group Charter.
    • Q. How do we get proposals in advance of the meeting?

Detailed

Monday, 26 October

Tuesday, 27 October

  • 08:30-09:00: Customers with Disabilities and Accessibility Vendors in Payments (Katie Haritos-Shea and Charles McCathieNevile)
  • 09:00-10:00: Automotive payments use cases (with the Web and Auto WG) (slides)
  • 10:00-10:45: Break
  • 10:45-11:30: Capabilities Strategic Reset (Pat Adler) (slides)
    • Now that the Working Group is up and running, how does the IG capture and communicate the aggregate of work going on to bring payment capabilities to the Web? We will revisit the high-level goals for this work and come up with a strategy to make progress.
    • Identity and regulatory topics?
  • 11:30-12:15: How a Web-based payment system could leverage ISO20022 (Kris Ketels) (slides)
  • 12:15-13:30: Lunch
  • 13:30-14:15: The Interledger Protocol (ILP) - A standard for linking ledgers and value networks via the Web (Adrian Hope-Bailie) (slides)
  • 14:15-15:30: Strategic direction for the Interest Group, Part II (Ian Jacobs)
    • Updates to use cases based on discussion?
    • Prioritization, planning, actions calendar including next FTF meeting and publications
    • Look at upcoming conferences as well
  • 15:30-16:00: Break
  • 16:00-17:00: Open. Some ideas:
    • Regional use cases
      • Topping up a prepaid account (99Bill, LianLian, TMoney, Furikomi)
      • Making a cash-payment (e.g., at convenience store to some network maintainer) and transmitting resulting voucher or electronic token to merchant.
    • Nbreds Web Payment demo: IOT Combined Service using Web Payment Standards (15 mins, Andy)
    • Next FTF meeting?
      • Last week of Feb FTF West Coast?
      • Do we do a roundtable in conjunction?
      • Sep FTF in Lisbon for FTF
  • Wrap-up

Candidate Topics With Commitments from People

Strategic Topics

Stakeholder Views

  • Mobile operators perspective (Natasha Rooney)
  • Payment Service Providers perspective (Chao Duan and Kepeng Li)
  • Banks perspective (Arie Levy Cohen)
    • Potentially Cyril on 4-corners and the web (decision based on his early october discussions)
  • Integrating Commerce and Payments on the Web (Joerg and DavidE signed up 2015-08-017)
  • Automotive use cases (Paul Boyes). (Tuesday)

See stakeholder view planning page.

Functional Topics

  • Verifiable attributes for Payments on the Web (Manu signed up 2015-08-017)
    • Ian has noted that this conversation is contingent on renewing the discussion since June, grounded in use cases expressed by diverse Members.
  • Internet of Value - A standard for linking ledgers and value networks via the Web (Adrian and Ripple Labs - signed up 2015-08-21)
    • Present Ripple Labs technical white paper (due to be published early October) - 20 mins
    • Propose standardisation work that can be undertaken - 10 mins
    • Discussion - 30 mins.
  • How a Web-based payment system could leverage ISO20022 (Kris/Vincent). Goals:
    • Gain a high-level shared understanding of what ISO20022 does and doesn’t do.
    • Discuss how it relates to the Web and specifically the scope of the new Working Group (if at all).
    • If there is agreement that it is relevant, discuss how it could be leveraged (including substantive issues like vocabularies and operational considerations like normative references).
  • W3C Security Activity Plans (Update). Wendy Seltzer

Topic Notes

  • Stakeholder priorities
  • Other candidate topics (some from Roadmap):
    • What would be necessary to bring a 4-corner model to the Web? (Cyril)
    • P2P Payments on the Web - enabling open Person to Person payments
    • Review of National Payments Improvements Efforts, lessons learned, and impact on Key Principles/Direction of IG work (Note: would be good to cover US Payments Improvement criteria as well as updates from others such as UK FPS, Australia NPP, SEPA/PSD, etc)
    • Mobilizing the Roadmap - planning for action. (This topic might include topics such as recruitment and specific planning around how to engage with/coordinate with WG's, CG's, etc)
    • External liaisons update?
    • Taking Capabilities documentation to the next level
    • Web Payments IG Roadmap - Charting a course forward for the IG and IG roadmap development
    • Identity/Credentials
    • Bitcoin
      • We continue to struggle to get this community involved.
    • Banks and Financial Institutions
      • Another community that we need more representation from
    • Unbanked/Underbanked and Financial Services for the Poor
      • We need a strategy, otherwise it's just hot air
    • Regulatory Hooks
      • What are we really going to do to help regulators?
    • Search and Knowledge
      • What would it take to get Yandex/Alibaba/Google's Knowledge teams involved?
    • Ecommerce
      • Offers
      • Coupons
      • Digital Receipts
      • Cross-pollination with new Digital Marketing initiative at W3C
    • Value Internet
      • Standardize a ledger format?
    • US Fed evaluation criteria applied to IG roadmap?
    • Submit "W3C Solution" as Faster Payments Candidate Solution
    • Algorithmic Contracts
      • What's our plan for these?
    • Supply Chain and Market Modeling
      • Can we use the architecture to automate the buy/sell lifecycle from mining ore, to refining, to creation of a good, to shipping, to retail sale?
    • External Reviews
      • ISO 20022 relation to deliverables of new WG; do we have new insights based on ISO20022 participation in the IG and the charter?
      • ISO 12812 use cases - how they are similar and different from the Web Payments use cases.
      • 1SO 20022 payment message dictionary standards - which are relevant to development of a Web Payments standard -- e.g., intergration.
      • ISO Study Group on amending the ISO Currency Code to accommodate virtual currencies.
      • Payments security standards -- e.g., X9 119 and other ISO standards -- relevance to Web Payments
    • Payment Logistics
      • Risk monitoring: how to get the account info and monitor the potential risks
      • Credit Gurantee: how to gurantee the user have the payment ability
    • Devices
      • Barcode Payment: how to use barcode to represent payment offer
      • Biometrics Payment: how to use biometeics payment methods to pay, for example, fingerprints, facial recognition, voiceprint etc.
  • Joint meetings
    • None planned; the groups of interest are meeting Thursday and Friday.
  • Update on Security / Authentication WG charter development (e.g., from Wendy Seltzer)
  • Next FTF meeting
    • Host in Europe?
    • Or in Cambridge, MA (AC meeting is 20-22 March)

Working Group Agenda

Important Documents

The Web Payments Working Group charter
Charter FAQ
A guide to Working Group Participants

Goals

  • Technical:
    • Transfer knowledge to the new Web Payments Working Group about the IG's vision for Web payments, emerging architecture, where the WG's work fits in, and any requirements that have been gathered.
    • Review initial input. The goal is not to have detailed discussion about the relative merits of early proposals, but rather to develop a common understanding of them.
  • Liaisons: Take advantage of the presence of other groups and people at TPAC to develop relationships and for initial discussions about how running a WG, horizontal topics (security, accessibility), API design, and testing.
  • Operations: Establish initial work priorities and plan. Leave Japan with shared understanding of what the group wants to achieve.

Detailed

Thursday, 29 October

  • 08:30-09:00: Introductions and review of meeting goals (Nick and Adrian)
    • Meeting goals
    • Looking for volunteer editors, test lead (and associated commitments)
    • Who wants to go to dinner?
    • Charter recap
  • 09:00-10:00: Web payments capabilities and where this group fits in (Pat)
  • 10:00-10:30: Break
  • 10:30-12:30: Initial input - getting a shared understanding
  • 12:30-13:30: Lunch
  • 13:30-14:30: How to write a Web API (Alex Russell)
  • 14:30-15:30: Review the Flow Imagined by our Charter (Adrian)
    • Where does discovery sit?
    • One / many wallets; browser as wallet; cloud wallets
    • Use cases for deferred payments / phases
  • 15:30-16:00: Break
  • 16:00-17:30: Technical discussion to build shared understanding (Adrian)
    • May include terminology
    • What are the hard questions?

Friday, 30 October

  • 09:00-10:00: Security considerations (Brad Hill and perhaps others; this time slot confirmed with Brad)
    • What has Web App Sec learned about designing APIs that would help us avoid mistakes?
    • What about Web Security generally (e.g., same origin policy) should we be thinking about as we start our work?
    • How would we design the APIs (or specifications) to facilitate security reviews?
    • See also Issue about PCI compliance
  • 10:00-10:15: Break
  • 10:15-11:00: More flows (Matt Saxon)
    • Recap
    • Tools
    • Candidate payment flows - 3DS, push payment (like bitcoin or credit transfer), alipay, direct debit, PSP proxies
    • Registration
  • 11:00-12:00: Accessibility considerations (Janina Sajka confirmed, and others from WAI PF; this time slot confirmed.)
    • An overview of how programmatic APIs can support accessibility
    • WAI PF experience with previous reviews of APIs and what we can learn from that
    • Considerations in the design of the APIs that would make them easier to review for accessibility support.
    • Future collaboration on accessibility of payment UI for implementations cited during Rec track process.
  • 12:00-12:30: Incorporating 3rd-party services in client-side JS: lessons from WebRTC identity management (Dominique Hazael-Massieux, this time slot confirmed)
  • 12:30-13:30: Lunch
  • 13:30-14:30: Test suites at W3C (Philippe Le Hégaret confirmed time) (slides)
  • 14:30-15:00: How we will work (Nick)
    • Tooling
    • Phone and face-to-face meetings
    • Primary roles of each chair
    • Editors (Role of the editor)
    • Ongoing relationship with the Web Payments IG
      • Role of IG (e.g., review of documents, updates on capabilities, ...)
      • Periodic updates to WG?
      • Chair-to-chair communications?
  • 15:00-15:30: Break
  • 15:30-16:30 More flows
  • 16:30-17:00 Initial plan and recap(Adrian and Nick)
    • Initial plan and milestones, who is doing what?

Notes

Operations

  • Ongoing relationship with the IG (a WG Chair + an IG chair)
    • Periodic updates between chairs?
    • Requests from WG to IG to review documents?
  • Operations (a WG Chair)
    • Meeting schedule
    • Tools (e.g., github)
  • Next FTF meeting (e.g., 2 days alongside a 1-day IG meeting)
  • Initial plan and timeline

Liaisons

  • Discussions with other groups at TPAC
    • WAI PF for introduction on their future API review?
    • Web Application Security WG

Technical Topics

  • Initial knowledge transfer from the IG
    • Capabilities
    • Requirements
    • Roadmap
  • Reviews
    • See Document Reviews
    • For WebIDL, invite public-script-coord list to review the spec
  • Test suite development (PLH?)
    • PLH has indicated he can join the meeting on Friday afternoon to discuss the test the web forward process and community and tooling
  • Topics that are likely to demand attention (put things on the table)
    • Extensibility
    • Message flows
  • How to write an API (Alex Russell?)
  • Initial input to the WG
  • Previous related work
  • KHS: Really appreciated the perspective that Dave Raggett brought to the F2F in NYC. Maybe ask him again for a 5 to 10 minute perspective now that IoT has gotten more focused, he might have additional nuggets. I think that an outside perspective helps us find new ideas and vocabularies.
    • IJ: Dave's presentation was about deployment.

Guests

  • Ganesh Jayadevan from Mahindra Comviva