Re: [w3c/payment-request] Applying "Detached" JWS Signatures to PaymentRequest (#714)

Hi @stpeter @marcoscaceres!  A peek in the reference may be of some use: https://tools.ietf.org/html/rfc7159#section-1
```code
   An object is an unordered collection of zero or more name/value
   pairs, where a name is a string and a value is a string, number,
   boolean, null, object, or array
```
I wouldn't characterize the (fully implemented) proposal as a "workaround", but rather an attempt creating something useful without "boiling the ocean".  Since JSON doesn't even separate integers and floating point numbers, it seems that a better alternative would be CBOR but then you browser guys would get a lot of new work which also isn't an option, right?

I have found that JSON (and JavaScript) can do [almost] everything you want although it sometimes looks a bit on the ugly side.

-- 
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/payment-request/issues/714#issuecomment-390696360