reiver
/
raft-format
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Compare commits

base: reiver:46e141aca565a15f103bb2b0b04e7c1b66b7d9ad
Branches Tags
reiver:master
...
compare: reiver:dadd298de2c12d23539c50ce572ee47e3583c92f
Branches Tags
reiver:master

2 Commits
46e141aca5 ... dadd298de2

Author SHA1 Message Date
Charles Iliya Krempeaux dadd298de2 initial commits 2024-01-20 08:54:25 -08:00
Charles Iliya Krempeaux 33f47f74d1 initial commits 2024-01-20 08:54:15 -08:00
1 changed files with 7 additions and 1 deletions
Show Stats Expand all files Collapse all files

8
README.md
View File

@ -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).
@ -40,7 +46,7 @@ For example:
## MIME Type
Although **zarf** does _not_ require a MIME-type (since it has magic-bytes), f a MIME-type is used for a **zarf** file, it should use the `multipart/zarf` extension (on systems where file-extensions are necessary).
Although **zarf** does _not_ require a MIME-type (since it has magic-bytes), if a MIME-type is used for a **zarf** file, it should use the `multipart/zarf` extension (on systems where file-extensions are necessary).
For example:
```