Add "How it Works" section

[msporny]

This PR adds a section called "How it Works" to the Data Integrity specification to conceptually describe how the technology described by the specification works.

There are a few images in the PR, so I'm attaching a screen shot for how the rendered diagram looks:

At present, the section is a bit out of place, and probably belongs more in the Introduction than in this section. I'll do an Editorial move later once we've agreed to the content.

---

Preview | Diff

[TallTed]

Mostly minor punctuation and grammar.

[decentralgabe]

nice work, this is easy to read and comprehensive

[dlongley]

I think this is a good start. We'll want to make sure that the description here also cleanly maps to what happens with BBS signatures, for example. In BBS signatures, transformation occurs, but the transformed data produces N messages that are hashed and signed, i.e., there are multiple signatures. This still seems to map to me but we'll have to see if others agree, ideally from the BBS suite spec writers.

[msporny]

In BBS signatures, transformation occurs, but the transformed data produces N messages that are hashed and signed, i.e., there are multiple signatures.

Yes, I winced in the same way when I re-read the text yesterday. I do think we'll need to do some minor modifications to handle the "hash N messages" case. I'll try to put that in a revision before merging.

[iherman]

My comment is purely stylistic and, I admit, picky... (I approve the text regardless of taking this comment or not)

The sentence:

This process is conceptually similar to...

is trying to provide an analogy to a reader who is unfamiliar with the concept of digital signatures and/or proofs of stake. And that is fine. However, wouldn't it be better, for consistency's sake, to add a similar analogy for what a hash function means? (I guess we can get away without an analogy for the transformation bit.)

[mprorock]

awesome improvement!

[msporny]

However, wouldn't it be better, for consistency's sake, to add a similar analogy for what a hash function means? (I guess we can get away without an analogy for the transformation bit.)

I have added this here: 0c83e1c

[msporny]

Editorial, multiple reviews, changes requested and made, no objections, merging.