Serialization
From Just Solve the File Format Problem
(Difference between revisions)
(→Serialization formats) |
Dan Tobias (Talk | contribs) (→Serialization formats) |
||
| Line 18: | Line 18: | ||
* [[Cursive Script Object Notation]] | * [[Cursive Script Object Notation]] | ||
* [[DER]] (Distinguished Encoding Rules) | * [[DER]] (Distinguished Encoding Rules) | ||
| + | * [[Doge Serialized Object Notation]] (DSON) | ||
* [[FDF]] | * [[FDF]] | ||
* [[FlatBuffers]] | * [[FlatBuffers]] | ||
Latest revision as of 22:56, 22 January 2024
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.
[edit] Serialization formats
- Avro
- Bebop [1]
- Bencode (used by BitTorrent)
- BSON
- Cap'n Proto
- CBOR (RFC 8949) (CBOR description)
- CoffeeScript-Object-Notation (CSON)
- Concise Encoding [2]
- Cursive Script Object Notation
- DER (Distinguished Encoding Rules)
- Doge Serialized Object Notation (DSON)
- FDF
- FlatBuffers
- Form URL encoding (application/x-www-form-urlencoded)
- Hjson
- I-JSON
- Ion [3]
- IWA (Apple iWork serialization; .iwa)
- Java Object Serialization
- JSON (.json)
- JSON5 (.json5) [4]
- JSONB [5]
- JSONH [6]
- JSONx
- LCON [7]
- MessagePack [8]
- Microsoft XNA Compiled Format (.xnb)
- Minecraft NBT format
- Multipart/Form-Data
- OLE Property Set
- Pickle (Python)
- PostScript binary object format
- Property List (.plist)
- Protobuf (Protocol Buffers; a Google format also used within IWA)
- RELOAD
- Simple Binary Encoding
- Thrift
- Transit [9]
- UXF (Uniform Exchange Format) [10]
- XFDF
- XML (originally intended only as a markup format, but ended up as probably the most popular serialization format)
- YAML (.yaml)
