> If we expect that various payment method dictionaries will share data members - as this method shares supportedMethods and supportedTypes (not supportedCardTypes BTW) - does it make sense to define a reuse and extension mechanism instead of redefining these methods each time and saying that they are similar to the same members from other dictionaries? Defining the same thing in two different places never feels like a good idea... We should not make the BasicCard spec a dependency of anything. 1. It is not a W3C Recommendation, it's just a Note. 2. The vision of the WG has always been that BasicCard is simply a bootstrap and will hopefully go away very soon. -- 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-methods-tokenization/issues/26#issuecomment-359195146
Received on Saturday, 20 January 2018 19:16:56 UTC