At today's teleconference [1] we resolved that: * Payment method identifiers that are URLs can be used to discover machine readable information. * We are defining a specification (Payment Method Manifest Spec [2]) that will house that machine readable information. * Given a payment method identifier (URL) user agents will discover payment method manifest files via HTTP Link headers. Editorial notes: * The Payment Method Identifier spec and Payment Method Manifest spec today are distinct; at some point they might be combined but we need to discuss that further. * We need to update the PMI spec to make clearer that the other spec (today) defines the manifest file's contents * We need to update the manifest file spec to talk about addressing those files (via HTTP Link headers). [1] https://www.w3.org/2017/02/02-wpwg-minutes#item04 [2] https://w3c.github.io/webpayments/proposals/Payment-Manifest-Proposal.html -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments-method-identifiers/issues/19#issuecomment-277083812
Received on Thursday, 2 February 2017 21:07:46 UTC