The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack. This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.
CBOR — Concise Binary Object Representation | Specification
CBOR is specified in an Internet Standard RFC. RFCs that serve as Internet Standards are generated by the IETF based on an extensive technical review and quality control process. These are meant to last.
MessagePack: It's like JSON. but fast and small.
MessagePack is an efficient binary serialization format. It lets you exchange data among multiple languages like JSON. But it's faster and smaller. Small integers are encoded into a single byte, and typical short strings require only one extra byte in addition to the strings themselves.
Protocol Buffers
Protocol Buffers are language-neutral, platform-neutral extensible mechanisms for serializing structured data.
DASL: DRISL — Deterministic Representation for Interoperable Structures & Links
DRISL is a serialization format that is deterministic (so that the same data will have the same CID) and that features native support for using CIDs as links. It is based on CBOR, using a narrow profile of CBOR's "Core" featureset called "[[cborc-42]]", specified formally in this IETF document.
Caveman | Lithic Token Compression
A semantic constraint engine for Claude Code & Codex. Forces agentic communication into minimal-token lithic structures. Retain 100% technical accuracy while destroying up to 87% of output latency.
The Bitter Lesson is coming for Tokenization
Highlights the desire to replace tokenization with a general method that better leverages compute and data. We'll see tokenization's fragility and review the Byte Latent Transformer arch.
DASL — Data-Addressed Structures & Links
A small set of simple, standard primitives to work on content-addressed data.
DASL — Data-Addressed Structures & Links
A small set of simple, standard primitives to work on content-addressed data.
Design Tokens Format Module 2025.10
This document describes the technical specification for a file format to exchange design tokens between different tools.
PBF Format - OpenStreetMap Wiki
PBF format ("Protocolbuffer Binary Format") is primarily intended as an alternative to the XML format. It is about half of the size of a gzipped planet and about 30% smaller than a bzipped planet. It is also about 5x faster to write than a gzipped planet and 6x faster to read than a gzipped planet. The format was designed to support future extensibility and flexibility.
DASL: Content-Addressable aRchives (CAR)
The CAR format offers a serialized representation of set of content-addressed resources in one single concatenated stream, alongside a header that describes that content.
rfcs/atproto/001-private-content.md at main · knasher/rfcs
Technical RFCs and design proposals for protocols and systems - knasher/rfcs
New blog post "JSON, CBOR and numeric types" about the distinction between integer and #floats in JSON: vmx.cx/cgi-bin/blog/index.cgi/json-c… #atproto
JSON, CBOR and numeric types | vmx - the blllog.
vmx.cx