From 4f7385a04d4e6a9763a0a91ea0dac56b7de8ef4d Mon Sep 17 00:00:00 2001 From: blek Date: Wed, 3 Jan 2024 13:31:19 +1000 Subject: [PATCH] grammar; specify more obviously what is what --- SPEC.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/SPEC.md b/SPEC.md index 34f5b8b..9a1aa10 100644 --- a/SPEC.md +++ b/SPEC.md @@ -6,11 +6,12 @@ This standart does not describe an encryption algorithm; It is a way to store en # NOTATIONS AND CONVENTIONS The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are interpreted as described in BCP 14 [RFC2119](https://www.rfc-editor.org/info/rfc2119) [RFC8174](https://www.rfc-editor.org/info/rfc8174) +This document also uses the following terminology: | Name | Description | | --- | --- | | SHA256(x) | An `x` value hashed via the SHA256 hashing function. | -| base64 | A base64 data encoding format, which is described in [RFC4648](https://www.rfc-editor.org/rfc/rfc4648) | +| base64 | The base64 data encoding format, which is described in [RFC4648](https://www.rfc-editor.org/rfc/rfc4648) | # 1. File format The file is a serialized array of strings encoded with either JSON or CBOR. The filename MUST end with either `.json` or `.cbor` extension to clarify the encoding.