Writing a proper spec

[SharkWipf]

The current spec is a very simple draft, there is no real structure or design guideline behind it.
Once we've finalized the general design, we should make it a "proper" spec, with clear, consistent, non-ambiguous language.
I do not have much experience with this, so suggestions on how to handle this are welcome.
Some suggestions have been made on Discord already, as to not steal credit I'll wait for those to be reposted here however.

[w-m]

The formatting suggestion from Discord:

About the structure of the design document: it might be helpful to take inspiration from successful RFC processes. I think RFC 7322 is too technical and strict at this point. But being aware of definitions for the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" should be helpful RFC 2219, so everybody in the discussion is on the same page, and there's no confusion.

Also I think PEPs (from Python development) are often well-structured and very readable. Consider using this structure: PEP 0001 - What belongs in a succesful pep? - I think all points but 7 and 8 (security & how to teach this) apply rather nicely to the container format proposal.