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

Re: [payment agent] Task force call agenda for Friday April 24, 2015 - 13:30 UTC

From: Adler, Patrick <patrick.adler@chi.frb.org>
Date: Fri, 24 Apr 2015 13:09:41 +0000
To: Ian Jacobs <ij@w3.org>, Adrian Hope-Bailie <adrian@hopebailie.com>
CC: Web Payments IG <public-webpayments-ig@w3.org>
Message-ID: <D15FA9C8.26996%patrick.adler@chi.frb.org>
Hi Adrian,

Thanks for raising this.  While this was not explicitly called out on the
agenda, I believe it would have come up as part of the first topic as the
Key Concepts and narrative should describe what we are trying to do from
an architecture perspective.  Specific to the goals of the document
though, I believe it would be good to discuss that independently, because
this will help drive what goes into this document and what goes elsewhereŠ

Thanks for suggestingŠ I will add to the agendaŠ


On 4/24/15, 7:24 AM, "Ian Jacobs" <ij@w3.org> wrote:

>> On Apr 24, 2015, at 3:50 AM, Adrian Hope-Bailie <adrian@hopebailie.com>
>> Hi Pat,
>> I'm still not clear on what our goal is in writing this document. Has
>>this been agreed and captured somewhere? If not, can we put it on the
>>agenda for today.
>I think of it as a high-level communications tool. When people ask us
>³what will our work look like?² there are many kinds of answers,
> * Here are some familiar pain points we plan to address.
> * Here¹s how the experience will be different for users, merchants,
>banks, etc.
> * In technical terms, we envision a Web of payment agents that exchange
>messages so that people can pay, apply offers, get discounts, etc.
>There are likely other answers people give as well. I think all of the
>above are useful, but Pat and I have been discussing the
>third one this week.
>I¹ve been thinking about the following related but separate efforts:
> * See if we can build a shared vision (at a high-level) of what¹s going
>on (That¹s the discussion Pat and I noodled on this week)
> * What are the requirements suggested by the use cases? That¹s work I
>thought Pat and I would focus on this week, and we
>   made some progress (see ³scaffolding² below) but we kept returning to
>the first topic. I have come to agree with Pat that
>   if we have a shared understanding (both about the high-level payment
>agent story and the scaffolding) it will be easier for
>   more people to do use case analysis independently (and also then
>aggregate our findings).
> * Is there an extensible architecture for addressing the use cases? To
>me that¹s the next level of detail below the high-level
>   vision.
>Unfortunately I will miss the call today due to another payments-related
>call. Have a good discussion!
>> Adrian
>> On 24 April 2015 at 04:26, Adler, Patrick <patrick.adler@chi.frb.org>
>> Hi All,
>> Sorry for not being able to make the call this morning.  I have
>>reviewed the minutes from the meeting and have tried to pull together an
>>agenda for tomorrow to discuss some of the key questions from todays
>>call and work towards kicking things into high gear. Please let me know
>>if there are any updates or additional topics and I will be happy to add
>> ========== 
>> Web Payments IG - Payments Agent Task Force Meeting Friday, April 24th
>> Time: 13:30 UTC
>> Web Payments IG Telecon Bridge Phone US: +1.617.761.6200 x9729 ("WPAY²)
>> IRC: http://tinyurl.com/w3c-wpay
>> Duration: 60 minutes
>> Scribes: Zakim, need to assign scribe
>> ==========
>> Rough Agenda Draft
>> 1. Agenda Bashing
>> 2. Discuss/Review Key Concepts and Framework for Facilitating
>>Requirements Capture and Architecture Narrative/Vision
>> - Key Terms/Concepts to discuss:
>> - Payment Agent (incl. Web of Payment Agents)
>> - Account
>> - Account Provider
>> - Authorized User
>> 3. Discuss/Review Likely Interfaces and Communication Boundaries
>> - Agent to Agent
>> - Agent to Account
>> 4. Discuss ³Scaffolding² categories for helping to group/structure like
>>requirements and provide input to workgroups
>> - User Agent integration
>> - Identification and Discovery ­ Includes Identification and privacy
>>needs of broad number of constructs (Users, Payment Agents, Accounts,
>>Account Providers, etc)
>> - Payment Information/Content
>> - Credentials
>> - Authentication/Authorization
>> - Digital Signatures
>> - Digital Contracts (Conditional Payments)
>> - Loyalty
>> - Discounts
>> - Offers
>> - Taxation
>> - Currency Differences (Forex)
>> - Generic Payment messaging / Scheme Containers
>> - Clearing and Settlement
>> - Payment Scheduling (recurring payments)
>> - Delivery and Shipping
>> - Regulatory / Jurisdictional
>> - Account registration and provisioning
>> - Security and auditing
>> - Non-functional requirements
>> 5. Assign action items and due dates for input to requirements and
>>first integrated draft
>> Looking forward to talking to everyone on the call.
>> Pat
>> This e-mail message, including attachments, is for the sole use of the
>>intended recipient(s) and may contain confidential or proprietary
>>information. If you are not the intended recipient, immediately contact
>>the sender by reply e-mail and destroy all copies of the original
>Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
>Tel:                       +1 718 260 9447

This e-mail message, including attachments, is for the sole use of the intended recipient(s) and may contain confidential or proprietary information.  If you are not the intended recipient, immediately contact the sender by reply e-mail and destroy all copies of the original message.
Received on Friday, 24 April 2015 13:10:45 UTC

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