Web Payments IG Telcon Agenda - 2015-05-11 @ 10:00 AM Eastern Time (US) for 60 minutes

[Sorry for the late agenda, having just recovered from the Paris AC meeting.]



Agenda for May 11 call:



1 Confirm agenda.  Please send agenda change requests in advance.



2 Payment Architecture



   The group has yet more progress, and review is in order.



   The latest published editors' draft is here:

   https://github.com/w3c/webpayments-ig/blob/master/latest/payment-agent/index.html

   [Github trick: prepend "http://htmlpreview.github.io/?<http://htmlpreview.github.io/?https://github.com/w3c/webpayments-ig/blob/master/latest/payment-agent/index.html>" in your browserNav window to the URL above to view.]



   Payment Architecture Priorities:

   https://www.w3.org/Payments/IG/wiki/Payment_Architecture_Priorities



   Architecture Document relationships:

   https://docs.google.com/drawings/d/1dThF6QRn8UH_8Vk9pbuTjb3HI5YtnH2GXtWdC2n_yrU/edit?pli=1



   Thoughts on the Conceptual Architecture and Technical Vision:

   https://docs.google.com/document/d/1FbHscEFUA1P6Frm9h-98bgBF8oCNNu3_0BZh8l7Aa0c/edit#<https://docs.google.com/document/d/1FbHscEFUA1P6Frm9h-98bgBF8oCNNu3_0BZh8l7Aa0c/edit>



3 June Face to Face Agenda - Continuing discussion



   We'll check to see if there are additional agenda items that the IG would like to consider.  It's important that

   we consider these items in a balanced way, and keep our #1 priority considering "how will this help our work

   move forward."



   Current meeting page:

   https://www.w3.org/Payments/IG/wiki/Main_Page/FTF_June2015



   Agenda notes:

   https://www.w3.org/Payments/IG/wiki/Main_Page/FTF_June2015#Agenda_notes



   [If you have not yet done so, please register:

   https://www.w3.org/2002/09/wbs/73816/ftf201506/]



4 Work Review Round-Table



   If no topics concerning the following groups are raised above, this section is for any late-breaking or unannounced update from the task forces.



   a. Use Cases and Glossary - Manu Sporny, Evert Fekkes

       https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force

       https://www.w3.org/Payments/IG/wiki/Glossary



       Complete Issues and Actions:

       Use Cases: http://www.w3.org/Payments/IG/track/products/2

       Glossary: http://www.w3.org/Payments/IG/track/products/1



       The first public working draft is nearing completion:

       https://dvcs.w3.org/hg/webpayments/raw-file/default/latest/use-cases/index.html



   b. Payment Architecture - Patrick Adler

       https://www.w3.org/Payments/IG/wiki/Payment_Agent_Task_Force



       Complete Issues and Actions:

       http://www.w3.org/Payments/IG/track/products/3



   d. External Reviews - Claudia Swenseid

        https://www.w3.org/Payments/IG/wiki/External_Reviews_Task_Force



        For complete issues and actions see:

        http://www.w3.org/Payments/IG/track/products/5



        Claudia will report on two items:

        * tokenization standard vis-a-vis the EMVCo tokenization specification

        * X9's offer to review any of the W3C's output



   e. Communications Strategy - Pat Adler, Ian Jacobs

       https://www.w3.org/Payments/IG/wiki/Communications_Strategy_Task_Force



       For complete issues and actions see:

       http://www.w3.org/Payments/IG/track/products/6





5 AOB



------



Conference bridge:  Zakim +1 (617) 761-6200, code 9729 IRC Channel: #wpay IG home page: http://www.w3.org/Payments/IG/ For details on meeting participation see http://www.w3.org/Payments/IG/#telec


________________________________
This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.