- From: Antonio Ruiz Martínez <arm@um.es>
- Date: Fri, 22 May 2015 13:19:56 +0200
- To: public-webpayments@w3.org
- CC: public-webpayments@w3.org, adrian@hopebailie.com
Hi everybody, After reading the current version of the document, I have some comments and suggestions that I would like to share. I hope they are useful. - Regarding user experience, I would mention that the payment process (initiation, purchase, obtaining a receipt and the product/service) should be uniform so that the user can see the process is conducted in the same way and, thus, it generates trust to the users. I do not know if this is what you want to mean with "harmonizing the checkout experience across e-commerce websites." I would also include that it should facilitate that the user can know the payment options available and even the (automatic) negotiation of these options. - I would also incluse some comment on that the way of making the encapsulation of (new or existing) payment schemes should be uniform and independent of the type of payment scheme (mobile or not). - From my point of view, I do not why know why the document needs the bullets "Enables monetization on the spectrum of Web to native apps" and "Bridges distributed value networks should part of the vision.". From my point of view, these issues are a consequence of "Encapsulates existing payment schemes and enables new schemes. " - As for security and privacy, the sentences that mention "Supports a wide spectrum of security requirements and solutions" or similar should be reworded. Why a "wide spectrum"?. I consider that the security, privacy and regulatory issues have to be taken into in the development of an e-commerce website or e-payment solution. However, I consider that, e.g., the support of different authentication mechanisms is not part of the payment architecture. However, in the processes that are part of the payment process, for example, getting a payment offer, the payment architecture should define the mechanisms to protect this information. Then, I consider that in the bullet we could say that security, privacy and regulatory issues will be taken into account to design the different process of payment architecture that need to be securized. Best regards, Antonio. El 18/05/2015 a las 14:58, Adrian Hope-Bailie escribió: > The IG are trying to finalize a short vision statement for the work we > are undertaking, specifically with regards to the architecture we will > be developing, for payments on the Web. > > The document is intended to express the technical principles we consider > important in the design of the architecture and I'd appreciate some > input on it's content. > > The document is also intended to be short, less than a page, and as such > not too detailed. It's purpose is to frame the design and allow all > stakeholders to agree up front that we are aligned on our vision. > > The audience should be broad, and not necessarily payments or Web > technology experts, but since this is related to the design of a > technical architecture the content will be technical. > > Please have a look at the first draft of this document and send me your > feedback. > > https://www.w3.org/Payments/IG/wiki/Payment_Agent_Task_Force/Vision > > Thanks, > Adrian > > p.s. Thanks Ian Jacobs for the initial work in getting this started. -- -------------------------------------------------------- Antonio Ruiz Martínez Department of Information and Communications Engineering Faculty of Computer Science-University of Murcia 30100 Murcia - Spain http://ants.inf.um.es/~arm/ or http://webs.um.es/arm/ e-mail: arm@um.es or arm [at] um [dot] es --------------------------------------------------------
Received on Friday, 22 May 2015 11:20:32 UTC