[w3c/webpayments-methods-tokenization] How are empty supported* fields to be interpreted? (#48)

I suspect the answer is that they should be interpreted as not supporting any, but I can see a small argument for them meaning that all are supported since the field is also optional. 

-- 
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/48

Received on Saturday, 11 August 2018 02:08:11 UTC