File Format Research Introduction
File Format Research is a series of introductory articles about file formats I care about.
A file format is an specification that can be executed or parsed by the corresponding computing environment when the data is stored in a standardized format. Therefore, on the surface, the file format is only a specification for the format of each data file. In fact, it is also a specification for the corresponding interpreter, compiler or reading and writing tools.
These articles focus on file formats that are parsed directly as a whole by application software and presented to human directly. The format of some files in a multi-file system that do not need to be directly viewed or modified by humans has low priority.
File Format Names
Each file format has 3 names:
- Media Type Name as the main identifier.
- Natural Language Name is used for the article titles and paragraphs.
- Suffix Name is used to distinguish file types in the file system.
Media Type Name
Generally, it is filled in according to the Media Type of IANA (Internet Assigned Numbers Authority). Details can be found at:
For those that cannot be found on MIME, I will find names in other websites such as Wikipedia or arrange the names myself. But this should be marked “non-standard”.
It is also possible that one file format corresponds to multiple Media Types. In this case, try to keep one or seperate them into different file types.
Natural Language Name
For convenience of natural language expression, each file format should have a natural language name. If there is a standard for this name, choose the standard. If there is no standard, choose the common name. I will choose a suitable name by yourself sometimes. It will be used as the document title when introducing the file format.
Although this name is mainly used in natural languages, there should be no duplication.
Suffix Name
The file extension is part of the file name in the file system and is used to identify the file format type. Generally speaking, the file format suffix is located at the end of the file name, starting with a period .
, followed by letters or numbers.
The suffix name is mainly determined based on the recommendation of the file format standard or standards maintenance organization. If there is no recommendation, it will be generally used name. In these articles, try to ensure that a suffix name belongs to only one file format. If there is a suffix name conflict, the conflict handling method should be stated.
In addition, a file format generally has only one suffix name. When the letters in the suffix name can be uppercase or lowercase, the lowercase form is generally used. When a file format has multiple suffixes, choose the most commonly used or standardized one. It is possible that a file format have multiple suffix names. Generally speaking, a file format can identify its different variants through the meta information inside the file. It is not necessary to distinguish the variant of file format by suffix name, so currently do not give multiple suffix names to a file format. If must, sperate them into different file format types.
The suffix name will also be used as the abbreviation of the file format. When used as a file abbreviation, all capital letters (and without .
)are used unless otherwise agreed.
File format type inheritance
There is an inheritance relationship between file formats. All file formats essentially derive from constraints and specifications on binary files.
When file format B inherits A, every qualified B file is required to be a qualified A file. Improved relationships between file formats are not reflected in this description. The two file formats before and after the improvement are considered to be in a parallel relationship.
If a file format inherits directly from the 8-bit binary byte format, enter “Byte” in the “Parent Format” column.
About Programming-related Languages
Programming languages that have corresponding file formats record corresponding file formats.
Programming languages that do not have corresponding formats are mentioned as language extensions in their main dependent languages and supplemented with reference materials and tags.
Languages that do not have independent file formats or dependent formats such as BNF are not documented in this series of articles.
Symbols and Tags
Here are descriptions of the symbols I’ll use in this series of articles:
- Openness
- Open Source?
- 📖 Open format documentation
- 📕 Private format documentation
- Charge?
- 🆓 Free
- 💰 Charge
- Open Source?
I also add at least one tag describing the usage of each format. The number of such tags is variable.
Recommended File Format
Here is a list of file formats that I personally recommend.