Re: Woleet presentation

Hi Gilles,

One of the shortcomings of version 1 was that the specification used regular JSON, and as such, did not have a canonical form. Because of this, implementing any sort of digital signing mechanism was problematic, as you could never be sure the JSON you have is in the same format/order as it was when it was signed.

This has been addressed in version 2. Chainpoint v2 receipts are constructed using JSON-LD. One of the benefits of JSON-LD is that JSON-LD has a defined canonical form. This allows for implementation of digital signatures and verification of those signature without the issues experienced when using regular JSON. Furthermore, JSON-LD also has its own defined mechanism for signing JSON-LD documents, called LD Signatures. Adopting JSON-LD as the receipt format also gave us the capability to optionally digitally sign the Chainpoint documents using LD Signatures.

Here is an excellent resource for learning more about JSON-LD, including a playground where you can test many aspects of JSON-LD documents as well as see LD Signatures in action.
http://json-ld.org/

Details on LD Signatures can be found here ->
https://w3c-dvcg.github.io/ld-signatures/



Jason
----------
[Tierion] [http://tierion.com/]
Jason Bukowski / Lead Developerjason@tierion.com [mailto:jason@tierion.com]
Tierionhttps://tierion.com [http://tierion.com/]
[Twitter] [https://twitter.com/_JasonBukowski_]  [Linkedin] [https://www.linkedin.com/in/jasonbukowski]