From 33f47f74d1a1032f2e78c8a6d3e6f930dfec7d17 Mon Sep 17 00:00:00 2001 From: Charles Iliya Krempeaux Date: Sat, 20 Jan 2024 08:54:15 -0800 Subject: [PATCH] initial commits --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index f080bf0..215a825 100644 --- a/README.md +++ b/README.md @@ -31,6 +31,12 @@ Also none of these supports a ‘**view-source**’ learning style (as none of t That is why the **zarf format** exists. +The **zarf format** is a text-based format (in the same way HTTP/1.1 protocol is a text-based), so a programmer can look at **zarf** files (i.e., ‘**view-source**’) to understand it. + +The **zarf format** is simple to create, thus making it easy to create an encoder. + +The **zarf format** is simple to parse, thus making it easy to create a decoder. + ## Extension Although **zarf** does _not_ require an extension (since it has magic-bytes), if a file-extension is used for a **zarf** file, it should use the `.zarf` extension (on systems where file-extensions are necessary).