Romain, that is true. But the question is: what is the advantage of using CBOR over simply transferring the original resource data (just like the original document of the TAG proposed)? Ivan --- Ivan Herman Tel:+31 641044153 http://www.ivan-herman.net (Written on mobile, sorry for brevity and misspellings...) > On 30 Jan 2018, at 20:04, Romain <rdeltour@gmail.com> wrote: > >> On 30 Jan 2018, at 19:11, Schindler Wolfgang Dr. <w.schindler@pons.de> wrote: >> >> Am I right then that for a content document in HTML CBOR only means a 1:1 translation of UTF-8 codes into a binary format that would have exactly the same file size. If this is true, I’m afraid I don’t see (yet?) the connection to Web Packaging and the rationale for exchanging a human-readable format for a binary format. Or do I perhaps miss decisive goodies? > > With CBOR and Jeffrey’s spec, you can *bundle* resources together and exchange them as one cohesive resource. Since a publication is a *collection* of multiple resources, we need a format to package them. > > Romain. >
Received on Tuesday, 30 January 2018 19:33:28 UTC