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

2014-02-02 Meeting Page

From Web Commerce Interest Group
Jump to: navigation, search

Web Payments IG Face-to-Face Meeting: 2-4 February 2015, Utrecht, NL

Registration

Please register as soon as possible and no later than 31st January 2015. For that, complete the the registration form


Venue

Our host is Rabobank in Utrecht.

The meeting place is in the Beatrix theater, right between the Central Station and Rabobank’s head office. Walking from the NH Hotel in the direction of Rabobank, you pass the Beatrix building. This is a really large theater, it can’t be missed. Enter through the doors opposite the multi-color banners, around the corner from the train station stairs.

Address:
Jaarbeursplein 6A,, Utrecht, Utrecht 3521 CB, the Netherlands.
Instructions on how ot reach Rabobank Offices (Beatrix Theater is only a few minutes walk from there)

In case of problem, you can contact Evert Fekkes at +31 30 216 5329 or +31 653 754 832 (mobile)

If you need a visa to attend the meeting and need an invitation letter, ask Stephane Boyera (boyera@w3.org).

Transportation and Hotels

Recommended Hotel

NH Utrecht

Jaarbeursplein 24 (Near Utrecht Central Station) Utrecht, 3521 AR NL +31-30-2977977

http://www.nh-hotels.com/hotel/nh-utrecht

The hotel is at a walking distance from the meeting venue.

An alternate hotel is Park Plaza hotel, see http://www.parkplaza.com/utrecht-hotel-nl-3531-bl/netutrec That is also at a walking distance, adjacent to the NH Hotel.

Transport

There is a direct train from Schipol Airport to Utrecht Central Station every 15 minutes. For journey advice and time tables you can also check: http://www.ns.nl ("Schiphol" as departure and "Utrecht Centraal Station" as destination).

Invited Observers

The following people are not official members of the Web Payments IG, but have been invited to join the face-to-face.

  • Patrik Smets (EMVCO Representative)
  • Floris Kleemans (UETP/Focafet Foundation)
  • Richard Martin (Visa Europe)
  • Vish Shastry (Visa Inc.)
  • Johann Caubergh (QisQi)
  • Stefan Thomas (Ripple Labs)

Meeting Specifics

When/Where

  • Dates - February 2-4, 2015
  • Location - Utrecht, NL
  • Host - Rabobank

Essential Goals for the Meeting

  1. bring our use cases up to the point where we can publish a First Public Working Draft, including refining the Glossary.
  2. review and refine the work of the payment agent task force.
  3. create a detailed outline for a “roadmap” document encompassing what we expect to do in the Web Payments Activity in the (foreseeable) future.
  4. brainstorm on who else should be involved in this activity.

Sessions

Each day will have 5 sessions:
1) Morning 1 - 9:00 - 10:30
- Break 10:30 - 11:00
2) Morning 2 - 11:00 - 12:30
- Lunch 12:30 - 13:45
3) Afternoon 1 - 13:45 - 14:30
- Break 14:30 - 14:45
4) Afternoon 2 - 14:45 - 16:15
- Break 16:15 - 16:45
5) Afternoon 3 - 16:45 - 18:00
Exceptions are:
  • Monday will start at 10:00 and have only one longish kickoff session.
  • Wednesday will end at 17:00, so "Afternoon 2" will extend by 15 minutes.

Agenda

Day 1 (Monday - Start 10:00 Local Time)

Day's Topics - IG Review, Use Case and Glossary Discussions

Morning 1

  • Administrivia
    • Welcome, Introductions, and W3M Announcements
    • Appointment of Scribe
    • Review and approval of
    • Review and approval of Santa Clara Face To Face Minutes
    • Review and Bashing of Agenda
  • Discussion: Capturing Key Principles and Desired Outcomes - What do successful Web Payments Look Like?
    • A fast and significant adoption of the technology (>100M+ in the first two years).
    • Level playing field (aka fair competition) for merchants, payment providers, customers, software vendors, and payment networks.
    • A great reduction in "stolen card" transaction fraud.
    • A great reduction in the amount of custom software that a merchant must write to integrate with new payment products.
    • Removal of the need for a merchant to hold on to sensitive customer data.
    • Greatly reduced payment provider switching costs for customers and merchants.

Lunch

Afternoon 1

  • Appointment of Scribe
  • Refining the Glossary
Web Payments Glossary
  • Introducing the Use Cases
Work of the TF so far, including categorization work
At the end of this section the goal is to have at least a handful of the "big rocks" that we are trying to improve as we go through specific use cases.
    • Approaching the Use Cases
      • Solidify our understanding, through the use case discussion, of the building blocks required to create a useful payment experience.
      • Identify missing blocks and gaps.
    • Use Cases TF Page
    • Use Cases Editors Draft
  • Introduction of the "Payment Steps" proposal (link TBA)
    • Offer of Sale
    • Establish Credentials / Payment Initiation / Request / Invoice Generation
    • Value-added services / Coupons / Loyalty / etc.
    • Jurisdictional and Regulatory Controls
    • Delivery of Proof-of-Hold / Proof-of-Funds/ Proof-of-Purchase / Digital Receipt
    • Payment Clearing
    • Refunds / Reversals
  • Focus
    • Focus on data being passed, rather than who it goes to.
  • Deeper dive on the Use Cases
Use the building blocks discovered in conjunction with use cases document to walk through early use cases deliverables to do proof of concept on building block needs/goals/gaps.

Break

Afternoon 2

  • Deeper dive on the Use Cases (continued)

Break

Afternoon 3

  • Applying Scenarios and Building Blocks
this section will take the use case scenarios and key building block principles in conjunction with the logical models to determine if we have the right level of abstraction in the building blocks and if there are any additional building blocks or details that should be added/edited.
  • Short introduction of the work of UETP (30 minutes).
  • Recap/overview of Day 2

Team Dinner/Outing

Indonesisch Restaurant Borobudur

Veemarktplein 42 (facing the Jaarbeurs)
19.30
set menu: rice table (mixed dishes)

Day 2 (Tuesday - Start 9:00 Local Time)

Day's Topics - discuss the User Payment Agent, begin to formulate the outline of the Roadmap

Morning 1

  • Appointment of Scribe
  • Overview of day
  • Agenda rebash
  • Review of Logical Web Payments Models (Payment Agent Architecture Concepts)
Include roundtable discussion/white boarding session on other web payments concepts or enhancements to existing concepts

Break

Morning 2

  • Continue discussion of User Payment Agent and Logical Web Payments Models

Lunch

Afternoon 1

  • Appointment of Scribe
  • Finish discussion of User Payment Agent

Break

Afternoon 2

  • Revisit Scenarios and Building Blocks, informed now by Use Cases and Payment Agent discussions
  • Begin discussion of the Roadmap Outline
Work in this section to begin to build an outline for the roadmap and identify needed information to complete the roadmap.

Break

Afternoon 3

  • Finish Discussion of the Roadmap Outline
  • Recap/overview of Day 3
Team Dinner

Day 3 (Wednesday - Start 9:00 Local Time)

Day's Topics - finish discussion of the Roadmap document outline, brainstorm about membership, review emerging ideas, define next steps

Morning 1

  • Appointment of Scribe
  • Overview of day
  • Agenda rebash
  • Roundtable discussion on new marketplace happenings that might influence/impact our work.
[E.g. new product launches/announcements/credentials, etc.]

Break

Morning 2

  • Membership brainstorm
    • Talent/Recruitment
      • Looking at the where we would like to go with the release plan,
      • Identify prioritized list of needed expertise/experience that will be required to ensure goals are met.

Lunch

Afternoon 1

  • Appointment of Scribe
  • Membership Brainstorm continued
    • Industry engagement and promotion - engage the broader workgroup in determining forums and places to build awareness of the W3C Payments work and any support needed from the team

Break

Afternoon 2

  • Refine Go-Forward Plans
    • Use Case FPWD publication
    • Payment Agent publication
    • Other required task forces or recommendations for WGs to W3M
  • Looking Forward: Wrap up, Action Items, etc.
  • AOB
Adjourn (17:00)

Minutes