Compare commits
No commits in common. "dadd298de2c12d23539c50ce572ee47e3583c92f" and "46e141aca565a15f103bb2b0b04e7c1b66b7d9ad" have entirely different histories.
dadd298de2
...
46e141aca5
|
@ -31,12 +31,6 @@ Also none of these supports a ‘**view-source**’ learning style (as none of t
|
||||||
|
|
||||||
That is why the **zarf format** exists.
|
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
|
## 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).
|
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).
|
||||||
|
@ -46,7 +40,7 @@ For example:
|
||||||
|
|
||||||
## MIME Type
|
## MIME Type
|
||||||
|
|
||||||
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).
|
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).
|
||||||
For example:
|
For example:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
Loading…
Reference in New Issue