Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9)

> that the data object could get awfully messy if the merchant supports 2 or 3 or 4 payment methods because none of the fields are "namespaced" and some of the fields could apply to less than all the methods. 

This is one of the reasons that we proposed the use of JSON-LD very early on in the Web Payments process (and to put more of a focus on data modeling in the beginning). It would remove the ambiguity and provide a future-proofed upgrade mechanism, but it may be too late for the WG to change direction at this point (and given the participants, I would imagine that they'll attempt to solve the problem by nesting/pairing data... which has it's own combinatorial complexity issues. As these specifications get more complex, we expect even more of these sorts of issues to surface.

-- 
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/3ds/issues/9#issuecomment-415113937