W3C home > Mailing lists > Public > public-webpayments-ig@w3.org > March 2015

RE: [use_cases] Web Payments Use Cases - Organized by Phases

From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Date: Tue, 10 Mar 2015 13:36:28 -0400
To: "'Ian Jacobs'" <ij@w3.org>, "'Web Payments IG'" <public-webpayments-ig@w3.org>
Cc: <ryladog@gmail.com>
Message-ID: <070801d05b58$be4866d0$3ad93470$@gmail.com>
Ian,

Quick suggestion for the Introduction. While we all know that the Web Platform strives to achieve interoperability (as opposed to proprietary) technologies - I am not sure that many in the financial services sector necessarily do - so I think we should include an implication by adding *interoperable* to one of these two sentences from the opening paragraph:

1. Since the Web is ubiquitous, strengthening support for *interoperable* payments has the potential to create new opportunities for businesses and customers.

2. Although we are seeing innovation in payment services, the lack of *interoperable* Web standards makes it more difficult to adapt to new payment approaches or integrate new payment providers.

Thoughts?

* katie *
 
Katie Haritos-Shea 
Senior Accessibility SME (WCAG/Section 508/ADA/AODA)
 
Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile | Office: 703-371-5545

-----Original Message-----
From: Ian Jacobs [mailto:ij@w3.org] 
Sent: Tuesday, March 10, 2015 1:04 PM
To: Web Payments IG
Subject: [use_cases] Web Payments Use Cases - Organized by Phases

Hi all,

I spent some time recasting the use cases in terms of payment phases [1], resulting in:

 Web Payments Use Cases - Organized by Phases  http://www.w3.org/2015/03/wpay-usecases.html

The document (still rough) includes:

 * Phases (consumer/merchant flow)
 * Short glossary (Evert’s glossary will make the connections between generalist vocabulary and specialist terminology).
 * Assumptions. (These are broad assumptions factored out from the use cases; the list is mostly to illustrate the idea).
 * Use cases. (Now these are very short statements, organized by phases)
 * Narratives. (One narrative for a web payment scenario, to be followed by much shorter statements to show the variety of 
                      [complete] scenarios we have in mind.). The Online purchase narrative is not yet complete.)

Note that with this document design, architecture and technical requirements are meant to live elsewhere.

If this approach appeals to the group, then more work will be required to make sure that the use case statements (now mercifully short) are accurate and that we have all the scenarios we think are important. 

Comments welcome,

Ian

[1] https://dvcs.w3.org/hg/webpayments/raw-file/default/latest/use-cases/index.html#the-phases-of-a-payment
--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                       +1 718 260 9447
Received on Tuesday, 10 March 2015 17:37:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:33 UTC