Tried to answer to all of them, that said I still fail to see what you miss to implement any signing or even an idempotent repo. Do you have a concrete example?
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mer. 16 mai 2018 à 08:12, Anders Rundgren <[email protected]> a écrit : > On 2018-05-15 13:05, Romain Manni-Bucau wrote: > <snip> > > So question is: what does the spec miss for your case? > Formatting and > ordering is in the spec and other parts are > > ourside jsonb so we are all good right? > > Well, for *enveloped* clear text JSON signatures the spec is pretty > incomplete but that is not particularly surprising (or appalling) since > there were no such requirements... > > - Serialization of JSON primitives: Undefined/Vendor specific > https://github.com/javaee/jsonb-spec/issues/50 > > - Algorithm for property sorting: Undefined/Vendor specific > https://github.com/javaee/jsonb-spec/issues/81 > > - I-JSON support: None (currently implemented as a "no-op" in Johnzon) > https://github.com/javaee/jsonb-spec/issues/80 > > Related brand new document to like (or not): > > https://github.com/cyberphone/I-JSON-Number-System#extended-numeric-data-types-compliant-with-i-json > > Cheers, > Anders > >
