Serialization
From Just Solve the File Format Problem
(Difference between revisions)
(→Serialization formats) |
(→See Also) |
||
| Line 37: | Line 37: | ||
== See Also == | == See Also == | ||
| − | |||
| − | |||
* [[Databases]] | * [[Databases]] | ||
* [[Markup]] | * [[Markup]] | ||
| + | * [[Metaformats]] | ||
| + | * [[Protocols]] | ||
| + | * [[Text-based data]] | ||
* [[Transfer Encodings]] | * [[Transfer Encodings]] | ||
Revision as of 16:26, 2 May 2017
Serialization is used to transform data structures (as used within a program, in whatever native formats might be used by the programming language the program is in) into a file or data stream of standardized format to be saved for later use, or transmitted through a network to be used by a different program elsewhere.
Serialization formats
- Bencode (used by BitTorrent)
- BSON
- Cap'n Proto [1]
- CBOR (RFC 7049) [2]
- CoffeeScript-Object-Notation (CSON)
- Cursive Script Object Notation
- DER (Distinguished Encoding Rules)
- FDF
- Form URL encoding (application/x-www-form-urlencoded)
- Hjson
- I-JSON
- Ion [3]
- IWA (Apple iWork serialization; .iwa)
- JSON (.json)
- JSON5 (.json5) [4]
- JSONH [5]
- JSONx
- LCON [6]
- MessagePack [7]
- Microsoft XNA Compiled Format (.xnb)
- Multipart/Form-Data
- Pickle (Python)
- Property List (.plist)
- Protobuf (Protocol Buffers; a Google format also used within IWA)
- Transit [8]
- XFDF
- YAML (.yaml)
