- From: Shane McCarron <notifications@github.com>
- Date: Tue, 03 May 2016 05:33:47 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Tuesday, 3 May 2016 12:34:19 UTC
Frankly, this is my problem with using WebIDL as a way of representing a data model. IDL isn't *for* data modelling (I speak as someone who was on that committee at OMG back in the day). It was *for* defining APIs that may be connected asynchronously over a network - especially when the different ends of that connection might be in differing programming languages. It represents a contract. In this case the contract is between the payee and the payment app for the important parts of the data. And we are in no position to enforce nor even negotiate that contract. At least, I don't think we are. It is too fluid. --- 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/browser-payment-api/pull/176#issuecomment-216513821
Received on Tuesday, 3 May 2016 12:34:19 UTC